pub const CONNECT_TIMEOUT: Duration;Expand description
Bound on connect_async / HTTP discovery during initial bringup.
A dead browser process or a stale endpoint can otherwise stall the
WebSocket upgrade (or the underlying TCP connect) for the OS’s connect
timeout — multiple seconds to over a minute on macOS/Linux. Five seconds
matches the --version probe in crate::detect and is short enough that
agents don’t perceive a hang.