[GP2-S3] WARP Graph Materialization Of WAL Evidence

[flyingrobots]

Roadmap slice: GP2-S3
Goalpost: Goalpost 2: WAL Evidence Projection
Parent: #521
Related: #522

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

Scope

Parent issues:
#521,
#522.

Scope:

• Materialize the projection records into a generic GraphStore shape suitable
  for WSC serialization.
• Keep graph nodes as projected facts.

Acceptance:

• WalRoot connects to writer epochs, segments, commit anchors, and recovery
  certificate refs.
• The materialized graph can be serialized to WSC without raw WAL append
  authority.
• Rebuilding the graph from the same WAL recovery evidence produces identical
  graph/WSC bytes.

Witness:

cargo test -p warp-core wal_projection_graph_materializes_deterministically

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

#298 - feat(warp-core): TTD domain logic — provenance storage + causal cone walk [merged]
#379 - feat(core): commit runtime WAL ACK evidence [merged]
#389 - warp-wasm: add WARP DRIVE G2b query projection [merged]
#550 - Expose braid membership history [merged]
#551 - Finish braid historical membership and replay goalpost [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!