[GP4-S3] WAL-After-Retention Commit Ordering

[flyingrobots]

Roadmap slice: GP4-S3
Goalpost: Goalpost 4: Retained Evidence Durability
Parent: #519
Related: #512, #513, #517, #522

Source: docs/design/wal-wsc-durability-roadmap.md on branch cycle/521-wal-wsc-storage-relationship at bde7957c.

Scope

Parent issues:
#519,
#521.

Scope:

• Ensure WAL records retained material refs only after the referenced bytes are
  available or intentionally recorded as missing/redacted/obstructed posture.
• Make crash boundaries explicit.

Acceptance:

• Crash before WAL reference may leave orphan retained bytes, but no false
  causal claim.
• Crash after WAL reference can recover the retained ref or typed missing
  material posture.
• Retained material loss faults only at the appropriate scope:
  submission, receipt/ticket, runtime global, reading, or diagnostic loss.

Witness:

cargo test -p warp-core retained_material_wal_commit_order

Dedupe note

This is the PR-sized implementation slice for the roadmap item above. Existing umbrella or adjacent issues remain linked as Parent/Related rather than duplicated here.

[coderabbitai]

🔗 Related PRs

#323 - Witnessed suffix admission evaluator [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#379 - feat(core): commit runtime WAL ACK evidence [merged]
#550 - Expose braid membership history [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!