test(remote-wake): stop pinning the readiness budget to the millisecond

ensureAwake() hands the readiness poll the caller's budget minus the wake step's own elapsed time, so on a busy runner the poll gets 39999 ms and the two tests that expected exactly REMOTE_WAKE_REQUEST_READY_TIMEOUT_MS flaked (seen in CI on #550 and in a local gate run). Both now check the value sits within a second under the budget, the shape the host-scoped wake test already uses, which still fails if the 90 s session default leaks through.

test/routes/session-routes.test.ts

@@ -2182,10 +2182,15 @@ describe('session-routes', () => {
           // The request budget, not the 90 s session default: the reverse proxy would
           // cut the request at 60 s while the session was still being built.
           expect(wakeWaitUntilReady).toHaveBeenCalledWith(expect.objectContaining({ hostId: 'hufflepuff' }), {
-            timeoutMs: REMOTE_WAKE_REQUEST_READY_TIMEOUT_MS,
+            timeoutMs: expect.any(Number),
             // The shutdown signal rides along so `WebServer.stop()` can end the poll.
             signal: expect.any(AbortSignal),
           });
+          // Not asserted to the millisecond: the wake's own elapsed time is subtracted,
+          // so a slow runner lands a few ms under the budget.
+          const [, readyOpts] = wakeWaitUntilReady.mock.calls[0] as unknown as [unknown, { timeoutMs: number }];
+          expect(readyOpts.timeoutMs).toBeLessThanOrEqual(REMOTE_WAKE_REQUEST_READY_TIMEOUT_MS);
+          expect(readyOpts.timeoutMs).toBeGreaterThan(REMOTE_WAKE_REQUEST_READY_TIMEOUT_MS - 1_000);
         } finally {
           startShell.mockRestore();
         }