Skip to content

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 Toffanetto7e16aa05b253
diff --git a/docs/usage.md b/docs/usage.md
index c995ace1..48e5c2c6 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -191,14 +191,6 @@ Markdown (`reindex` requires a clean derived database). `explain: true` exposes
and the entity RRF contribution. Empty entity indexes contribute no candidates
or 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 Skills
From an agent, say:
@@ -464,6 +456,14 @@ docker cp ai-memory:/data/wiki ./my-ai-memory-wiki
docker 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 project
A session captured under the wrong project (a `cd` into a scratch