Prove bounded memory across global jobs, attachments, migration, and recursion

[flyingrobots]

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

Outcome

Extend the v19 bounded-observation proof into a release gate covering every path that previously escaped through full state or eager attachment collection.

Required proof

• Generated oversized graph migration, reopen, append, checkpoint, resume, comparison, BTR, export, diagnostics, and bounded readings under explicit heap/RSS caps.
• A logical retained value above the 5 MiB decode boundary with every actual page/shard below its configured limit.
• Multi-gigabyte generated attachment streaming plus a memory-hostile eager control.
• Recursive graph traversal with shared children, direct and indirect cycles, live locators, redaction, missing capability, and slow-consumer backpressure.
• Source ratchets for forbidden full-state codecs, replay-basis contracts, eager content APIs, and unbounded collectors.
• Compact generators and low-megabyte checked-in fixtures only.

Acceptance

• Correctness, cardinality, termination, receipts, and memory limits are hard gates.
• CI runs real production storage/page paths.
• Baseline changes require reviewed source changes.
• The release witness cites merged-main results.
• A disposable Think migration is recorded as local release evidence without committing user data.
• Existing Goalpost: v19 bounded-memory and CPU performance contract #758–Publish benchmark history and gate performance regressions in CI #761 and Prove and improve migrated v18-to-v19 read performance #800 are revalidated rather than assumed sufficient.

[coderabbitai]

🔗 Related PRs

#93 - Fix recursive tree OID read fanout and release v17.0.1 [merged]
#107 - Prepare v18.0.0 release metadata and final gates [merged]
#751 - feat(materialize): add retained CAS materialization handles [merged]
#788 - Add one-shot v18-to-v19 retained-substrate migration [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!