Skip to content

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

Rust

Merge main into fix/sweep-compacted-residue-terminal-when-compaction-off

AkitaOnRails136db80fa733
diff --cc CHANGELOG.md
index d64ed5c7,c7c531f9..a96d3d4f
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -13,15 -13,39 +13,48 @@@ version in [`docs/changelog/`](docs/cha
### Fixed
+- The forget sweep now keeps an already-compacted page terminal when
+ `compact_cold_episodic` is off — the default everywhere. The guard that made
+ a page carrying the V65 `compacted_at` marker "neither re-compacted nor
+ evicted" sat inside the compaction arm only, so with compaction off such a
+ page was tombstoned and then hard-deleted. The marker is not A2's alone: the
+ A3 cold-cluster dedup merge-note stub and the B2 dream pass both stamp
+ `compacted: true` under their own flags, so the durable residue a merge chose
+ to keep could be destroyed without anyone enabling compaction. A
+ non-compacted cold page is still evicted exactly as before (#1632).
+ - A project whose every page has passed its TTL is read as new again when
+ the profile digest sizes itself. The newness probe was the one `pages` read
+ in the profile module without the expiry guard its three siblings apply, so
+ such a project still counted as having memory: it got the smaller
+ established-project digest and lost the note offering
+ `ai-memory profile apply`, with no live page left to show for it (#1631).
+ - The first start after the 3.2.0 upgrade no longer slows down as the
+ one-time CJK index backfill (V87) progresses. Each batch filtered the source
+ table from its first row again, so the pass probed every row it had already
+ indexed once more per batch: quadratic in the row count, and hours of
+ startup on a store with 1.6 million observations while `serve` answered
+ nothing. Each batch now resumes after the last rowid it indexed, so every
+ row is examined once (#1652).
+ - Restoring a page from a checkpoint (`/admin/restore-page`) no longer
+ rewrites the restored file's `generated.at` to the current time when the
+ checkpoint is already OKF-conformant. The restore now keeps the
+ checkpoint's own timestamp when conformance leaves the rest of its
+ frontmatter unchanged and the file on disk holds other content, so a
+ checkpoint emitted by ai-memory restores byte for byte whatever the clock.
+ When the file on disk already holds the same content, its timestamp is kept
+ so file and row stay aligned; checkpoints that need conformance still go
+ through the existing inheritance and stamping rules (#1671).
+ - The native Windows Docker wrapper now recognizes `upgrade` after valid
+ `--config` or `--data-dir` global options and pulls the image instead of
+ forwarding `upgrade` into the helper container. Unknown and malformed
+ options still reach the CLI parser (#1667).
+ - `ai-memory run codex` no longer starts a new session when Codex has
+ compressed the linked rollout. Codex keeps a rollout it has not written for
+ a week as `rollout-*.jsonl.zst`, which the launcher did not recognize, so it
+ reported the session as missing and repointed the workstream to a fresh one.
+ The compressed copy is now read for the resume, the pre-launch baseline and
+ the transcript import, and the plain file wins when both exist. `backfill`
+ and the session listings see compressed Codex sessions too (#1653).
- Updated tokio to 1.54.1 in the server, relay, importer and wikisync
lockfiles. 1.52.3 and the 1.53.x releases before 1.53.3 fall inside
RUSTSEC-2026-0386, an unsound advisory for `AsyncFd` constructors that