v0.145.0

Install or update: npm i -g cotal-ai@0.145.0

Restart running Cotal processes and agent sessions to use the new code.

What changed

• A managed Claude Code seat wakes on peer messages again.
• Report a TCP listener that does not offer required TLS as tls-unsupported, rather than unreachable.

Every change in full

• A managed Claude Code seat wakes on peer messages again. Claude Code binds the server:cotal wake channel only to a server its own configuration declares, the user config or the project's .mcp.json, and never to the launch's --mcp-config entry alone; a seat launched without one joined the mesh, reported idle and let every turn and direct message expire. cotal setup and cotal update now register the plugin's server as the user-scope MCP entry cotal (claude mcp add --scope user, the same command and arguments as the plugin's own server, so a plain session runs one process), a carried seat's private home declares it, cotal status reports it under Claude wake channel, and a managed launch whose user config and project .mcp.json declare no cotal server is refused with a message naming cotal setup. Run cotal update on each machine that spawns Claude seats; docs/UPGRADING.md has the details.
• Report a TCP listener that does not offer required TLS as tls-unsupported, rather than unreachable. Preserve the registration and show the transport mismatch in raw connection, registration and status diagnostics. Consumers of ProbeResult must handle the new failure reason.

What's Changed

• fix(connector-claude-code): register the user-scope cotal entry the wake channel needs by @davidfarah2003 in #5852
• fix(core)!: distinguish unsupported TLS from an unreachable broker by @davidfarah2003 in #5850
• chore(release): version packages by @davidfarah2003 in #5853

Full Changelog: v0.144.0...v0.145.0