v1.1

Corv v1.1

Corv v1.1 is a reliability and compatibility release. It keeps the existing
connection-manager workflow while hardening the paths that matter during long,
automated remote operations.

Existing v1.0 and v1.0.1 installations can upgrade in place with:

corv update

Saved connections and credentials remain compatible. The release does not
require an on-disk migration or remote software.

Highlights

Predictable output for agents

• Every agent-facing response has a fixed byte budget. Large output preserves
  its beginning and end instead of filling the model context.
• Corv retains up to 20 MiB per completed run locally. Larger logs keep the
  first 4 MiB and the final section, with explicit truncation metadata.
• corv output <run-id> [pattern] returns a bounded view and filters before
  applying the output budget.
• JSON reports run state, exact exit codes, error classification, and output
  size metadata consistently, including local and infrastructure failures.

Reliable detached work

• Long commands remain detached on the remote host and can be recovered after
  client, broker, or network interruption.
• Persisted job identity prevents an identical command from being executed
  twice during recovery.
• Completed responses are rendered from the finalized log, so late output and
  final error lines are not lost.
• Remote files are removed only after the retained local log is durably saved.

Connection and broker resilience

• SSH handshakes, control operations, and local IPC waits are bounded.
• Keepalives detect half-open connections, and dead connections receive one
  controlled redial.
• Per-connection channel limits queue concurrent work instead of overrunning a
  server's SSH session limit.
• A changed profile cannot reuse a connection or job belonging to the previous
  target or credentials.
• Updated binaries detect and replace stale resident brokers before serving
  commands.

Local state integrity

• Connection profiles, vault data, broker job state, retained logs, imported
  keys, and endpoint metadata use crash-safe atomic writes.
• CLI and TUI connection mutations share a cross-process lock.
• The vault records its key backend while preserving compatibility with
  existing encrypted state.
• Broker IPC is owner-restricted, and detached remote files use a private
  per-user directory.

New diagnostics and recovery

• corv test <name> checks resolution, TCP connectivity, jump routing, SSH
  handshake, host-key trust, and authentication without running a command.
• corv status shows warm connections and active runs without starting the
  broker.
• corv vault reset provides an explicit, confirmed recovery path for damaged
  or unavailable stored credentials.

Operational notes

• Remote command execution requires a POSIX shell. Windows OpenSSH servers are
  not supported as remote execution targets.
• Warm SSH connections do not preserve shell state between commands.
• Local run logs and completed remote remnants are retained for 24 hours.
• Release artifacts include SHA256SUMS; the installers and corv update
  verify downloaded binaries.

The release workflow runs build, vet, static analysis, formatting checks, the
full test suite, the Linux race detector, and a reachable-vulnerability scan
before publishing any artifacts.