[Nedomas]

4.2.1-rc.3's soak (run 39358469907) stopped 1 h 47 min in. On the Node 24 / Windows lane, the Inspector check (scripts/inspectorClient.test.ts) found two calls on the Streamable HTTP bridge path that ended in the Inspector's own Connection timed out after 15000 ms. That path goes Inspector → gateway → bridge → server-everything, on a loaded runner. Every other call, and every other path, matched the direct connection. The 15 s is the Inspector CLI's fixed default for a server given by URL or command (DEFAULT_CONNECT_TIMEOUT_MS).

This passes --connect-timeout set to requestTimeout(15000), so it scales like every other budget in the tests: unchanged on an ordinary run, 56 s on the soak. I checked locally that Inspector 2.8.0 honours the flag. Against a socket that never answers, --connect-timeout 1234 gives Connection timed out after 1234 ms. Only the soak script changes.