Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge remote-tracking branch 'origin/main' into merge-464
AkitaOnRailsac33e937f264
diff --cc CHANGELOG.mdindex 22d52a3f,57e3907e..10fca990--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -8,20 -8,20 +8,34 @@@ and this project adheres to [Semantic V## [Unreleased]### Fixed+- The Windows Docker wrapper's thin-client commands now reach a+ loopback-published server instead of failing with `Connection refused (os+ error 111)`. `ai-memory status`, `search`, `bootstrap` and every other+ thin-client command runs inside a short-lived helper container, where the+ CLI's default `http://127.0.0.1:49374` resolves to that helper rather than+ to the Windows host, so a healthy `docker run -p 127.0.0.1:49374:49374`+ server was unreachable from the wrapper while `curl` from PowerShell worked.+ The wrapper now injects `AI_MEMORY_SERVER_URL=http://host.docker.internal:49374`+ for those commands, matching what the POSIX wrapper has done on macOS since+ (#107) — Docker Desktop gives Linux containers no host networking on either+ platform. `install-mcp`, `install-hooks` and `setup-agent` still render+ `http://127.0.0.1:49374` into host-side agent config, because+ `host.docker.internal` does not resolve on the Windows host, and an explicit+ `AI_MEMORY_SERVER_URL` (homelab or remote server) is still honoured. (#464)+ - Page paths that cannot be materialised on every supported platform are now+ refused at write time instead of failing late (#462). `PagePath` accepted+ DOS device names (`CON.md`, `aux.md`), components ending in a dot or space,+ the characters `< > : " | ? *`, and control characters. On native Windows+ some of those failed with a generic HTTP 500, while others were written+ successfully but could not be checkpointed by libgit2 or deleted through the+ normal API — silent partial state, which is worse than a clean rejection.+ The check runs in `Wiki::write_page`, the single funnel every page creation+ passes through, and returns an error naming the offending component and the+ reason. It is deliberately **not** in `PagePath::new`: persisted rows are+ reconstructed through that constructor on every read, so tightening it would+ make an already-stored non-portable page unreadable and break the whole+ listing it appears in. The rule is identical on every platform, so a wiki+ authored on Linux stays usable on Windows.- Made non-FTS search hits describe the page instead of repeating itsheading. Only the FTS5 path built a real excerpt (`snippet(pages_fts, ...)`,centred on the matched terms); the vector, entity-match, graph-neighbour and