Delete dead WARP caches and homemade CAS implementations

[flyingrobots]

Parent: #734
Blocked by: #735

Remove

• SeekCachePort, CasSeekCacheAdapter, cache refs, CLI clear path, and runtime wiring.
• The unused RuntimeHost adjacency LRU.
• CasFirstMemoizationEngine and CasIndexStorageAdapter.
• Uninstantiated index rebuild and streaming checkpoint storage paths.
• HealthCheckService/CachedValue where no live caller exists.
• Production defaultBlobStorage, InMemoryGraphAdapter, browser hashing, and browser-only storage fallback.
• Legacy unattached intent blob storage where the v19 intent path supersedes it.

Proof

• Graft/reference scans show no surviving production callers.
• Public export and consumer fixture tests identify intentional removals.
• Test fakes live under tests and use supported git-cas adapters.
• No replacement cache is introduced.

[coderabbitai]

🔗 Related PRs

#705 - Fix: remove domain default port singletons [merged]
#708 - Fix live materialization state-cache hits [merged]
#726 - Move graph exports behind v19 public API boundary [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!

[flyingrobots]

Dependency transition: #735 is closed via merged PR #744, so this slice is no longer blocked. Status moved to status:active; implementation will stack on current main after merged PR #745.

[flyingrobots]

Implemented and merged in #746.

Closure evidence:

• The supported public storage constructor is GitStorage; Git history and the repository-scoped git-cas adapter are composed internally and bound behind the opaque WARP storage handle. [cite: storage.ts#16-37@ed963453be09357668f101083e097d977cf260b2] [cite: src/application/WarpStorageRegistry.ts#9-34@ed963453be09357668f101083e097d977cf260b2]
• Repository CAS construction and CDC policy have one production owner, GitCasRepositoryAdapter, which supplies WARP runtime storage services behind ports. [cite: src/infrastructure/adapters/GitCasRepositoryAdapter.ts#46-85@ed963453be09357668f101083e097d977cf260b2]
• Intent admission no longer writes unattached persistence blobs, and the regression test proves writeBlob() is not called. [cite: src/domain/services/controllers/IntentController.ts#28-40@ed963453be09357668f101083e097d977cf260b2] [cite: test/unit/domain/services/controllers/IntentController.test.ts#40-56@ed963453be09357668f101083e097d977cf260b2]
• The production/publication AST gate bans the deleted cache, CAS, index, health, and in-memory storage symbols and former seek/adjacency wiring identifiers in every identifier role and module path. [cite: test/unit/scripts/storage-ownership-boundary.test.ts#6-36@ed963453be09357668f101083e097d977cf260b2] [cite: test/unit/scripts/storage-ownership-boundary.test.ts#56-91@ed963453be09357668f101083e097d977cf260b2] [cite: test/unit/scripts/storage-ownership-boundary.test.ts#94-121@ed963453be09357668f101083e097d977cf260b2]
• The package contract permits only GitStorage on the storage subpath; in-memory composition is confined to test helpers. [cite: test/unit/scripts/v19-public-api-boundary.test.ts#211-216@ed963453be09357668f101083e097d977cf260b2] [cite: test/helpers/MemoryStorage.ts#6-18@ed963453be09357668f101083e097d977cf260b2]
• Retained runtime behavior remains executable across checkpoint reload, index verification, provenance, intent, sync, and GC paths after the deletion. [cite: test/unit/domain/runtimeProductExecutableSurface.test.ts#29-120@ed963453be09357668f101083e097d977cf260b2] [cite: test/unit/domain/runtimeProductExecutableSurface.test.ts#122-160@ed963453be09357668f101083e097d977cf260b2]

Final gates: all GitHub Actions checks passed, CodeRabbit approved, and zero review threads remained unresolved before merge.