dc0 controller REBUILT from MAAS via Path C; environment ready for the deploy ...

Operator ruling: remove the machine and rebuild fresh from MAAS rather than
troubleshoot or gracefully repair. Executed as Path C, every gate captured.

C.2b unregister (client-side) then MAAS RELEASE, not delete -- release returns the
VM to Ready while preserving the interface carve and the juju-controller tag that
bootstrap targets, and MAAS re-images at bootstrap, which is the fresh rebuild.
C.3: 10 machines, count unchanged, no cascade, tag survived.

C.5 proved the credential WORKS rather than merely exists: key extracted without
being printed, AUTH OK against the dc0 region endpoint, rack identity hot-kid/
c3aqh8 confirming DC-local rather than Office1, superuser scope, temp profile
logged out. The cloud definition and credential survived the unregister -- they
belong to the client, not the controller.

C.7 bootstrap complete EXIT 0 in ~6 min onto the tagged VM, both ruled constraint
flags plus --bootstrap-base.

C.8 empirically confirms the warning: a fresh controller has NO model-defaults --
all five keys measured empty before setting. Proxies set at controller level and
read back on content; apt-mirror deliberately left unset per D-135 amendment (b).
The snap keys had never been set on the OLD controller either, so this closes a
gap rather than restoring one.

C.9 add-model with defaults INHERITED; spaces gate PASS 0 fatal.
C.10 all five staged inputs re-verified against HEAD; machines overlay re-staged
after the origin block was deleted at convergence.

Step 4.2 dry-run gate ALL PASS: nine constraints all this DC in the 3/2/4 split,
nine machines, no overlay path error (the three ERROR greps are the documented
benign R11 unmarshal pair and RPC teardown noise). Four designate applications
present, correct under D-106.

Deploy (4.3) NOT run -- gated mutation.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf