Worktree-Only Closeouts & Carryover Coverage

Agents Remember 2.9.0

Closeout is now worktree-only, branch-memory carryover covers every artifact kind, and the README's Status section now states where the project is and where it is going — with release history living here, in GitHub Releases.

⚠️ Breaking change — deliberate Stability exception

• The direct_closeout_preview and direct_closeout_apply MCP tools are removed (GitHub #62). Worktree-only closeout was the original design intent of the session lifecycle: every change to a managed repo — chat builds included — runs through a code + memory worktree, keeping external memory consistent and auditable. The direct path was a leftover from an incomplete cleanup. Migration: worktree_start → work → worktree_closeout_preview / worktree_closeout_apply.
• Under the Stability promise, tool removals belong to a major bump. This ships in a minor release as a recorded, deliberate exception: 3.0 is reserved for the dashboard/observability architecture named in the README's new Status section.

Highlights

• Worktree-only closeout doctrine (#62): tools, skills (l-01-session-job-lifecycle, c-12-closeout), docs, and tests aligned; the MCP tool surface goes 37 → 36.
• Carryover artifact coverage: memory_carryover_plan / memory_carryover_apply now also carry the repo entity catalog and memory-only doc updates between memory branches.
• Repository rename sweep: stale agents-remember-md references swept across docs and onboarding after the GitHub rename to agents-remember.

Docs And Public Surface

• The README Status section is rewritten from the per-release narrative chain (a de-facto changelog) into a two-paragraph current state + direction statement; per-release history now lives in GitHub Releases — this page is the canonical changelog.
• system/git-workflow.md / system/tools.md (memory layer): the version-bump location count corrected to three (pyproject, SERVER_VERSION, README Status).