Operator reconsidered D-101's "PXE is v4-first" clause on the pass6 fresh-
feasibility evidence (not the prior ruling). GA-R5 exchange, exact utterance:
"Adopt v6 (gated on live test)".

RULED: metal-admin node commissioning for the 10.13 redeploy TARGETS IPv6 (UEFI
+ DHCPv6 + HTTP boot), GATED on a one-node canary (DHCPv6 -> UEFI HTTP boot ->
enlist -> commission -> READY, captured) with v4 fallback before any fleet
commit (hard rule 2 -- no fleet commit on an unproven-on-this-cloud path). The
ungated full-fleet option was NOT chosen.

Basis: pass6 research found no MAAS-side blocker at 3.7.2 for DHCPv6
commissioning (historical bugs closed 2017/3.1), rack<->region v6 feasible-now
(source prefers AF_INET6), and the only hard blocker is legacy-BIOS PXE (Intel
firmware) -- avoided by UEFI, which we set on the VR1 node VMs. D-101's clause
was an unmeasured judgement, not a capability ceiling.

Reconciliation: AMENDS D-101 (PXE-v4-first clause only; IPv6-primary principle +
family matrix unchanged -- this ADVANCES "v6 wherever possible"); CONSISTENT
D-139 (metal-admin plane stays dual-stack; only the boot-path family shifts);
moots the standalone "soften D-101 PXE wording" DOCFIX (this amendment IS that
correction, now ruled). provider-public needed NO reconsideration -- D-101
already rules it dual-stack + native v6 GUA ext_net (v4 retained for external
v4-internet only).

Owed at redeploy design time (logged, not built): UEFI (OVMF) node-VM loader;
DHCPv6 + MAAS HTTP-boot on the metal-admin commissioning range; the canary test
+ captured evidence as a new gate. Still-owed DOCFIX (independent of A): the
stale OVN "No" row in charm-ip-family-compatibility.md.

CURRENT-STATE updated in the same commit (GA-R1 C1). repo-lint 0-fail.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fg98z7QyzwYUs8fsWCn728