deployah — a4 DISPATCHED 01:2xZ. Operator answered: fire now, box as-is. gh rerun of the failed jobs, exit 0, sha VERIFIED unchanged 25e6001585ed0cd495a72c7634dded9dd207bdae, run in_progress. ALL SEVEN GATES True, printed before the command fired: gate1 run_terminal completed, non_terminal 0 (this IS the twohost-b-terminal precondition) gate2 runner_quiet hfenduleam busy False, online gate3 queue_empty foreign non-completed 0 gate4 free_space 211777974272 B = 197.23 GiB gate5 no_user_cargo user-rooted 0 of 0 total, parent-chain-root attribution gate6 kitsubito_quiet builders 0, load 0.01 gate7 acl_open verifier exit 0 RECORD LINES, as you asked, quoting rather than inferring: defender exclusion for runner work dir: unknown (non-admin read returns: N/A: Must be an administrator to view exclusions) defender real-time protection: True qbittorrent at dispatch: RUNNING pid=47056 cpu_s=6095 So a4 runs WITHOUT the exclusion confirmed and WITH seeding live. The operator chose that knowingly after I put the three options to him with the contention risk stated. If a4 reds on a Phase B cell the record already says what the box was doing — nobody has to reconstruct it, and it does not become an argument about whether we checked. SCOPE: only test(Windows) was failed, so rerun-failed re-runs exactly that ONE job. twohost-a and twohost-b are NOT re-run and stand green from a3 on the reads you accepted (helper 6.11 s; role_b 5/5 from B's own served count). I will state that explicitly in the verdict rather than let it read as a4 having re-proved them. Expect ~45 min, no twohost leg. WATCH: bwy99mxii, armed AFTER the dispatch, jq-free (gh -q in-process), first emission a REAL event through the real path carrying status, non-terminal count and the completed set. Its previous incarnation's first line was the terminal-state check, so this one cannot exit on a3's staleness. ACCEPTANCE a4 as you worded it: the seven with criterion 4 replaced by "Summary 2, and BOTH previous victim cells re-executed and PASS" — webserve_attachment_e2e arm 12 AND mesh_recovery roster_route_survives_a_transient_dial_failure_with_discovery_disabled. Criterion 2 rides Phase B by construction, so a green Phase B is what finally lets the Windows docs-drift gate run for the first time at this sha. STOP holds: any Phase B red = STOP, no a5, respin onto a new head with your rider 5 and hertz's rider 3.