Two defects in the C1 changelog, both found on review:

1. The RA advertises `RDNSS 2602:f3e2:f01:1` -- a field we never set; OPNsense
   auto-defaulted it to the edge's own LAN v6 address. Same failure class we avoided
   with mode=unmanaged (advertising a service that may not exist), one field over,
   and it slipped in BECAUSE the field was left unset. CHECKED: the edge's Unbound
   really does answer DNS on that v6 address (dig from voffice1 resolves; it works
   with no v6 egress because Unbound queries upstream over v4). Correct -- but by
   luck, not design. Set RDNSS explicitly when this RA config is reused on the
   DC0/DC1 edges at Stage 3.

   Bonus: this makes "services binding v6" EVIDENCE rather than inference -- a real
   v6-bound service answering real queries.

2. The address-revert line said `--commit 10.10.0.1 lan :: 64`, which does NOT clear
   the field -- it would SET the unspecified address. The script cannot express a
   clear at all (4 args required, address validated). Shipping an unverified revert
   is exactly what the delivery rule exists to prevent. Replaced with the honest
   GUI clear + a note that a --clear flag would be the real fix.

repo-lint 0 fail.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>