Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(wiki): place reindex coordination with raw wiki usage
Éverton Toffanetto5996a713f181
diff --git a/docs/usage.md b/docs/usage.mdindex a86d93e5..ea374b8b 100644--- a/docs/usage.md+++ b/docs/usage.md@@ -221,14 +221,6 @@ Markdown (`reindex` requires a clean derived database). `explain: true` exposesand the entity RRF contribution. Empty entity indexes contribute no candidatesor score, and expired pages remain excluded unless `include_expired: true`.-Watcher reindexing shares the per-page mutex used by writes and batches on the-same Wiki handle and its clones. It waits before reading the file, holds that-mutex through the SQLite upsert, and releases both page and global mutation-guards before embedding. Different paths can proceed concurrently, and the-watcher never rewrites the page. External editors and independently constructed-Wiki handles do not take these locks; external edits can still race with a-server write or reindex.-## Install the routing snippet and Agent SkillsFrom an agent, say:@@ -494,6 +486,14 @@ docker cp ai-memory:/data/wiki ./my-ai-memory-wikidocker exec ai-memory git -C /data/wiki log --oneline```+Watcher reindexing shares the per-page mutex used by writes and batches on the+same Wiki handle and its clones. It waits before reading the file, holds that+mutex through the SQLite upsert, and releases both page and global mutation+guards before embedding. Different paths can proceed concurrently, and the+watcher never rewrites the page. External editors and independently constructed+Wiki handles do not take these locks; external edits can still race with a+server write or reindex.+## Move a session to another projectA session captured under the wrong project (a `cd` into a scratch