The previous commit edited these three files through a JSON round-trip that
reindented them to one space, which made dns-config the only case formatted
differently and buried a three-line change in 220 lines of whitespace.
The comparison unmarshals before diffing, so the layout was never load-bearing;
this is purely about the diff a reviewer has to read. Same content, edited in
place this time.
The drift guard asserts that the full, envelope and legacy paths produce the
same PeerConfig for a fixture. The new destination field was invisible to it:
the frozen legacy implementation never emitted it, so a fixture with a non-empty
account URL would have made legacy disagree with the other two, and no fixture
set one, so nothing failed and the field had no coverage at all.
The legacy path now emits the account setting, which is what AddressV6 already
does. It does not take the deployment-wide default the live path falls back to,
because the harness runs that path with no server config, so the two agree on
every fixture.
The dns-config case pins an account-level URL. Removing the legacy line makes it
fail on the legacy mode for that exact field, which is what makes the fixture
worth having.
riccardom