test/crew.test.ts runs under 10 s: its archive test waits for the crew, not a fixed 6 s #9086

Intent: the gate stays fast and honest.

Today bun test test/crew.test.ts takes 21.6 s for 4 tests (measured on this branch). The last test ("a run queued before Archive is cancelled…", ~line 247) calls await Bun.sleep(6_000) after Wake to show the cancelled run is not revived, then waits up to 60 s more per settled call.

Done when:

• [x] The 6 s sleep is gone: the test drives the crew's next pick directly (or waits on the event the crew emits when it picks) and then asserts the run is still cancelled. Nothing it asserts is weaker.
• [x] bun test test/crew.test.ts reports under 10 s on the check, and no test in it over 5 s; the pull quotes before and after.
• [x] If the stand-in harness or its pick interval is the rest of the cost, it is shortened for the test only through an existing knob, never by changing production defaults.

Files: test/crew.test.ts, maybe a test helper under test/helpers/. Risks: the test must still fail if Wake revives a cancelled run: show it by breaking that once locally and saying so in the pull. Fits: a builder (torque/scout).

Reviewed pull #9089 at its head: ticked The 6 s sleep is gone: the test drives the crew's next pick directly (or waits on the event the crew emits when it picks) and then asserts the run is still cancelled. Nothing it asserts is weaker.; bun test test/crew.test.ts reports under 10 s on the check, and no test in it over 5 s; the pull quotes before and after.; If the stand-in harness or its pick interval is the rest of the cost, it is shortened for the test only through an existing knob, never by changing production defaults..