DOCFIX-169: fix stale bundle.yaml expectations in phase-01-bundle-deploy.md
DOCFIX-167 (Designate + D-108 DR mechanism reactivation) edited the same
shared bundle.yaml this existing, live-cloud-relevant VR0 runbook deploys,
but didn't update this runbook's own documented expectations. Found during
a full-project sweep: "expected plan: 50 apps, 97 relations" was stale
(real count 56/108); "NO designate (D-019)" GATE text was flatly wrong.
Fixed both live-gate references; left the historical 2026-06-03 as-built
record unchanged (append-only audit trail). Flagged, rather than decided,
a real architectural tension: this bundle now serves both a plain VR0
redeploy and DC1's buildout, so any future phase-01 run gets the new
charms regardless of intent.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QrcJx8TUar7pYAvpGJw57A
1 parent d2295b2 commit 4c8b2ead70a103b030343bcc625d5f7ae52642cb
@JANeumatrix JANeumatrix authored 1 hour ago
Showing 3 changed files
View
docs/changelog-20260710-phase01-bundle-staleness-fix.md 0 → 100644
View
docs/session-ledger.md
View
runbooks/phase-01-bundle-deploy.md