Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge PR #598: redact opaque auth-bearing HTTP headers
AkitaOnRailsf9214ff8baea
diff --cc CHANGELOG.mdindex c7b89bea,e7ff74c9..ba7b17fc--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -8,27 -8,18 +8,39 @@@ and this project adheres to [Semantic V## [Unreleased]### Fixed+- `install-hooks --agent zcode --apply` now removes stale ai-memory+ hooks left under event keys this version no longer manages (e.g. a+ legacy `SessionEnd`), instead of reporting "already up to date" while+ a broken/orphaned entry lingered (#600). The dry-run printed snippet+ also now states plainly that `--apply` persists the auth token to+ `<data-dir>/auth-token` (0600) and writes token-less args, so the+ applied config differs from the embedded-token snippet by design.+- Local-embedding model download (`fetch_model`) now bounds a stalled+ connection instead of hanging startup forever (#602): a 30s connect+ timeout and a generous 600s overall ceiling (large model files, so+ not the inference clients' flat 120s that would fail a slow download).+- The OKF v0.2 migration no longer crash-loops on startup with a+ libgit2 `invalid object specified … class=Tree` error that left the+ server unable to boot (#594). The wiki commit re-hashed files through+ libgit2's index, whose stat cache could trust a cached blob OID absent+ from the object database (a store carried across libgit2/git versions,+ or an interrupted earlier operation) — `write_tree` then aborted and,+ because the migration commits through that path, every restart failed.+ The commit now clears the index before staging so every file is+ re-hashed from the working tree. (The Docker runtime ships no `git`,+ so the fix is in-library, not a CLI fallback.)+ - HTTP headers that carry a credential in an opaque value are now redacted+ before reaching durable storage. Previously such a header matched no+ built-in pattern unless it used the `Bearer` keyword or an+ `UPPER_SNAKE_TOKEN=` shape. The bearer rule requires the literal keyword,+ and the generic env-var rule requires `[A-Z][A-Z0-9_]*_TOKEN`, which never+ matches a kebab-case header name. `X-Amz-Security-Token` (AWS SigV4),+ `X-Api-Key`, `Private-Token` (GitLab), and `Ocp-Apim-Subscription-Key`+ (Azure) all fall in that gap, and tool output echoing a `curl` invocation+ is a common way they reach capture. A `key` or `token` suffix on its own+ does not imply a secret, so it must be qualified by an auth word:+ `Idempotency-Key`, `Continuation-Token` and storage partition keys are+ left intact and stay readable in captured output.- `as_of` time-travel queries and the entity retrieval stream now workon real stores. Both read the entity index, which was populated onlyfrom an LLM consolidator's `entities:` frontmatter — absent on the