MCP Inspector had no connect timeout at all, and now defaults to 30 seconds.

connectionTimeout defaulted to 0, which InspectorClient.connect() read as unbounded, so the only thing ending a hung handshake was the SDK's 60s per-request timeout on initialize, which doesn't cover transport.start() and reports a misleading "Request timed out." PR #2362 sets a 30s default and keys the post-timeout teardown to the timer firing rather than to connectionTimeout > 0, because with a real default the old gate would tear down every failed connect including a recoverable 401. Measured against a server that accepts TCP and never answers: 60.5s before, 30.4s after.