Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(lifecycle): correct the merge-loss list and the CLI project selector

Felipe Neves Ricardocd24657470af
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ec3ddd56..1bcb675a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,6 +11,16 @@ version in [`docs/changelog/`](docs/changelog/):
## [Unreleased]
+### Fixed
+- Corrected `docs/lifecycle-ops.md` on two points. The `move-project` merge
+ drops everything the source project owns, the same set `purge-project`
+ deletes: managed workstreams, cross-project messages, auto-improvement
+ state, entities, page feedback and project grants as well as sessions,
+ observations and handoffs. The `400` for sending both a project name and an
+ id, or neither, applies to the admin endpoints; the CLI resolves a missing
+ project from the marker, the git remote, then the directory name.
+ ([#1493](https://github.com/akitaonrails/ai-memory/issues/1493))
+
## [3.1.2] - 2026-10-20
### Fixed
diff --git a/docs/lifecycle-ops.md b/docs/lifecycle-ops.md
index b3b35fca..d940035a 100644
--- a/docs/lifecycle-ops.md
+++ b/docs/lifecycle-ops.md
@@ -33,10 +33,13 @@ on a homelab box where mistakes are harder to undo.
whose name is ambiguous: an empty legacy twin row left by an older migration
can carry another project's old name, and the name lookup refuses it.
`list-projects` prints each project's id. The id is looked up inside the
-workspace the command names. Sending both the name and the id, or neither, is
-a `400`, so is a malformed UUID, and an id that names no project in that
-workspace is a `404`. `--confirm`, the preview and every other guard behave
-the same as with a name.
+workspace the command names. On the admin endpoints, sending both the name and
+the id, or neither, is a `400`, so is a malformed UUID, and an id that names no
+project in that workspace is a `404`. The CLI refuses both flags together before
+sending anything, and with neither it resolves the project the way other
+commands do: the `.ai-memory.toml` marker's `project`, then the git remote, then
+the directory name. `--confirm`, the preview and every other guard behave the
+same as with a name.
State-touching commands route through the HTTP admin API except `reset`,
`restore`, and `reindex`, which are direct-disk lifecycle operations that
@@ -614,11 +617,16 @@ destination promotes its legacy name first, the response includes
`manifest_warning` when that committed promotion's manifest refresh/checkpoint
fails; the CLI prints it.
-**What does NOT migrate (merge case only):** in the `copy-purge` path the
-source's `sessions`, `observations`, and `handoffs` (the raw episodic
-capture log) are dropped by the purge, and the moved pages start a fresh
-supersession chain (the real page history lives in the wiki's git
-mirror). The `true-move` path has no such loss.
+**What does NOT migrate (merge case only):** the `copy-purge` path copies
+only the source's latest pages and their embeddings. The purge then drops
+everything else the source project owns, the same set `purge-project`
+deletes: its `sessions`, `observations`, and `handoffs` (the raw episodic
+capture log), its managed workstreams with their native sessions, runs,
+events and `raw/workstreams/` segments, the cross-project messages it sent
+or received, auto-improvement state, entities, page feedback and project
+grants. The moved pages start a fresh supersession chain (the real page
+history lives in the wiki's git mirror). The `true-move` path has no such
+loss.
> **Operational caveat: moving the project the current session writes
> to.** Lifecycle hooks stamp a bounded observation on every supported tool-lifecycle event into the