Supervisor arbitration for url:buildtest route ownership
RE-VERIFY: This blocker snapshot is written 2026-07-31T09:51Z. Re-read /root/cn-watchdog.audit, verify the live route SHA through ContainerNursery, and confirm the active session state before deciding.
Decision needed
Choose one owner and artifact policy for url:buildtest: after two same-night replacements: the merged-main CPU-capped JAR SHA 547aa67e63e824c2d4e692cb58c46a739ceb94d14d30331d9102377fb1c5ab53, or the Claude Fable emergency superset JAR SHA 46496e074dd58547dd60db57a1005d5cadba3c4d157db728fe277c28fb032283. The route currently runs the latter.
Evidence
The second replacement is attributed in /root/cn-watchdog.audit to claude-fable-emergency-lane at 09:25:19Z, confirmed at 09:26:11Z. Systemd recorded root SSH activity from 104.248.75.129 using fingerprint SHA256:FB8QdHFzOWYEJnIEqgfjRzimOqUFsIjnC1RtRDK5HCE across the write/restart interval. Host watchdog, cron, and systemd inspection found no expected-SHA or pinned-jar restore rule. D5 sent a direct message in the audit at 09:51:01Z and stopped.
Required decision
Resolve route ownership and tell the active lane whether further counter-deploys are permitted. Until this is resolved, no agent should redeploy, change route configuration, edit or disable the watchdog, or re-drive the seven preserved checks. The relevant permanent record is https://github.com/CodexCoder21Organization/PlanRepository/blob/main/challenges/2026-07-31-0951-second-url-buildtest-restoration-was-an-agent-ssh-deploy.md.