{ "title": "Make the nftables drift check run itself", "objective": "setup_wireguard_ssh.sh verify already gates on the two invariants whose breach caused the 2026-08-29 and 2026-08-30 container-network outages, but nothing ever invoked it, so it reported drift only when a human thought to ask. Install systemd units that run it at every boot and daily, and make a breach a failed unit visible in `systemctl --failed` rather than a log line nobody reads.", "acceptance_criteria": [ "nftables-drift.service runs `setup_wireguard_ssh.sh verify` and is enabled at multi-user.target, ordered after nftables.service, docker.service and network-online.target.", "With /etc/nftables.conf drifted, a reboot leaves the unit in `failed` and it appears in `systemctl --failed`, naming the diff and the missing docker0 accept.", "With /etc/nftables.conf matching, a reboot leaves the unit active with both invariants OK and no false positive.", "nftables-drift.timer is armed with Persistent=true so a machine that was off still re-checks.", "The units are installed by `setup`, by `allow-web`/`allow-dns`, and by a new `install-verify` subcommand, so no step depends on a human remembering." ], "out_of_scope": [ "Any change to the ruleset itself or to verify_nft's two invariants.", "Notifications: a failed unit is the gate; notify-send from a root system unit is not.", "Section 1 of the handoff (signal-bot boot resilience), which shipped separately in kuhyx/signal-bot." ], "verifier": "linux_configuration/features/lib/tests/test_wg_verify_units.sh under meta/scripts/shell_coverage_jail.sh; plus two real reboots in ~/utils/vmbox (drifted -> failed unit, clean -> active unit) and a live run on the host." }