[GP3-S6] WSC Export/Import CLI

[flyingrobots]

Roadmap slice: GP3-S6
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,
#506.

Scope:

• Add read-only CLI export/inspect/import-verification commands for WSC
  causal-history bundles.
• Avoid mutating Echo history during import verification.

Acceptance:

• CLI can export a fixture WAL root as ref-only WSC.
• CLI can verify self-contained WSC without the original WAL root.
• CLI reports unavailable WAL/CAS material as typed obstruction JSON.

Witness:

cargo test -p warp-cli --test cli_integration wsc_causal_history

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]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#379 - feat(core): commit runtime WAL ACK evidence [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!