[GP3-S1] WSC Causal-History Export Profiles

[flyingrobots]

Roadmap slice: GP3-S1
Goalpost: Goalpost 3: WSC Causal-History Export And Import
Parent: #522
Related: #521

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

Scope

Parent issues:
#522,
#521.

Scope:

• Add a versioned export profile model for:
  ref-only, self-contained, and CAS-addressed.
• Define what evidence each profile must carry.

Acceptance:

• Ref-only profile carries projected graph facts, locators, segment digests,
  LSN ranges, and commit anchors.
• Self-contained profile carries enough segment bytes or retained material to
  validate the segment digest and commit chain without external WAL storage.
• CAS-addressed profile carries content hashes and semantic refs without
  claiming the CAS tier is itself causal authority.

Witness:

cargo test -p warp-core wsc_causal_history_export_profiles

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]
#323 - Witnessed suffix admission evaluator [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [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!