fix(site-publish): retain immutable route history

Authored-By: OpenAI (GPT-5) <noreply@openai.com>
2026-08-29 23:15:29 +00:00
parent 85a0b41380
commit 892b6e6441
3 changed files with 79 additions and 27 deletions
@@ -133,8 +133,10 @@ any route's mutable objects change.
 Mutable default and override partitions receive their final cache policy before
 the matching prefix-scoped stale deletion, so publication never exposes a
 provisional cache policy or a pointer to a missing immutable target.
-Generated Ingress annotations retain each bucket's prior route and immutable paths. When a move
-places that retired prefix inside the new sync scope, only its declared
+Generated Ingress annotations retain each bucket's prior route and all immutable
+key prefixes. The prefixes are bucket-relative and carried forward after a rule
+is removed or renamed, so later deployments and route moves cannot forget them.
+When a move places a retired prefix inside the new sync scope, only its declared
 immutable subtrees are excluded; a current-file collision fails publication.
 The bucket-keyed history rejects a protected-to-public transition even when the
 artifact is renamed; publishing that artifact publicly requires a new bucket.