Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge land/1517
AkitaOnRailsf1524a15f042
diff --cc CHANGELOG.mdindex ef7369ab,2cabc857..94807cee--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -287,28 -236,18 +287,39 @@@ version in [`docs/changelog/`](docs/chasession-start fetch whenever any handoff was open, so the session startedwith no profile digest, brief or inbox notice at all. The refusal now costsonly the claim, and the handoff stays open.+- The pre-migration backup archive is now flushed and fsynced, along with its+ directory entry, before it is verified. The buffered tail of the archive was+ written when the writer was dropped, which discarded any error such as a full+ disk, and the file was never put on stable storage, while the verify pass+ re-read it from the page cache and cleared a destructive in-place migration+ to run. ([#1525](https://github.com/akitaonrails/ai-memory/pull/1525))+- Wiki commits no longer stage a write that is still in flight. A batch write+ keeps one `.ai-memory-tmp.` staging file per page on disk across an await,+ and auto-commit does not hold the mutation lock, so a checkpoint landing in+ that window committed page bodies that were never installed, and a batch+ that then failed left the rolled-back content in wiki history. A page parked+ under `.ai-memory-delete.` during a delete, or under+ `.ai-memory-tmp.move-session.` during a session move, is left out the same+ way. ([#1524](https://github.com/akitaonrails/ai-memory/pull/1524))++- The `/hook` ingress now skips a leading UTF-8 byte-order mark, as the native+ hook client already did. Some PowerShell pipelines add that marker when+ writing to a native process, and the POSIX shell hook bundle forwards the+ payload byte for byte, so such an event was answered with 400 and lost+ without notice. `ai-memory-relay enqueue --file` skips the marker too.+ ([#1523](https://github.com/akitaonrails/ai-memory/pull/1523))+ - The POSIX shell hook bundle, the PowerShell bundle under PowerShell 7 and the+ generated TypeScript integrations under Bun (OpenCode) no longer send+ their requests through an environment proxy (`http_proxy`, `HTTPS_PROXY`,+ `ALL_PROXY`), as the native hook client and the bridge already did. In a+ sandbox that exports a proxy with an empty `NO_PROXY`, the filtering proxy+ answered the loopback event POST with a 4xx, which the hooks treat as a+ permanent rejection, so the observation was dropped instead of spooled and a+ resuming session got no handoff. A server reachable only through a forward+ proxy needs a direct route; see `docs/https-via-proxy.md`.+ ([#1517](https://github.com/akitaonrails/ai-memory/pull/1517))+- `mcp-bridge` and the `setup` self-check no longer send requests to theserver through `HTTP_PROXY`, `HTTPS_PROXY` or `ALL_PROXY`, as the hooksalready did. A sandbox such as ai-jail exports a proxy with an empty