chore(release): prepare v0.7.1

[snimu]

Patch release. Two bug fixes and catalog/test maintenance, no breaking changes, so patch per the no-major-releases policy.

Why this one matters beyond the changelog

The headline fix is #836: running retry_worker on a stopped session worker cleared the in-memory stop flag but not the saved stop marker, so recovery immediately cancelled itself and the session stayed stuck at "Session worker is not connected". Explicit retries now clear saved stop markers first, matching the existing recovery behavior for client-owned workers.

Contents

PR	change
#836	explicitly retried session workers recover instead of cancelling themselves
#809	bundled websearch skill documents the /login → MCP Connections step required to configure Serper
#699	dropped Nemotron 3 Ultra from the Prime Inference catalog (maintenance, no changelog entry)
#658, #661, #700, #787	test, comment, and README maintenance (no user-facing behavior)

#836 merged without a changelog entry; this PR adds it under 0.7.1.

Version bump

Lockstep across the root package and the four published packages: agent, ai, coding-agent, tui. packages/web-ui does not exist in this repo, so it is not bumped despite the release skill listing it. Example and private workspaces verified untouched with git diff --exit-code. The lockfile diff is a pure version bump (version fields and inter-package ranges only), matching the v0.7.0 precedent.

node scripts/sync-versions.js reports all inter-package dependencies in sync, and npm run check is clean at 0.7.1.

Changelog sections follow the v0.6.1 precedent: [Unreleased] finalized to [0.7.1] - 2026-08-07, with a fresh empty [Unreleased] above it and empty version sections in the packages that had no entries.

Daemon protocol 7 / schema revision 13 are unchanged since v0.7.0, so there is no client/daemon compatibility impact.

Release validation

• v0.7.1 candidate packed with npm run release:pack and installed through the real install.sh in a fresh Prime Sandbox
• Installer resolved the stable channel, verified the tarball SHA-256 (prime-agent-0.7.1.tgz: OK), and provisioned the IPython kernel venv
• prime-agent --version, status, and doctor succeeded
• Fresh unauthenticated run produced clear login guidance
• Authorized headless inference invoked IPython and returned the expected result
• Kernel state persisted across --print runs with -c, surviving shutdown --force and daemon restart
• Subagent round trip: rlm(...) spawn, child reply via agent_message.send, parent received it
• prime-agent update reports up to date against the production manifest; update --force against a local manifest installs via the latest.json tarball spec
• Sandbox evidence captured and the sandbox deleted

Note on the previous release

v0.7.0 published successfully: latest.json reports v0.7.0 and releases/v0.7.0/prime-agent-0.7.0.tgz returns 200.

Not merging this myself.