Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge remote-tracking branch 'origin/pr/1814' into release/3.2.10
AkitaOnRails7b3fbcf0f969
diff --cc CHANGELOG.mdindex 51c93188,191c29d7..8c55d507--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -13,83 -13,9 +13,86 @@@ 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).+- `ai-memory user grant` and `ai-memory user revoke` now refuse empty or+ whitespace-only `--user`, `--workspace`, `--project`, and (for grant)+ `--level` 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 (#1792).+- Stopped the lifecycle relay from treating an oversized HTTP response as a+ transport failure and immediately resending its batch. A response beyond the+ 64 KiB acknowledgement cap now retains its HTTP status, stops the flush, and+ keeps unacknowledged events pending, including on HTTP 429 backpressure (#1799).+- Decoded WebVTT cue character references before document-import sanitization,+ preserving literal escaped tags and applying the existing text-size limit+ to the decoded text. SRT extraction is unchanged (#1800).+- Preserved native OIDC hook-spool entries when the POSIX or PowerShell script+ bundle drained the shared queue. Scripts now leave those entries for native+ credential resolution instead of posting them anonymously and retiring them+ on a 2xx or 401 response; static, anonymous and legacy entries still drain+ normally (#1801).+- Refused backup restores with a missing or invalid gzip trailer before+ replacing live data, even when all tar entries were readable (#1805).+- Kept separate pre-migration archives when installations share a backup+ destination and start in the same second, instead of overwriting an+ existing installation's snapshot (#1806).+- Restored the previous wiki file when `restore-page` could not commit its+ SQLite update, including a rejected case-colliding historical path. Restores+ now share the page writer's lock through conformance, file replacement and+ indexing so a concurrent write to that same path cannot leave disk and+ SQLite disagreeing (#1807).+- Kept concurrent page edits current during opt-in cold-cluster dedup and dream+ merges. Each write batch now skips if a selected source version changed,+ preserving the newer body, tier and pin along with unchanged peers (#1808).+- Dropping the final store writer handle now finishes when its command queue+ is full. Accepted writes still drain before the writer thread exits, including+ when callers have cancelled their waits (#1809).++- Scheduled empty-project cleanup now preserves projects that have sent or+ received agent messages, including claimed/cancelled history, so it cannot+ silently delete their inbox/outbox through a project cascade (#1810).++- Fixed `server add` rejecting valid inline tables in `servers.toml`, including+ token rotations and URL changes. Updates now accept the same table forms as+ reads and removal, preserving registered roots and other profiles (#1812).+ - Kept OpenCode V1 failed tool results in the managed workstream ledger,+ including their visible error text and error status, instead of importing+ only the call and silently dropping the failure reason (#1814).- Refused empty and whitespace-only `--workspace` and `--project` flags at theshared CLI scope-resolution choke point (`resolve_scope`,`resolve_scope_noting_marker_project`, `resolve_scope_with_marker`, and