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/1796' into release/3.2.10

AkitaOnRailsd0c9f8613186
diff --cc CHANGELOG.md
index 7cfb79a0,28ac006e..1c736739
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -13,37 -13,11 +13,42 @@@ version in [`docs/changelog/`](docs/cha
### Fixed
+- Sorted recent page lists by timestamp rather than RFC3339 text, so updates
+ with different fractional-second precision appear in chronological order
+ in the legacy recent API, project activity, folder previews and namespace
+ listings. Kept title-sort and equal-timestamp path tie-breaks (#1247).
+
+- Fixed `restore` replacing live data when a backup without `config.toml`
+ contains API keys that the configured pepper cannot verify. It now refuses
+ before the swap, preserving the live wiki, database and config, and names
+ the original configuration as the remedy (#1495).
+
+- Preserved explicit DOCX/PPTX line breaks and DOCX tabs in document imports
+ when XML uses paired tags, including formatted PowerPoint breaks in slides
+ and speaker notes. DOCX carriage returns now also keep adjacent text runs
+ on separate lines instead of joining their words. Paragraph tab-stop
+ definitions no longer insert spurious tabs into the extracted text (#1786).
+
+- Kept a wiki-sync server page when its repository file was recreated after
+ the sync planned a deletion. `sync --propagate-deletes --apply` now rechecks
+ local absence before sending the delete, preserves the page's baseline and
+ reports the changed file for the next sync, including with `--prefer repo`
+ (#1787).
+- Transcript imports (`backfill`, the `run` ledger, `recover`) now drop Codex
+ memory-writing agent runs by the same signals the live hook uses: the
+ checkout cwd, an event's recorded cwd, or a Codex user prompt that opens
+ with `## Memory Writing Agent`. A custom `CODEX_HOME` whose last path
+ component is not `.codex` previously reimported those sessions (#1790).
+- Admission webhook HTTP requests now follow redirects only within the
+ configured `scheme://host:port` origin (up to 10 hops) and fail on
+ cross-origin redirects without forwarding page payloads or applying foreign
+ response mutations, surfacing the redirect refusal cause in logs and
+ `reject`-policy errors (#1794).
+ - `ai-memory project access` and `ai-memory project grants` now refuse empty
+ or whitespace-only `--workspace`, `--project`, and (for access) `--mode`
+ values before sending any request to the server. These commands take
+ required names and never call `resolve_scope`, so the #1774 choke point
+ did not cover them (#1791).
- Refused empty and whitespace-only `--workspace` and `--project` flags at the
shared CLI scope-resolution choke point (`resolve_scope`,
`resolve_scope_noting_marker_project`, `resolve_scope_with_marker`, and