Problem
Initial remote connection timeout is not user-configurable from CLI. On restricted networks, connect attempts can feel hung or fail unpredictably.
Evidence:
- CLI exposes no connect-timeout flag:
src/cli/args.rs:1049-1068
- Remote troubleshooting discusses connect-timeout scenarios:
docs/remote-troubleshooting.md:10,61
Files to change
src/cli/args.rs
src/cli/commands.rs
src/client/remote_client.rs
docs/remote-troubleshooting.md
Acceptance criteria
- Add
--connect-timeout-ms (or equivalent) for remote CLI.
- Connection errors clearly indicate timeout vs auth/protocol mismatch.
- Tests validate timeout path behavior.