Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #919 into main
AkitaOnRails0e91c05b9b78
diff --cc CHANGELOG.mdindex 2460796d,3dc43fa3..9ee38f89--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -48,16 -48,20 +48,30 @@@ and this project adheres to [Semantic Vunchanged — this only makes the existing warning reliably visible. (#903)### Fixed+- A page whose `expires_at` is a bare date (`2026-10-01`) now gets an OKF+ `stale_after` that names the instant the TTL expires it+ (`2026-10-01T23:59:59.999999Z`) instead of the date copied verbatim. OKF+ v0.2 requires every timestamp to carry an explicit UTC offset, and read a+ bare date as the start of that day, a day earlier than ai-memory's+ end-of-day TTL. An RFC 3339 `expires_at` is still carried unchanged.+ Pages already written that way are repaired in place when `serve`+ starts: index row and file, with the same version row, `updated_at`,+ `generated.at` and body, in one wiki commit, and nothing to do on later+ starts. (#917)+ - `ai-memory backfill` stamps each imported session and observation with the+ transcript's own event time instead of the moment it was imported, so a+ transcript from weeks ago no longer looks like it just happened. An event+ without a valid timestamp inherits the nearest one, and the session's start+ and end are the earliest and latest event times. The `/hook` body accepts a+ top-level RFC 3339 `occurred_at`; it must be positive and no more than five+ minutes in the future, and anything missing, malformed or out of bounds+ falls back to "now" instead of failing the hook. Because an imported+ session now ends in the past, it can sit below the auto-improve watermark+ and the experience-pass anchor (no automatic review until a newer session+ moves them), an opt-in observation retention window can prune its older+ observations right after import, and the "most recently active project"+ fallback after a restart may not pick a project that was just backfilled.+ (#919)- The default log filter's `rmcp=warn` cap (#894) no longer raises rmcpabove a quieter `log_level`. A target directive beats the global leveleither way, so with `log_level = "error"` or `"off"` the cap re-enabled the