Configuration's own default (1s) is tight for a WAN link doing a
client-cert TLS handshake - occasional latency/broker-load spikes can
hit it even when the broker itself is healthy and otherwise reachable
(e.g. via a separate browser WSS connection), producing an
intermittent raw "Connection timed out" instead of the graceful
AgentTimeoutException callers actually handle. This is the connect
step only, distinct from dispatch()'s own per-request reply timeout.