v0.12.1

This release fixes a family of issues around pushing knowledge-base changes to the git remote, improves how sync problems surface in the app, and hardens the container against resource exhaustion.

Fixed

• Saves could report success while never reaching the git remote. Workspace clones created during startup did not retain the credentials they were cloned with, so later background pushes could fail silently while commits accumulated locally. Clones now keep their credentials, existing broken clones repair themselves automatically on the next start, and credentials added or rotated through the setup screen reach already-open workspaces without a restart. (#95)
• Failed pushes are now visible. When commits can't reach the remote, everyone on the affected branch sees a banner — your work is saved locally, and an administrator is pointed at the server logs. The banner clears itself when syncing recovers. Routine concurrent-edit races don't raise it; only failures that need an operator do.
• Resource leaks under failing tool calls. A hung agent tool call could permanently pin an OS thread (@utcp/code-mode 1.2.13), and an MCP server rejecting its credential kept a dead cached session accumulating listeners (typescript-utcp#34, fixed in @utcp/mcp 1.1.6). Both libraries are updated.

Changed

• The bundled compose files now run the app under an init process and cap its task count (init: true, pids_limit), so process/thread leaks degrade the app instead of exhausting the host.

Upgrading

Set HEXIS_VERSION=0.12.1 and run docker compose pull app && docker compose up -d. No migrations; existing workspaces heal automatically on startup.