# Changelog 2026-07-10 -- Full-project sweep: DC-DC runbook consistency fixes (DOCFIX-171)

No live infrastructure touched. Part of the full-project sweep (see
`docs/changelog-20260710-sweep-vr0-runbook-opentofu-fixes.md`, DOCFIX-170,
for the sweep's overall scope). This changelog covers findings from a
dedicated agent that re-checked all seven DC-DC Stage runbooks and the
master tracker against the actual repo state after the second gap-closure
wave (DOCFIX-162 through 168).

## Items

### 1. DOCFIX-171a -- Stage 1's calculator scripts never wired into Step 3
FILE: `runbooks/dc-dc-phase0-vcloud-prep.md`.

WHAT: `docs/dc-dc-deployment-workflow.md`'s gap register item #7 and
`scripts/dc-dc-mtu-geneve-budget.sh`'s own header both asserted "the first
real run is part of executing Step 3" of this runbook -- but Step 3 still
contained only the old manual back-of-envelope arithmetic, never actually
invoking either `scripts/dc-dc-mtu-geneve-budget.sh` or `scripts/dc-dc-
ceph-disk-budget.sh`. Same class as DOCFIX-169: a gap-closure delivery
never got cross-referenced back into the runbook that was supposed to
consume it. Fixed: Step 3 now shows the real invocations (with their exact
flags) in place of the hand-arithmetic instructions, explicitly noting the
calculator's OUTPUT (a downstream tenant-MTU consequence) is distinct from
what actually goes into `underlay_mtu` (the measured value itself).

### 2. DOCFIX-171b -- Stage 5's stale Sequence-list bracket tag
FILE: `runbooks/dc-dc-phase4-juju-bundle-per-dc.md`.

WHAT: the top-level Sequence list still read `6. Write + apply the IPv6
family-matrix overlay [NOT YET WRITTEN -- see below]`, even though Step 6's
own body had already been correctly updated (during DOCFIX-164) to
`[OVERLAY DRAFTED 2026-07-10, NOT YET APPLIED]`. The Sequence-list's own
bracket tag was simply never touched when the Step 6 body was -- a direct,
within-file self-contradiction. Fixed to match.

### 3. DOCFIX-171c -- Stage 6's checklist overstated its own step content
FILE: `runbooks/dc-dc-phase5-dr-failover-drill.md`.

WHAT: the delivery checklist claimed Steps 4/5/8/10.2/11.2-11.4 "call
these scripts... instead of typing the command sequences by hand," but
those step BODIES (verified by reading them) still showed only raw
`radosgw-admin`/`rbd mirror pool ...` commands -- no invocation of
`scripts/dc-dc-radosgw-multisite.sh`, `dc-dc-rbd-mirror.sh`, or
`dc-dc-dr-drill.sh` appeared anywhere in Steps 1-12. Fixed by adding a
"PREFER `scripts/dc-dc-...`" pointer at the top of each of the five
affected steps, directing to the corresponding script (with its exact
subcommand) as the safer, tested alternative to typing the raw commands,
while keeping the raw commands as the reference/fallback. Updated the
checklist item itself to describe what's now actually true rather than
what was aspirationally claimed before.

### 4. DOCFIX-171d -- two DOCFIX numbers never closed out in the session ledger
FILE: `docs/session-ledger.md`.

WHAT: comparing final in-use numbers (from changelog filenames and
cross-references elsewhere) against the ledger's own tail: DOCFIX-164 (the
IPv6 overlay) and DOCFIX-167 (the bundle.yaml Designate/D-108 change) both
had ledger bullets ending in unresolved "Uncommitted -- orchestrating
session will assign the real DOCFIX number at integration time" boilerplate
-- even though both deliveries HAD been assigned real numbers and committed,
correctly cited everywhere else (the tracker doc, the runbooks, the
changelog file titles themselves). This is an integration-pass omission,
not a numbering collision (no number was reused or double-assigned) --
fixed by writing the real numbers into both closing lines. A third, lower-
severity instance (gap #15/DOCFIX-166's entry, which already cited the
correct number up front but still carried the same stale closing
boilerplate) was fixed for consistency too.

## Verification

`bash scripts/repo-lint.sh`: 0 fail, 1 documented legacy warn. No script
logic touched by this changelog -- doc/runbook prose only.

REVERT: `git checkout HEAD~ -- runbooks/dc-dc-phase0-vcloud-prep.md
runbooks/dc-dc-phase4-juju-bundle-per-dc.md runbooks/dc-dc-phase5-dr-
failover-drill.md docs/session-ledger.md` (safe).
