Correct public M3 status after catalog publication

[flyingrobots]

Priority

P1 — must be fixed before closing M3.

Problem

README.md still says catalog publication and restart recovery are future work, and describes the durable segment-store specification as containing still-planned publication work. PR #64 merged catalog generations, writer-locked filesystem publication mechanics, and immutable bounded restart snapshots, so the public project status now contradicts main.

Evidence

• README.md in the Golden File Worldline status paragraph says M3 only provides immutable-segment construction and that catalog publication remains future work.
• The following routing paragraph describes publication as still planned.
• PR Publish durable catalog generations #64 merged as 3a42bd4837d80ebf13d607aaffca05ac5ddb3fb6.

Dependencies

PR #64 is merged. This documentation repair must land before issue #17 closes M3.

Acceptance criteria

• The README states that M3 implements catalog generations, writer-locked publication mechanics, and immutable restart snapshots.
• The README keeps store initialization, platform admission, explicit crash recovery, and the crash-injection matrix assigned to Build the durable crash-injection and recovery matrix #17.
• Links and nonclaims agree with the living segment-store topic pages.
• The repository documentation-integrity, Markdown, formatting, and diff-hygiene gates pass.

[coderabbitai]

🔗 Related PRs

#54 - Define the durable segment store protocol [merged]

---

📝 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]

Resolved by #67. Current main at merge commit fa105da now states the implemented M3 catalog generations, writer-locked publication mechanics, immutable restart snapshots, platform admission, explicit recovery paths, and the 105-case crash-injection matrix. The living segment-store pages, README, changelog, and conformance routing were updated together. Hosted documentation/workflow integrity passed on the exact merged head (1c8937d), as did the full Rust, fuzz, and dependency gates. The original dependency wording is now historical because #17 is also complete.