CodeTerm v1.15.1

Domios 1.15.1 release PR. Draft: the release SHA follows once the remaining P0 lanes land; publication and tags need the owner's GO.

CodeTerm 1.15.1

• Updates show per-component progress in a clean panel, and an update that cannot install says why
  before it stops anything. Install refusals reach the CLI with their code and how to recover.
• Plugin installs and updates swap atomically: a failed step rolls back and names the exact step.
• Account, sign-in and update failures appear as toasts instead of a titlebar slot. Small surfaces
  show compact errors; plugin rows take one line with one channel notice.
• Attachments appear at once with an uploading state and clearer kind labels.
• A tab previews files in its own AgentPad, with a shared viewport viewer and edge-aware touch previews.
• The sidebar shows each section as LABEL N with live working activity and a one-line worker summary.
• Memory Activity lists configured agents, Workers and Services, with details on click.
• Claude model and effort switches apply mid-turn when the provider supports it.
• The tray shows Admin from the server's authority.
• Immediate deliveries skip the queue, heartbeats get their own chip, and the feed never blanks.
• Escape closes the Mesh peer drawer before the view.
• The Browser surface stays stable while the window resizes.

Fixes

• Runtime launches send only the assigned-task starter; the brief travels as developer instructions (P0).
• Restored tabs bound to their own session no longer show Starting while they work, and interrupted
  tabs and routed messages wake restored tabs.
• Chat runtimes keep their declared agent runtime, and worker failures record their real reason.
• Agent provider listing never waits on a plugin VM.
• Codex edit cards read path-keyed change maps; unknown edits show their raw payload.
• Telegram file sends deliver the document or fail loudly; bridge inject failures stay typed and never replay.
• Agent notifications stay in the bell, with no strip above Chat.
• Updater template placeholders and flag values are never treated as prerequisites; relocation
  tolerates a stray provider-update.lock.
• Review hooks do nothing without checklist storage; Workers close seeded criteria by id.
• Retained exit evidence is rechecked when a process identity is lost.
• An isolated verify server opens loopback-only sockets.

Internals

• Rename phase 2: crates, packages and the contract bridge move to Domios (Herald). Phases 3-5 ship in 1.15.2.
• Envelope grammar v1 with typed segments and shared fixtures.
• Stage timing instrumentation for providers, chat start, preview and PTY.
• Typed GitHub blueprint node and reuse-first blueprint prompting.
• Release CI runs in tiers: fast checks, then tests behind them; builds start at once. Qualified dry runs
  publish through release-publish.yml; RELEASE_AUTO_PROMOTE stays off.
• The platform test classifier caches results by source digest; platform jobs compile only packages
  with platform-specific tests.
• PR-time script, gateway and frontend workflows are gone: their guards run in release-preflight and
  the fast Linux tier.
• ConPTY shell-exit diagnostics report session, host and shell context.

Plugins

Plugins release on their own train. plugins/channel.json and the manifests agree
(node scripts/release-plugin.mjs check: 7 checked):

Plugin	Version	minCodeterm	Tag
provider-claude	1.14.15	1.15.1	plugin-claude-v1.14.15 to create on master after this release
provider-codex	1.14.49	1.14.9	plugin-codex-v1.14.49 to create on master after this release

provider-claude 1.14.15 needs this app version, so its tag waits for 1.15.1 to publish.

Issues

Public issues fixed by this release are resolved from the release range with
release_issue_contract.py on the final SHA and close only after served-byte verification.

Qualification (on the release SHA)

• Canonical full regression once, then ./build.sh release-preflight.
• release.yml dry run with tests on release/1.15.1.
• Publication from the qualified run through release-publish.yml after the owner's GO.

Still to land before the release SHA

• Ember (task_bc5sz3): P0 lane-scan CPU.
• Sentry (task_ml70hr): P0 background loops.
• Possibly Herdsman (one toast system) and Tempo (--speed).