fix(release): synchronize reviewed private API baselines

[Eclipseic1848]

Summary

• Synchronize the Runtime and Worker API snapshots after the already-merged append-cursor and idempotency fixes.
• Refresh the corresponding candidate-baseline hashes and capture metadata, with an explicit update reason.
• Change only three baseline files. Product code, public method signatures, schemas, dependency contracts, acceptance conditions, quality floors, and the historical reference baseline remain unchanged.

Cause

Candidate Qualification run 33815181917 (attempt 2) passed the npm security audit on Ubuntu and Windows, then failed because the two API snapshots still described the pre-fix private members. The drift consists of six private declarations and one test-hook comment; it is not a network failure or a new public-method change.

Validation

• Regenerated snapshots from a fresh production build using the existing baseline update command.
• node scripts/phase2-baseline.mjs: passed.
• Independent comparison: public signatures remain identical after removing private declarations and comments for diagnostic comparison only. The production baseline checker remains unchanged.
• Deep equality check: all baseline contracts other than the two reviewed API hashes remain unchanged; only evidence metadata and the captured development commit were refreshed.
• Repacked coremind-runtime@0.7.1 with npm 11.5.1: SHA-256 remains 97c3bb9abb89981d93505e7c39a0de3599689ba2683a015bbe001b0f2af9f80d.
• git diff --check: passed.
• Independent Standards review: PASS, no findings. Independent Spec review: PASS, no findings.

Release boundary

This PR does not create a tag or publish packages. Engineering and Candidate Qualification checks remain required. Both earlier candidate attempts skipped Provider certification; no real Provider certification has run yet for this version.