Refresh segment-store v1 living documentation after recovery delivery

[flyingrobots]

Problem

The living keep.segment-store/v1 reference still describes merged initialization and recovery work as future or incomplete:

• docs/formats/segment-store-v1/README.md says crash and recovery evidence remain owned by issue Build the durable crash-injection and recovery matrix #17;
• docs/formats/segment-store-v1/publication.md says issue Build the durable crash-injection and recovery matrix #17 must implement initialization;
• the same page says issue Implement catalog generations and one-writer/many-reader publication #16 does not implement admission/recovery and refers to a future admission producer.

Issues #16 and #17 are complete on main. The current-behavior reference therefore understates shipped guarantees and gives v2 migration work a stale source boundary.

Priority

P2 — should fix. This is not a current data-integrity defect, but it can misdirect implementation and review of the v1-to-v2 migration.

Dependencies

Depends on completed issues #16 and #17. It does not block issue #19, but should close during M4 before the v2 documentation becomes the primary format route.

Acceptance criteria

• Every living v1 format page describes current main behavior rather than completed issue-era plans.
• Historical scope remains available through linked issues, ADRs, and Git history without posing as current truth.
• Claims are reconciled against implemented initialization, platform admission, publication, restart, and recovery evidence.
• Existing requirement identifiers and concrete tests remain the evidence anchors.
• Documentation refusal, integrity, link, and whitespace gates pass.

Non-goals

• Changing the v1 byte format.
• Implementing v2 retention.
• Reorganizing unrelated documentation.

[coderabbitai]

🔗 Related PRs

#26 - Implement M1 Golden File Worldline identity [merged]
#48 - Specify canonical flat chunk layouts [merged]
#50 - Implement bounded streaming CAS [merged]
#54 - Define the durable segment store protocol [merged]
#68 - Define retention roots and GC liveness [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[flyingrobots]

Audit follow-up for T-14.1. Tracker: #132.

Reconcile the already-prepared v1 documentation against original criteria and integrate it; do not close solely because code exists on the feature branch.

The audit source is docs/audits/completed-roadmap-2026-09-30.md on feature/roadmap-m4-tasks. Original acceptance criteria and definitions of done remain authoritative. This comment records remaining work and links existing ownership; it does not assert that the issue is complete or change its recorded dependencies.