Fork: 0
OpenStack / openstack-caracal-dc-dc
Transfer to URL with SHA Find file
Newer
Older
openstack-caracal-dc-dc / docs / changelog-20260710-skill-vr1-awareness.md
@JANeumatrix JANeumatrix 5 hours ago 4 KB DOCFIX-177: make the skill and runbooks/README.md aware the VR1 DC-DC track exists
Raw Blame History

Changelog 2026-07-10 -- skill/reference VR1 DC-DC awareness (DOCFIX-177)

No live infrastructure touched. Found while the operator was heading to the vcloud host to begin real execution: .claude/skills/openstack-cloud-ops/ (loaded before any nontrivial task, per this repo's own CLAUDE.md) and runbooks/README.md (what the skill's routing table points to for "Deploy / redeploy / teardown") were both SILENT on the entire VR1 DC-DC track -- zero mentions of docs/dc-dc-deployment-workflow.md, the seven dc-dc-phase*.md runbooks, dc-dc-teardown-rollback.md (DOCFIX-176), or opentofu/. A fresh session reading only the skill (which is exactly what happens at session start / after compaction) would have been routed straight to VR0's phase-01..08 runbooks with no indication the DC-DC track -- the actual live mission for today -- exists at all.

Fix

  1. runbooks/README.md: new "VR1 DC-DC track" section -- a table mirroring the existing VR0 "Phases" table's format, listing all 7 Stage runbooks + dc-dc-teardown-rollback.md, explicit that Stage numbering here is a SEPARATE sequence from the VR0 phase-NN numbers above it (they share a repo, not a numbering scheme), and a pointer to docs/dc-dc-deployment-workflow.md as the actual master tracker (stage status + tooling gap register) rather than duplicating that content here.
  2. .claude/skills/openstack-cloud-ops/SKILL.md: routing table gained a dedicated VR1 DC-DC row (previously the "Deploy / redeploy / teardown" row only pointed at the VR0 sequence); "Standard loops" gained a second "Deploy loop (VR1 DC-DC)" entry alongside the existing VR0 one, including the fix-forward-before-teardown reminder from DOCFIX-176's rollback decision tree and the opentofu UNVALIDATED caveat.
  3. references/environment.md: "The two deployments" section (VR0 + Roosevelt) became "The three deployments" -- VR1 DC-DC added as a pointer-only entry (this file stays VR0's own detailed ground truth; VR1's facts live in the master tracker, not duplicated here). "Repo map" section gained a VR1-specific addition listing where the new docs/ runbooks/opentofu/scripts actually live.
  4. references/troubleshooting.md: one paragraph clarifying that appendix-A-troubleshooting.md is VR0-specific and the VR1 track has no incident index yet (nothing has been executed) -- so a future troubleshooting session doesn't waste time searching appendix-A for a VR1-specific symptom that was never logged there, and knows to log a genuinely new VR1 finding as a DOCFIX/D-NNN candidate instead of assuming it must already be documented.

Checked, not changed: references/operating-discipline.md's "Session continuity" section was re-read against tonight's actual practice (ledger updates at every deliverable, ledger-scan.sh reconciliation) and found accurate -- no drift to fix. references/script-authoring.md is generic command-block/gating discipline that applies equally to both tracks -- correctly track-agnostic, left as-is. references/opentofu-provider-docs.md is provider-research content (already VR1-authored this session), not topology/routing content -- out of scope for this pass.

Also fixed before this delivery: unpushed commits

Found git status showing main 2 commits ahead of origin/main (DOCFIX-174 and DOCFIX-175/176) -- since the session bootstrap the operator runs on the vcloud host starts with git pull, these would have been invisible there this morning. Pushed to origin/main before starting this delivery.

Verification

bash scripts/repo-lint.sh: 0 fail, 1 documented legacy warn (ASCII-only convention held across all edits). No script logic changed -- doc/runbook/ skill prose only, no test harness applies. Full gauntlet re-run: same pre-existing environment gaps as every prior check tonight, zero regressions (see this delivery's session-ledger entry for the exact count).

REVERT: git checkout HEAD~ -- runbooks/README.md .claude/skills/openstack-cloud-ops/SKILL.md .claude/skills/openstack-cloud-ops/references/environment.md .claude/skills/openstack-cloud-ops/references/troubleshooting.md (safe -- routing/reference content only, no live infrastructure or script behavior depends on any of it).