v2.0.4

Same session. Same links.

A network disconnect should not turn a running terminal into a different
sharing session. v2.0.4 separates the host's identity from its SSH transport.

Reconnect continuity

• Automatic host reconnects retain SSH read-write, SSH read-only and web links,
  for both named and unnamed sessions.
• A cryptographically random 256-bit host secret stays in memory. The relay
  derives independent 128-bit viewer capabilities; possessing a viewer token
  does not authorize reclaiming a host's identity.
• Named RW links use a 32-character hexadecimal prefix instead of five digits.
• A session remembers its actual assigned name, including collision suffixes.
• Alias replacement and cleanup are serialized and ownership-aware: an old
  daemon cannot erase the replacement's links. Garbage collection follows the
  same locking rules without blocking the relay's accept loop.
• If a name is claimed by an unrelated host during a gap, the client warns
  when its RW link changes. Names are not permanent reservations.

Private by design

The client negotiates support before sending its identity in a dedicated
private protocol message. That message never enters viewer streams or their
replay buffers. Host configuration commands are also excluded from those
streams, and private option values are no longer logged.

Upgrade notes

Upgrade the hosting client and relay to v2.0.4 or newer for continuity.
Older versions remain compatible but keep the previous reconnect behavior.
Restart an already-running host once to begin using the new client.

Detaching and reattaching to the same host preserves its identity. Ending the
host process and starting a new one intentionally creates fresh credentials,
even with the same session name. No reconnect secret is written to disk.
RO named links and bare-name web URLs remain name-based and are not secrets.

Verification and downloads

Regression coverage includes repeated reconnects, overlapping old/new daemons,
name collisions, full restarts, maximum-length names, capability derivation,
viewer-token impersonation attempts and private-message filtering.

The release is published only after Linux and both native macOS architectures
build, server/site deployment succeeds, and the full binary manifest is
verified. All twelve binaries are accompanied by checksums.txt.