Files
Neil a3493c61aa fix(cli): keep SSH connected authoritative and separate the probe budgets
Review follow-ups on the paired-host listing:

- ssh.listTargetSummaries went back to reporting connected:false when no
  connection object exists. That is a local fact the app knows, and omitting
  it made every target read as unknown right after launch or an ssh-config
  import. It also defeated the CLI short-circuit, adding one useless
  ssh.getState per idle target.
- The target enumeration call keeps the client default timeout; only the
  per-target state fan-out is charged against the 5s budget, so one busy
  main process no longer drops the entire SSH inventory into a warning.
- An RPC-level rejection proves contact, so it reports connected:true with
  probeError status_rejected instead of looking like a network failure.
- host list help no longer contradicts its own output on --environment.
2026-09-07 19:45:58 -07:00
..