[v0.17 ANNO] Track the versioned annotations sidecar cutover

[TheGreenCedar]

Package ANNO tracking issue in the v0.17.0 consolidated remediation program.

Outcome

Track the ordered delivery of the annotations storage foundation and sidecar cutover. This issue owns no implementation PR and must not appear in a PR closing keyword; each PR-sized child closes only itself.

Ordered delivery

1. ANNO-A / [v0.17 ANNO-A] Add canonical annotation anchors and batched error accessors #1697 — W2.2 + W6.1: canonical annotation anchors, lookup accessors, indexed error cleanup, and batched deletion.
2. PERF-Q / [v0.17 PERF-Q] Replace broad store reads with selective lookups #1661 — W6.2 + W6.3: selective store reads and related hot-path work.
3. ANNO-B / [v0.17 ANNO-B] Cut annotation CRUD over to the versioned sidecar #1698 — W2.3 + W2.4: versioned sidecar, journaled cutover, CRUD, conservative rebinding, and visible orphans.
4. SRC-C / [v0.17 SRC-C] Repair signature identity and parser projections in one rebaseline window #1657 — W4.6 + W4.7 after annotation identity is stable.
5. STORE / [v0.17 STORE] Preserve resolution scope through deletion and hoist store invalidation #1658 — deletion-resolution scope and later storage work.

The native dependency chain is:

#1697 → #1661 → #1698 → #1657 → #1658

#1638 is the completed W2.1 precursor. W2.5, which removes the retained core bookmark tables, remains explicitly deferred to the next release.

Program boundaries

• Child implementation PRs use codex/* branches and close only their owning child issue.
• Keep the annotations sidecar outside the core projection promotion fence.
• Preserve atomic old-or-new publication, pinned readers, crash recovery, content-verified freshness, observational status/doctor, and proof-owned cleanup.
• The required core database schema-version bump belongs to ANNO-B. Product and package version surfaces remain owned by the release lane.
• Broad source proof remains once on the frozen release candidate.

Done when

• Both ANNO children are merged to dev/codestory-next and closed.
• The ordered storage dependencies are represented by native issue dependencies.
• Bookmarks and categories survive position shifts, full refresh, unique rename or move, concurrent publication and CRUD, cache reset, migration crash, ambiguity, deletion, and reappearance.
• No core cleanup can delete user state, no older writer can fork annotation truth, and retained legacy tables remain carry-over rather than an active write path.
• The tracker is closed manually only after the integrated acceptance evidence is recorded.

Refs #1179