Eliminate production full-state materialization contracts

[flyingrobots]

Plan: https://github.com/git-stunts/git-warp/blob/plan/streaming-recursive-materialization/docs/plans/streaming-indexed-recursive-warp.md
Design PR: #813

Problem

Production still exposes complete-state contracts through loadReplayBasis(): Promise<WarpState>, materialization requests carrying WarpState, monolithic full-state codecs, whole-state hashing, and compatibility paths that reconstruct the complete graph.

This contradicts #626, #738, and #742 and caused the real Think migration to fail after promotion when a 23,995,927-byte replay basis reached the 5 MiB production CBOR boundary.

Outcome

• Delete the production full-state codec and replay-basis adapter.
• Remove ports and requests that accept or return a complete graph state.
• Ratchet forbidden whole-state names and unbounded fallbacks in src/.
• Prototype bounded replacements for patch, checkpoint, comparison, BTR, export, diagnostics, and retained resume.
• Delete _materializeGraph() rather than renaming the same operation.

Acceptance

• No production port, adapter, service, command, or proof accepts or returns a complete graph state.
• encodeWarpFullState, decodeWarpFullState, decodeCanonicalWarpFullState, and loadReplayBasis are absent from production.
• Architecture tests fail when a forbidden contract is reintroduced.
• Any global mutable algorithm uses an explicit bounded external workspace.
• Related debt LogicalTraversal is a deprecated facade with a broad materialization seam #225, MaterializeController is a god object (~1009 LOC) #226, _materializeGraph() survives the v17 reading contract #248, and Consumer typecheck still expects public materialization #260 is closed or narrowed with source evidence.

[coderabbitai]

🔗 Related PRs

#732 - Fix: anchor state-cache payloads against Git GC [merged]
#746 - Delete dead WARP caches and homemade CAS paths [merged]
#755 - fix: retain bounded materialization roots [merged]
#771 - feat: resume retained materialization predecessors [merged]
#813 - Define streaming indexed recursive WARP architecture [open]

---

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