fix(cli): clear connection timeout timer to prevent 5s exit delay

[dkisser]

Summary

Usage: bridge [args]

Commands:
up Start ws-server and local-proxy
down Stop both services
restart down then up
status Show service state
logs [name] Tail logs (ws-server | local-proxy)
update [version] Upgrade to a release (default: latest)
doctor Diagnose the install
uninstall Remove ~/.browser-bridge/ (use --yes to skip prompt)
version Print installed + latest version

Browser commands (when services are running and a browser is connected):
browser:list List connected browsers
navigate Open a URL in the current tab
click Click an element
type Type text into an element
screenshot Take a screenshot
See 'bridge --help' for the full list. CLI commands that open a WebSocket connection were hanging for ~5 seconds after printing output. The connection-timeout +setTimeout+ was never cleared once the socket reached the OPEN state, so Bun kept the process alive until the timer expired.

Changes

• Save the connection timeout handle in +listBrowsers+ and +sendCommand+ and +clearTimeout+ it as soon as the socket opens.
• Remove the stray +console.log('Connected to server')+ from the WebSocket client.

Verification

• +time bun apps/cli/src/index.ts browser:list+: dropped from ~5.0s to ~90ms.
• +time bun apps/cli/src/index.ts --browser <id> pageinfo+: dropped from ~5.0s to ~90ms.
• +bun run type-check+: passes.
• +bun test+: 49 pass, 0 fail.

Test Plan

• Manual timing of +browser:list+ and +pageinfo+
• Type check
• Unit test suite