Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

Merge remote-tracking branch 'origin/pr/1479'

AkitaOnRails08c003a4c0a2
diff --cc CHANGELOG.md
index 5e4b7f8e,60f8bcd0..51f9d0a4
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -12,16 -12,9 +12,19 @@@ version in [`docs/changelog/`](docs/cha
## [Unreleased]
### Fixed
+ - Reported appended and removed lines in wiki sync conflict summaries, with
+ an explicit end-of-file marker instead of line 0 and matching previews.
+ ([#1477](https://github.com/akitaonrails/ai-memory/issues/1477))
+- Accepted ordinary absolute and relative Windows destination paths in the
+ wiki sync companion while still refusing directory junctions and symlinks.
+ ([#1476](https://github.com/akitaonrails/ai-memory/issues/1476))
+- Preserved dotted Windows harness names when resolving PATHEXT wrappers, so a
+ command such as `agent.tool` launches `agent.tool.cmd` rather than `agent.cmd`.
+ ([#1475](https://github.com/akitaonrails/ai-memory/pull/1475))
+- Corrected Pi MCP/setup-agent guidance to name `ai-memory-pi.ts`, described
+ its location when `PI_CODING_AGENT_DIR` is set, and corrected OMP's
+ setup-agent hint to name `ai-memory-omp.ts`.
+ ([#1446](https://github.com/akitaonrails/ai-memory/pull/1446))
- Routed OpenCode's `claude-haiku-5-5` through the Anthropic Messages API for
both Go and Zen instead of the unsupported Chat Completions protocol.
([#1470](https://github.com/akitaonrails/ai-memory/issues/1470))
diff --cc companions/ai-memory-wikisync/README.md
index fcfdcbc8,4a806097..99f9e1f0
--- a/companions/ai-memory-wikisync/README.md
+++ b/companions/ai-memory-wikisync/README.md
@@@ -114,11 -110,11 +114,13 @@@ This section describes `plan` and `expo
`--dest`; case-fold collisions are refused; symlinked destinations,
symlinked components and symlinked state directories are refused; files
are replaced atomically (tmp + rename + fsync).
+ On Windows, ordinary absolute and relative destinations are accepted;
+ directory junctions and paths through them are still refused.
- **Local edits win until forced.** Each page is compared three ways:
destination file, last exported state, server body. A file that
- diverged from both is reported with a diff summary and refused; the
+ diverged from both is reported with a diff summary and refused. The summary
+ identifies the first differing line, including appended or removed lines;
+ a missing line is shown as `<end of file>`. The
whole batch is then refused and nothing is written. `--force` overwrites the
divergent files with server content.
- **Never deletes.** `plan` and `export` never delete local files or server