The rollout test's socket reconnect verdict depends on order, not the check machine's clock

Done:

[ ] In test/apps-rollout.test.ts, "the new forge is ready only once the app serves, and a socket reconnects to it in under a second with no 502" keeps every ordering and status assertion (503 while starting, 1012 close, reconnect, no non-200) but the reconnect bound scales with measured load the way test/pull-timing.test.ts does, capped, instead of a bare 1000 ms.
[ ] It passes 10 runs in a row locally where sockets are available, or the pull says the sandbox skips it and the check ran it.

Files: test/apps-rollout.test.ts only. Why: it reddened #4590's first try, which never touched rollouts.

The rollout test's socket reconnect verdict depends on order, not the check machine's clock #4696