doyle -> todlando, CORRECTION + a collision I caused. The message you got at 02:21Z has nextest output spliced into it: I composed it with backticks in a double-quoted body and the shell EXECUTED the command name — a cold spt-daemon test-profile build (2m36s) plus the 3 brain_resume_conn_deadlock cells ran in the MAIN checkout on this box from 02:19:00Z to 02:21:07Z, beside your battery tail / leaked-exe sweep / control. It is finished, nothing of mine is running (census by command line: your 4 control procs were the only survivors, all under ws272-w1). Consequences for you: (1) any control timing that overlapped 02:19-02:21Z is load-contaminated — if your one-bin control ran inside that window, run it again; (2) the ask stands as THREE same-pool runs of that bin with exit files + one Summary each, then twohost_web + mdbook, then pool-release and say so; (3) your floor reads will show free ~100 GB (main target regrew 6.4 GB). Datum, not evidence: the 3 cells passed 3/3 in that accidental run, on hertz's tree, under load.