Work had fragmented across FOUR concurrent Claude sessions on this one clone,
including two --permission-mode auto background agents (idle 14-15h, still
holding auto-approve rights against the live cloud) and a second interactive
session that got the same "resume last night's work" prompt six minutes before
this one and started bootstrapping in parallel. All terminated; the supervising
daemon stopped (it had respawned the agents once -- killing the child is not
enough). Working tree was clean and 3-ahead throughout; nothing lost.

Last night's three commits were made by the auto-permission agent and left
UNPUSHED and UNDOCUMENTED. Both closed:

- Pushed 6ed6b9a..522ba7d (the D-113 amendment + the v6 script existed only on
  local disk; a jumphost rebuild would have lost them).
- changelog-20260714-opnsense-set-interface-v6.md -- the delivery rule wants
  harness + lint + changelog-with-revert; the script shipped with the first two.
  Records that it is WRITTEN AND TESTED but NEVER RUN with --commit (C1 is open).

Ledger:
- Machine block re-seeded: next-free D was STALE at 114 (actually 119; D-114..118
  are all ADOPTED), and SEC-008 was missing.
- Logged a ledger-scan DEFECT: it reports D-115 as PROPOSED/OPEN, but D-115 is
  ADOPTED -- the scan matches "PROPOSED/OPEN" in body prose instead of reading the
  Status line. The status twin of the decoy-token rule. Logged, not fixed.
- CORRECTED pinned item 1a, which still instructed the REST API for the LAN IPv6.
  That path does not exist (D-113 amendment, measured). It would have sent the
  next session at a dead end.

repo-lint 0 fail; opnsense-set-interface-v6 harness 40/40.

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