v0.31.0

What's new

• The hosted MCP server keeps a tool client per person. It builds one per person and catalog revision and reuses it until a tool they may read changes, one of their secrets changes, or it sits unused for an hour, so a warm request answers in the time of the request alone instead of rediscovering every tool. Keys, metering, audit and revocation stay per request. (#437)
• Pages call the viewer's tools. An HTML page on the file page gets window.bevel.tools (search, info, call, chain), answered as the viewer with the same tools and refusals their agent gets. The first call that may write asks the viewer once per page view; on the embed or a preview the page is told tools are not available and can offer "Open in the platform". Every page call is in the Audit log under the viewer, with the page's path as the agent. (#437)
• Agents read history and sync their drafts with tools. Five workflow tools, on every agent connection: list_file_changes (a file's commits, who made each and when), read_file_at (the file at a commit, or at another branch's published tip), compare_file (the diff of a commit, or of a file between two branches), branch_status (where a draft stands: ahead, behind, what its change request would carry) and update_branch (bring the target, or the draft's own shared state, into the draft as a merge commit, and publish it). Conflicts are resolved with update_branch too: the first call describes every conflicted file and undoes the merge, a second call with a resolution per file (resolved text, one side kept, or the file deleted) lands and publishes it. Nothing is ever left half-merged on disk, every read is authorized at the exact commits it serves, and a resolution takes the same gates a save takes. This replaces the git reach agents lost when the internal shell tool was removed in 0.30.0. (#439)
• Page titles keep the tails of g, y and p. Titles that were cut short with an ellipsis also lost the bottoms of their letters; they now have room for them without moving anything else on the page. (#404)

Upgrading

No compose change; the database migration 0018_agent_events_page runs at start. The new agent tools appear on every agent connection after the restart. If your in-app agent prompt still tells the agent to run git, point it at the tools instead; the agent guide describes them.

The Docker image is ghcr.io/bevel-software/hexis:0.31.0; the npm packages are @bevel-software/platform-*@0.31.0.