Collection-versioning Phases 3-5 #31

Deferred — this issue names an explicit trigger below. No work happens until the trigger fires.

Trigger

Something needs to render an old document against its original schema, or CI needs strict version pinning.

The phases

• Phase 3 (fetch by version) — the smallest read-side piece, and the one that unblocks anything interesting.
• Phase 4 (in-memory forward-migration) — the load-bearing one.
• Phase 5 (strictCollectionVersions: true) — a CI ergonomics flag.

Each is independently shippable once Phase 2 (historical config snapshots) lands.

Reference

04-collections/index.md → Future phases