told-by and standing-every-process are green in any order and on any shard, or each is quarantined under its own issue #2070

Split from #2037. Both attempts at #2037 (pulls #2053, #2060) went red on tests that were already in GATE: "two forges in one process keep their own error and refusal signals" (test/standing-every-process.test.ts) and "who told and who shipped > (unnamed)" (test/told-by.test.ts; it also matches test/vitals.test.ts). The gated set was identical. Only the order changed, from GATE's hand order to name order, so these files landed on different shards beside different files. They depend on what ran before them.

Done looks like:

• [ ] bun test --randomize with five different seeds, run on these files together with the files they share a shard with in name order, is green every time. Or the shared state (module-level singletons, env, a cached signal store, the clock) is reset in the test's own setup.
• [ ] The "(unnamed)" test in told-by gets a name, so a red names it.
• [ ] If a file cannot be made order-independent in one run, it goes to EXCLUDED in scripts/gate.ts with its own new issue, not left flaky.
• [ ] The pull says which shared state caused it.

Files: test/told-by.test.ts, test/standing-every-process.test.ts, maybe test/vitals.test.ts, and the src module whose state leaks. Risk: do not weaken an assertion to make it pass.