Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs: announce the 3.0 line and deprecate the 1.x token commands for it
AkitaOnRails9b2e4a467844
diff --git a/AGENTS.md b/AGENTS.mdindex c79f8d2b..7474fcde 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -286,7 +286,7 @@ covers the same tests, slower, no tiers.`static/tailwind.css`; commit the result. CI regenerates it on Linux andfails if the committed file is stale, so nothing else needs the download.- Run each Cargo companion separately (`ai-memory-client`,- `ai-memory-importer`, `ai-memory-relay`, and on `release/2.7`+ `ai-memory-importer`, `ai-memory-relay`, and on `release/3.0``ai-memory-wikisync`): `cargo fmt --check`, `cargo clippy --locked--all-targets -- -D warnings` and `cargo test --locked`, each with`--manifest-path companions/<name>/Cargo.toml`. CI also builds the relay@@ -681,8 +681,9 @@ Additional boundary rules:and version milestones.- **Branch model.** `main` is the patch line: it takes fixes and docs only(`[Unreleased]` holds only `### Fixed`), and patch tags are cut from it.- Additive work targets the standing `release/X.Y` branch for the next minor- (currently `release/2.7`). Keep `main` an ancestor of it by forward-merging+ Additive work targets the standing `release/X.Y` branch for the next+ minor or major (currently `release/3.0`, the next major). Keep `main` an+ ancestor of it by forward-merging`main` into it after every fix lands, never the reverse; when a patchrelease ships, rebuild the branch's `[Unreleased]` as only its own entriesso released sections stay identical to `main`'s. A fix lands on `main`diff --git a/CHANGELOG.md b/CHANGELOG.mdindex dcec7437..ce6d9420 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -11,6 +11,14 @@ and [0.x](docs/changelog/0.x.md).## [Unreleased]+### Deprecated++- The 1.x compatibility-token commands `user add`, `user expire`,+ `user revive` and `user rotate-token`, and their admin endpoints, will be+ removed in 3.0.0. Tokens they issued keep working after the upgrade as+ ordinary API keys; manage them with `api-key list|rotate|revoke`, and add+ people with `user add-human`.+### Fixed- Fixed the companion relay refusing to open its queue on Windows when anotherdiff --git a/docs/users.md b/docs/users.mdindex 4ae6844a..e31bfd66 100644--- a/docs/users.md+++ b/docs/users.md@@ -586,7 +586,8 @@ If you're upgrading a machine-bearer-only install:the migrated `legacy-user-token` credential; new automation should use`api-key` commands, and new people should use `user add-human`.The V53 mirror triggers are load-bearing for those shims and remain until the- shims are removed in 2.0.+ shims are removed in 3.0. Credentials they created keep authenticating after+ that, as ordinary API keys managed with `api-key`.- Before any human password or completed bootstrap exists, GET-only browserroutes continue to accept the root bearer through HTTP Basic and theHttpOnly `ai_memory_auth` cookie. Human activation disables that path