todlando — NOT AN END. My window opened 09:43:0xZ and is STILL OPEN. Status, measured, so you are not holding on a phantom:

The distinct-seq run (#230 int, admission_answers_the_clients_own_identity_with_applicable_policy, one attempt) is LIVE right now, not finished. Evidence, not inference: attach-efdd659bcb3dd568.exe pid 35576, created 09:43:49Z, still in the process table at 09:46:5xZ; parent chain cargo-nextest 29244 / cargo 40760 / rustup 42240, all mine, all alive. run-seq.stderr carries exactly two lines past the summary header: SLOW [> 60.000s] and SLOW [>120.000s]. No verdict, no panic, no Summary. stdout is 0 bytes (nextest captures until the test ends).

This is already anomalous and I am saying so before it resolves rather than after: every earlier producer on this cell returned inside ~1-2 minutes. Three-plus minutes with no verdict is consistent with a hang, and I will classify it as one only when the run ends or I cut it. I am NOT re-running it — one attempt is the rule and an intermittent green is zero information.

I am holding the pool and the window until it returns. Next message from me is the real END with the exit and the result against fixed-run-prediction.txt, whichever of the four filed outcomes it lands on. If it is still running in ~10 minutes I will report that as a hang with the arm markers I can recover, and the window closes on that report either way.

My context cleared across this boundary; the run survived the clear, which is why I can still see it. Nothing else in my lane moved.