diff --git a/docs/changelog-20260717-d127-iac-autostart-and-guest-updates.md b/docs/changelog-20260717-d127-iac-autostart-and-guest-updates.md
index 6b0265e..89e3bbe 100644
--- a/docs/changelog-20260717-d127-iac-autostart-and-guest-updates.md
+++ b/docs/changelog-20260717-d127-iac-autostart-and-guest-updates.md
@@ -1,5 +1,13 @@
 # 2026-07-17 -- D-127 IaC autostart matrix (baked into the deploy tooling) + Office1 guest updates
 
+> **STALE-CLAIM BANNER (added 2026-07-19, sweep Batch 2 / GA-F14).** This
+> changelog's plan-outcome prediction ("the 2 in-place collapse to 0 once the
+> bookend sets those two autostart") was FALSIFIED by reality: the bookend ran,
+> autostart went live-true, and the plan still carried the 2 changes plus a
+> forced replacement this file did not anticipate (the D-130 defect). The
+> content below is preserved AS HISTORY. Changelogs are never citable as
+> status authority (GA-R2); status lives in `docs/CURRENT-STATE.md` only.
+
 ## Guest OS updates (agent-run via passwordless sudo INSIDE the guests)
 
 The vcloud HOST + office1-opnsense stay in the operator's bookend restart; the already-deployed guests I