v6.1.0: Bounded Residency

[flyingrobots]

Outcome

Large-vault and large-blob reads have explicit bounded-residency contracts: single vault lookup uses targeted tree reads when available, vault listing streams when possible, and unbounded payload reads prefer streaming blobs.

Design

• docs/design/0045-v6-1-bounded-residency/bounded-residency.md

Current Truth

• Archived source material identifies full vault tree loading and adapter blob materialization pressure.
• GitPersistenceAdapter already exposes readBlobStream(), readTreeEntry(), and iterateTree() primitives.
• The design must prove those primitives are a coherent product contract, not just available adapter methods.

Goalpost Slices

• Bounded Residency: targeted vault lookup #43
• Bounded Residency: streaming vault list #44
• Bounded Residency: blob read residency contract #45
• Bounded Residency: docs and release evidence #46

Required Proof

• RED tests before implementation for each runtime behavior slice.
• Focused tests plus npm test before PR closeout.
• Design witness under docs/design/0045-v6-1-bounded-residency/witness/ when implementation lands.