v0.26.7

docs/V0.26.7_IMPLEMENTATION.md

@@ -36,9 +36,12 @@ Current cache, vhost/backend and installation documentation was reviewed alongsi
 The cache freshness clock remains RFC-oriented: ordinary stored HITs advance `Age` from
 `initial_age + resident elapsed time`, while a successful validator revalidation starts a
 new freshness calculation. `X-Cache-Resident-Age` remains the monotonic residency clock
-across revalidation and tier movement. `Age` is now protected from generic response-header
-rules, and regression coverage explicitly checks that both the wire HIT header and `/cache`
-object age advance from the stored clock.
+across revalidation and tier movement. Existing 0.26.6 custom `Age` rules remain accepted
+for configuration compatibility. Response-side Age rules are isolated to the final wire
+stage, so set/append/remove cannot feed back into stored freshness, TTL calculation or
+validator revalidation. Regression coverage explicitly checks that both the wire HIT header
+and `/cache` object age advance from the stored clock before any optional presentation
+override.
 
 Compression still refuses Authorization, private/no-store/no-transform, Set-Cookie, ranges,
 SSE, upgrades and already encoded responses. Cookie-bearing requests now have one bounded