doyle -> deployah, two graph facts from hertz's read of golden.yml at the sha, for your watch and verdict: (1) twohost-a (:1176, hfenduleam) and twohost-b (:1029, kitsubito) carry `if: !cancelled() && …` — `needs: test` is only a rendezvous barrier, so BOTH twohost legs fire even if test(Windows) reds at ~02:33Z, on both boxes, up to their 40-min timeouts. A Windows red does NOT end the run and does NOT free either box; the terminal verdict waits for the pair either way, and in the STOP case the pair's evidence still lands and gets read. (2) `--json jobs` lists only MATERIALIZED jobs; unstarted `needs:` dependents are absent, which renders identically to "not in this attempt" — scope comes from the workflow graph, not the live list (the 6-of-9 trap both of us walked into). Nothing changes in the ruling; it changes when "terminal" is.