A cut waits up to five minutes for running crew runs to finish, and the tick says how many it waited on #11918

Part of #11839 (point 3). Today a release drains the process mid-run and the run is lost.

Done looks like:

• [x] src/keeper/cadence.ts holds a cut while crew runs are in flight, as it does for a snapshot, but only for five minutes from the first tick that found them; the tick line reads "waiting on N crew runs (Xm of 5m)" and cuts after the bound regardless. A release_now hotfix does not wait.
• [x] One test with the clock passed in: runs in flight hold the cut at minute 4 and release it at minute 5; a hotfix is not held. It fails without the change.
• [x] bun test on the touched tests and bun x tsc --noEmit pass.

Files: src/keeper/cadence.ts, one test. Risks: never touch the release workflow or the chart; the bound keeps a stuck run from stopping releases. Brief: a Sonnet builder (Mason or Scout).

Reviewed pull #11920 at its head: ticked src/keeper/cadence.ts holds a cut while crew runs are in flight, as it does for a snapshot, but only for five minutes from the first tick that found them; the tick line reads "waiting on N crew runs (Xm of 5m)" and cuts after the bound regardless. A release_now hotfix does not wait.; One test with the clock passed in: runs in flight hold the cut at minute 4 and release it at minute 5; a hotfix is not held. It fails without the change.; bun test on the touched tests and bun x tsc --noEmit pass..