D-060: revert to Pattern A; supersede D-057/D-058 ...

Revert provider NIC to Pattern A (MAAS-built OVS br-ex) on the existing D-052/D-053 scheme. bundle.yaml clean bf7de5a checkout (provider-public x11, VIP triple .4/.8/.12, all 4 br-ex MACs); lib-net.sh + carve back to D-052/D-053; NEW provider-bundle-check.py gate; standup retargeted; teardown.sh + teardown runbook updated. Retire: phase-00-maas-recidr.sh, provider-vip-standup.sh, d057-bundle-check.py, and the 3 provider-vip/reconfigure runbooks.

Update v1-redeploy-changelog.md

decisions and changelog updates

MAAS script updates

Phase 0 updates

Phase 0 updates

Create README-D057-PACK.md

Provider VIP carve updates

Update v1-redeploy-changelog.md

Fix scripts

Phase 6 scripts

Phase 6 updates

Phase 6 updates

Fix repo

New Phase Scripts

Phase 5 updates

Update v1-redeploy-changelog.md

Phase 3 updates

Update v1-redeploy-changelog.md

MAAS script updates

MAAS script changes

MAAS script updates

Fixed merge issue on changelog

MAAS scripts

MAAS scripts

docs: add v1-redeploy-changelog.md (running log; stages D-054 + DOCFIX-039)

D-053 rename network space fabric-data -> data-tenant Bundle: 4 bindings + 2 header-comment lines (nova-compute:neutron-plugin, ovn-chassis:data, ovn-chassis-octavia:data, octavia:ovsdb-cms). Space-name only; subnet/VLAN/role/binding-semantics unchanged. Live MAAS already on data-tenant; bundle now matches. Verifier 8/8. docs: D-053 appended (D-052 body left intact, append-only).

D-052 explicit network-space bindings + D-051 SCS Domain Manager policy ...

normalize docs/netbox-vip-queue.md to LF; .gitattributes explicit text for md/yaml/sh/py (text=auto mis-flagged the mixed-ending file)

Post deploy changes