Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge branch 'main' into fix/directory-link-targets
caminhar-deus444170607d5f
diff --cc CHANGELOG.mdindex ca57f544,4a28b987..6f22c197--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -27,13 -27,11 +27,18 @@@ and this project adheres to [Semantic Vmean latency instead of 20.2 s — in that run the hosted mean sat on theserver's 20 s completion timeout, which made the reranker stall everyquery before falling back. (#873)+- `ai-memory status --workspace <name> --project <name>` scopes the `links`+ line, and its `typed edges` detail, to one project instead of the whole+ store. `GET /admin/status` accepts the same optional pair and answers with a+ new `links_scope` object (`ScopeLinkStatus`); naming only one of the two is+ a `400`, an unknown scope the usual `404`. Without the pair the response and+ the human output are byte-identical to before, so the endpoint stays a plain+ health probe. (#911)+ - `ai-memory status` (text and `--json`) and `GET /admin/status` report the+ server's HTTP exposure, so an unauthenticated bind is pollable by a monitor.+ The verdict is admin-gated at parity with the existing `bind`/`data_dir`+ fields and defaults to `Unknown` (never `Safe`) when unset or read by an+ older client. (#904)### Changed- Quieted the default server log: the reconciliation-pass summary that fired