Skip to content

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

Rust

Merge audited PR #1496

AkitaOnRails70c04e500af3
diff --cc CHANGELOG.md
index fdd62f20,1bcb675a..b3a9409a
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -11,29 -11,16 +11,39 @@@ version in [`docs/changelog/`](docs/cha
## [Unreleased]
+### Security
+- Updated `rustls-webpki` 0.103.15 → 0.103.16 for
+ [RUSTSEC-2026-0382](https://rustsec.org/advisories/RUSTSEC-2026-0382), in
+ which certificate verification may accept distrusted intermediates, and
+ `webpki-root-certs` 1.0.9 → 1.0.10 for
+ [RUSTSEC-2026-0383](https://rustsec.org/advisories/RUSTSEC-2026-0383), whose
+ bundled roots still trusted distrusted emSign intermediates. The importer,
+ relay and wiki sync companions take the same `rustls-webpki` bump.
+
### Fixed
+- Held `ai-memory run` heartbeat notices while the harness owns the terminal
+ and printed them after it exits, so a server outage no longer writes into the
+ harness TUI. Only the first and latest notices are replayed, with a count of
+ the rest.
+ ([#1500](https://github.com/akitaonrails/ai-memory/issues/1500))
+
+- Dropped stopwords from the quoted bag of words a search falls back to when
+ its text looks like FTS5 syntax but does not parse, such as a question
+ ending in `(prod)`. The fallback OR-joined `what`, `is`, `the` and `of`
+ with the content words; it now filters through the configured
+ `[search.fts] stopwords` list like a bare query, keeps the words the user
+ quoted, and keeps every word when all of them are stopwords.
+
+ - 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.
++ deletes. This includes managed workstreams, cross-project messages,
++ auto-improvement and profile-harvest state, consolidation jobs, ingest keys,
++ entities, page feedback, purge tombstones 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 --cc docs/lifecycle-ops.md
index b3b35fca,d940035a..77433473
--- a/docs/lifecycle-ops.md
+++ b/docs/lifecycle-ops.md
@@@ -614,11 -617,16 +617,18 @@@ destination promotes its legacy name fi
`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.
++or received, auto-improvement and profile-harvest state, session-consolidation
++jobs, ingest deduplication keys, entities, page feedback, purge tombstones and
++project grants. The moved pages start a fresh supersession chain (the real
++page history lives in the wiki's git mirror). The append-only audit trail
++remains, with references to the removed source ids. 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