Merge concurrent immutable history correction

Authored-By: OpenAI (GPT-5) <noreply@openai.com>
2026-08-29 23:17:33 +00:00
parent 898816db16 892b6e6441
commit 9b0a8c4fd4
3 changed files with 69 additions and 25 deletions
@@ -134,9 +134,9 @@ 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 and `site-publish-history.yaml` retain every
-seen bucket's access, prior route, and cumulative bucket-relative immutable
-paths, including while an artifact is absent. When a move
-places that retired prefix inside the new sync scope, only its declared
+seen bucket's access, prior route, and cumulative bucket-relative immutable key
+prefixes, including while an artifact is absent. Removed or renamed rules stay
+recorded. When a move places a retired prefix inside the new sync scope, its
 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.