Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs: point the changelog entries at this PR
Djalma Júnior30c3967e298b
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex b56675ac..4f13b8ff 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -16,7 +16,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0value, and headers without the secret are ignored as before. The serverrefuses to start with a proxy secret but no `root_username`, because noproxied request could ever reach a root-only capability again. Unset — the- default — nothing changes (#310).+ default — nothing changes (#333).- Qualified identity keys: every ownership decision resolves a request to`sub:<subject>` or `user:<name>` via one accessor(`ActorContext::identity_key`), never a bare string, so a username equal to@@ -25,12 +25,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0filesystem-safe `path_segment` derivation ships alongside for per-operatorwiki paths. `OwnerFilter` / `owner_stamp` carry the read and write sides ofthe same contract, with "absent = shared" as the compatibility rule- (#310).+ (#333).- The `/admin/*` route layer and the MCP `memory_forget_sweep` tool now ask"does this deployment distinguish operators" instead of "do `users` rowsexist", so a trusted-proxy deployment — which never writes a `users` row —gets root-only admin gating instead of waving every proxied caller through- the single-operator escape hatch (#310).+ the single-operator escape hatch (#333).## [1.21.0] - 2026-07-31