|
Values-file provenance symmetry; repair the mangled ledger rotation note
Two small corrections found on review. (a) The values file recorded `apex_record` only on the dual-family path, so the dc0 v4 file carried no provenance at all -- and the asymmetry would have read as a bug once commit 2 gives dc1 the apex field. Added `source_v4`, recorded on BOTH families, because the v4 prefixes come from lib-net.sh and NEVER from the apex: a values file carrying only `apex_record` misattributes half its own inputs. Re-derived dc0; the rendered overlay is byte-identical (a3b30e40...) and dc1 still reproduces exactly. (b) docs/session-ledger.md's third rotation note was left MANGLED by an earlier edit -- a sentence broke off mid-number and ran into a stray fragment of the 2026-07-25 MAAS-admin-recovery summary. Flagged at this session's open; repaired here rather than only reported, with a note saying so and a pointer to that summary's archived body. Gauntlet ALL GREEN (85) on vcloud; repo-lint 0 fail. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf |
|---|
|
|
| docs/session-ledger.md |
|---|
| render/values/vr1-dc0-vips.yaml |
|---|
| scripts/render-dc-overlays.py |
|---|