Bounded Residency: streaming vault list

[flyingrobots]

Parent Goalpost

• v6.1.0: Bounded Residency #38

Work

Add RED tests proving vault list consumes iterateTree() when available rather than materializing a whole tree map before listing entries.

Expected Proof

• Focused vault listing test with an adapter fixture that exposes iteration and detects whole-tree reads.
• Clear fallback test or error contract for adapters without streaming iteration.

[flyingrobots]

Resolved on origin/main at beb8a29.

VaultService.iterateVault is the incremental enumeration surface, and listVault consumes it instead of first materializing a whole vault-tree map: src/domain/services/VaultService.js#725beb8a29 and src/domain/services/VaultService.js#747beb8a29. VaultPersistence.iterateEntries prefers iterateTree and retains an explicit readTree compatibility fallback: src/domain/services/VaultPersistence.js#147beb8a29 and src/domain/services/VaultPersistence.js#153beb8a29.

The focused regression exposes streamed entries, makes readTree fail, and verifies that the whole-tree path was never used: test/unit/vault/VaultService.test.js#552beb8a29, test/unit/vault/VaultService.test.js#558beb8a29, and test/unit/vault/VaultService.test.js#576beb8a29.

The focused audit and the complete unit suite pass on the cited SHA. Closing as already implemented and covered.