chore(release): prepare v0.7.2

[snimu]

Patch release. Bug fixes, small UX additions behind existing surfaces, and a dependency consolidation; no breaking changes, so patch per the no-major-releases policy.

Why this one matters beyond the changelog

The headline is the stuck-worker family (#850 → #851 → #852): workers whose stops timed out or whose processes died could stay registered forever, showing sessions as ready that could never respond and leaving "Session worker is not connected" states that #836 (shipped in 0.7.1) only partially covered. This stack makes worker lifecycle reporting truthful, finalizes timed-out stops once the process actually exits, and self-heals stale registrations on resume. Plus #838: queued steering/follow-up messages can now be edited in place (Alt+Up/Alt+Down browse, Enter/Alt+Enter apply) and interrupts preserve the queue.

Contents

PR	change
#838	edit queued messages in place; interrupts preserve the queue
#850	accurate worker lifecycle: new stopping state, disconnected workers never ready, stopping workers hidden from live sessions
#851	timed-out worker stops finalize in the background instead of stranding registrations; zombies no longer count as alive
#852	open/resume self-heals stale worker registrations
#1226	Down Arrow stays in a nonempty prompt until the cursor reaches the end
#767	independent expand/collapse for tool calls, a2a messages (ctrl+p), and thinking
#1135	agents view keeps expansion state when leaving and returning
#647	login URL copy action
#521	privacy-safe pseudonymous analytics with disclosure and opt-out
#846	Homebrew installs no longer self-update the Cellar keg
#772	expanded sent a2a messages show only the message text
#632	consolidated dependency updates (undici 7.29, biome 2.5.5, marked 18, typescript 7 dev-only, typebox 1.3, aws bedrock sdk, vitest 4.1.10, brace-expansion, ip-address, postcss transitives)
#1132	stale Gemini test model (test-only, no changelog entry)

#838, #850, #851, and #852 merged without changelog entries; this PR adds them under 0.7.2.

Version bump

Lockstep across the root package and the four published packages: agent, ai, coding-agent, tui. Example and private workspaces verified untouched (git diff origin/main...HEAD touches only the 10 release files). The lockfile diff is a pure version bump (version fields and inter-package ranges only), matching the v0.7.1 precedent. node scripts/sync-versions.js reports lockstep and all inter-package dependencies in sync; npm run check is clean at 0.7.2.

Changelog sections follow the established precedent: [Unreleased] finalized to [0.7.2] - 2026-08-11 with a fresh empty [Unreleased] above, and empty version sections in packages with no entries.

Daemon protocol 7 / schema revision 16 (rev 15 mutate_queued_message from #838, rev 16 stopping workerState from #850) — additive revisions within protocol 7, no client/daemon compatibility break.

Release validation (fresh Prime Sandbox, node:22-bookworm)

• v0.7.2 candidate packed with npm run release:pack; all four tarball SHA-256s verified in the sandbox (sha256sum -c SHA256SUMS: OK)
• Installed through the real install.sh as a non-root user against a local channel layout (stable → v0.7.2 → releases/v0.7.2/*.tgz); installer resolved the channel, verified checksums, and installed cleanly
• prime-agent --version → 0.7.2; status and doctor succeeded
• prime-agent update against the local manifest reports "already up to date (v0.7.2)"
• Offline CLI smokes with the faux provider and isolated PRIME_AGENT_HOME: text, JSON, and RPC modes all exited 0 with expected output
• Daemon lifecycle: prompt via daemon path, status showed the 0.7.2 supervisor, shutdown --force stopped it cleanly
• Full test matrix in-sandbox: agent 69 ✓, ai 315 ✓ (727 skipped, keyless), tui 742 ✓, coding-agent 3 CI shards, process-stress suite 8 ✓, kernel suite (one ACP cold-CLI timeout under parallel load passed clean on re-run)
• Remaining shard failures are sandbox-environment artifacts, identical on an unmodified main control build in the same sandbox (EACCES tests running as root, /tmp hardlink EXDEV in the 4603 harness, one root-environment lsof/proc assertion) — the same test files pass locally on this branch
• Sandbox deleted after evidence capture

Note on the previous release

v0.7.1 published successfully; latest.json reports v0.7.1 as current stable.

---

Note

Low Risk
Mechanical version and changelog edits with no runtime code changes; risk is limited to release metadata accuracy.

Overview
Release packaging only — bumps prime-agent and published workspaces agent, ai, coding-agent, and tui from 0.7.1 → 0.7.2 in package.json files and package-lock.json (version fields and inter-package ^ ranges only).

Finalizes [0.7.2] - 2026-08-11 in each package changelog: coding-agent documents the shipped fixes and features (stuck-worker stack #850–#852, in-place queued message edits #838, TUI expand/collapse, analytics, Homebrew self-update, agents view persistence, etc.); agent, ai, and tui get dated empty sections under the same version. No application source changes in this diff.

^{Reviewed by Cursor Bugbot for commit a3690c0. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Release v0.7.2 across all packages

Bumps all package versions from 0.7.1 to 0.7.2 and updates internal cross-package dependencies accordingly. The coding-agent changelog notes functional fixes included in this release: in-place editing of queued steering/follow-up messages, worker state reporting fixes, stop timeout handling to avoid zombie counts, and self-healing session open/resume after stale worker registrations.

^{Macroscope summarized a3690c0.}