1. **P2 — The new manifest cache has no retention bound.** §4.1 now requires reading each version once and keeping its manifest in memory ([spec:232](/home/paulca/amadan.net/carlos/platform-edge-asset-cache/docs/superpowers/specs/2026-10-24-edge-asset-cache-design.md:232)). `GetManifest` returns a newly decoded manifest; it supplies no cache or eviction policy ([release.go:710](/home/paulca/amadan.net/carlos/platform-edge-asset-cache/internal/release/release.go:710)). Repeated deployments therefore accumulate retained manifests even for one route, after those builds stop serving. The disk budget and fill limits do not bound this memory.
2
3
**Smallest fix:** retain only the bounded asset declaration for builds currently referenced by a local route’s installed version or serving generation; discard unreferenced entries and permit refetching on rollback. Add a test that cycles one route through many versions and verifies retained state stays bounded while both currently needed declarations remain available.
4
5
No other delta findings. The remaining corrections match the code and do not reopen the round 4 acceptance.
amadan