Skip to content

chore: release v0.19.0 to main - #1293

Merged
ajianaz merged 164 commits into
mainfrom
chore/release-v0.19.0
Sep 29, 2026
Merged

ajianaz merged 164 commits into
mainfrom
chore/release-v0.19.0

Conversation

@ajianaz

@ajianaz ajianaz commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

What

Release sync: merge develop (v0.19.0) into main. Merge branch from origin/main, all 26 conflicting files resolved as theirs=develop. Proof of content integrity: the committed merge tree is byte-identical to origin/develop (write-tree = 94919dbbb849fa977955b7698ad3fc110baa05c2 = develop tree). Version 0.19.0, CHANGELOG [0.19.0] section complete.

Why

Standard release step: develop → main sync so the v0.19.0 tag can point at main (release.yml requires the tag to be on main).

Testing

ajianaz and others added 30 commits August 11, 2026 22:10
3 files still referenced ~30ms (stale from early benchmarks).
Actual measured P50 at 1K-10K memories is ~45ms per benchmarks.md.
Updated: architecture.md, mcp.md, index.md
…-to-45ms

fix(docs): standardize recall latency to ~45ms
- Add internal/ to .gitignore (prevents future strategy/launch doc leaks)
- Add benchmarks/longmemeval/results_*/ to .gitignore (ephemeral data)
- Add docs/package-lock.json to .gitignore (VitePress build artifact)
- Move blog/comparison-2026.md → docs/comparison-2026.md (consolidate docs)
- Remove stale benchmarks/longmemeval/results_diverse/ (raw output, not summary)
- Remove docs/package-lock.json from tracking

Audit confirms: zero internal/ files in entire git history after filter-repo scrub.
…#1015)

* feat(bench): batch import + strategy flag + API embedding auto-config

- Replace 53x individual remember calls with single JSONL batch import (10x speedup)
- Add --strategy flag to pass vector|hybrid to uteke recall
- Auto-configure embedding API from EMBED_API_KEY/EMBED_API_BASE env vars
- Add --chunk-sessions flag for session chunking (Tier 2 prep)
- Dedup recall results by session_id (first occurrence = highest rank)
- Raise subprocess timeout 120s -> 600s for large imports

Initial 5Q results: hybrid R@5=1.000 vs vector R@5=0.800 (+20pp)

* fix(bench): only mark sessions inserted after import succeeds

Address Cora findings:
- Move inserted_sids population to after batch import success
- Parse import response to verify imported_count > 0
- Log warning if import returns 0 inserted

* fix(bench): resolve uteke binary by absolute path to avoid x86_64 PATH clash

Background subprocess calls were resolving to /opt/data/.cargo/bin/uteke
(x86_64) instead of target/release/uteke (AArch64). Now resolves relative
to repo root with shutil.which fallback.

* docs(bench): add 50Q hybrid results — R@5 98.0%, R@10 100%

Strategy comparison (uteke only):
- Vector 500Q: R@5=85.4%, R@10=88.5%, NDCG@5=0.810
- Hybrid 50Q: R@5=98.0%, R@10=100%, NDCG@5=0.960
- Improvement: +12.6pp R@5

Hybrid uses RRF (k=60) fusion of vector + FTS5 search.
1 miss at R@5 (single-session-user), recovered at R@10.

run_eval.py changes:
- Add --strategy flag (vector|hybrid)
- Throttle: taskset -c 0-1 + nice -n 19
- Absolute binary path resolution
- Timeout: 900s per question

* fix(core): add dedup, retry, and auto_link to import path (#1005)

Import pipeline was missing 3 features that remember() has:
1. Dedup check — cosine >= 0.95 skips duplicate entries
2. Retry on embedding failure — 3 retries with backoff
3. Auto-link cosine edges — graph edges for imported memories

Changes:
- import_export.rs: call check_duplicate() before insert, use
  retry_embed() instead of single-attempt embed(), call
  auto_link_cosine() after successful insert
- operations.rs: make retry_embed() and check_duplicate() pub(crate)
  so they're accessible from import_export.rs

Import path is now semantically consistent with remember() path.

* fix(core): cross-compile ORT_LIB_NAME for Android/iOS (#1014)

Add target_os = "android" to Linux .so branch and target_os = "ios"
to macOS .dylib branch. Without these, uteke-core fails to compile
for mobile targets with E0425 (cannot find value ORT_LIB_NAME).

Android uses libonnxruntime.so (same as Linux, loaded via jniLibs).
iOS uses libonnxruntime.dylib (same as macOS, framework embedded).

This unblocks uteke-mobile cross-compilation.

* feat(core): hybrid as default recall strategy

Change default_strategy from vector to hybrid (RRF: vector + FTS5).

Benchmark justification (LongMemEval-S):
- Vector 500Q: R@5=85.4%, R@10=88.5%
- Hybrid 50Q:  R@5=98.0%, R@10=100.0%
- Improvement: +12.6pp R@5

Changes:
- config.rs: default_strategy = hybrid + assert in test
- cli.rs: update help text default to hybrid
- recall.rs: update comment to reflect new default
- configuration.md: update all references
- cli-reference.md: reorder examples, hybrid first as default

Users who want vector-only: set default_strategy = vector in config
or use --strategy vector flag.

* fix(bench): guard taskset/nice with sys.platform check

Cora finding: taskset is Linux-only, would FileNotFoundError on macOS.
Now conditionally applied only when sys.platform == 'linux'.

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…ng text (#1006, #1002) (#1016)

#1006: CLI update check skipped when UTEKE_NO_UPDATE_CHECK env var is set.
Benchmark script sets this automatically, saving ~500ms per subprocess call.

#1002: Pre-truncate text before tokenizer to avoid wasted CPU on tokens
beyond MAX_SEQ_LEN (2048). Uses 4 chars/token heuristic with char-boundary
safety.

#1003: Already resolved — idx_memories_namespace index exists in SCHEMA_INDEXES.
#1004: Already resolved — compute_graph_signals uses single batched SQL query.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…enance (#1007, #1010, #1012, #1013) (#1017)

* feat: Phase 3 — lifecycle/deprecated endpoint, memory tools guide, source provenance (#1007, #1010, #1012, #1013)

#1007: GET /lifecycle/deprecated — list deprecated memories with sunset info
- list_deprecated() in aging.rs with DeprecatedMemoryInfo struct
- Handler + route + API registry entry

#1010: Memory tools guide injection
- guide.rs module with default_guide() for system prompt injection
- CLI: uteke guide command
- API: GET /guide endpoint

#1012: Implicit memory hierarchy docs
- docs/organizing-memories.md — type + importance pattern
- VitePress nav entry

#1013: Auto-populate source provenance
- CLI extraction: set source_label from input filename, source_type='extract'
- Server extraction: set_source on each extracted fact
- CLI output: display source_type alongside source in verbose mode

* docs: regenerate api-reference.md for new endpoints (#1007, #1010)

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
SYSTEM_PROMPT now requests scene-segmented JSON output with type and
priority per fact. parse_facts handles three formats: scene-segmented
nested JSON, flat object array with type/priority, and legacy flat
string array (backward compatible).

ExtractedFact struct carries content, scene, fact_type, priority.
CLI and server callers use remember_typed + set_importance + scene tag.

Offline mode unaffected — ExtractedFact::flat wraps existing strings.
9 new tests cover nested parsing, backward compat, dedup, priority
range validation.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
- Version bump to 0.14.0
- CHANGELOG entry for v0.14.0
- Docs: cli-reference scene-segmented extraction section
- Docs: memory-lifecycle deprecated endpoint

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
- Add 60s/30s/30s delay between crate publishes for index propagation
- Add repository, rust-version, documentation, homepage to uteke-mcp
- Fixes: uteke-mcp/cli/server fail because uteke-core not yet in index
- Fixes: 'manifest has no documentation, homepage or repository' warning

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Root cause: commit 0b5cad3 removed docs/package-lock.json from git tracking
and added it to .gitignore. The deploy-website workflow still referenced it
via cache-dependency-path, causing setup-node to fail:
'Some specified paths were not resolved, unable to cache dependencies.'

Fix:
- Replace actions/setup-node with oven-sh/setup-bun
- Replace npm ci with bun install --frozen-lockfile
- Replace npm run build with bun run build
- Add docs/bun.lock as tracked lockfile
- Remove docs/package-lock.json from .gitignore (no longer relevant)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Add mutation testing infrastructure to validate test quality across
critical pure-logic modules. 11 new mutation-killing tests improve
salience_recency.rs score from 76% to 96%.

Changes:
- Add cargo-mutants config (mutants.toml) with exclusions for
  modules requiring external services
- Add mutation-testing CI workflow (develop→main PRs only,
  pre-release quality gate)
- Add .gitignore entries for mutants output directories
- Add mutation-testing.md developer documentation
- Write 9 mutation-killing tests for salience_recency.rs
- Write 2 mutation-killing tests for recall_cache.rs

Results (cargo-mutants v27.1.0):
  jaccard.rs:       12 mutants, 9 caught, 0 missed (100%)
  salience_recency: 53 mutants, 48 caught, 3 missed (96%)
  recall_cache:     25 mutants, 18 caught, 5 missed (80%)

Refs: nginjen mutation testing pattern (#mutation-testing)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…ion-killing tests (score 50%→97%) (#1024)

Two production bugs found by mutation testing:

1. Heading duplication: oversized markdown sections had their heading
   prepended twice in the first sub-chunk (once by split_by_headings,
   once more by the sub-chunk loop), corrupting downstream embeddings.
   Fixed by removing the dead heading_prefix re-prepend path entirely.

2. Multibyte infinite loop: split_long_text's zero-progress guard
   advanced by raw byte offsets that could land inside multi-byte UTF-8
   characters (CJK/emoji), flooring back to start forever.
   chunk_markdown("日本語", 2) would hang. Fixed with a proper
   forward-char-boundary advance in the guard.

Also:
- 40 new mutation-killing tests (chunker: 20 → 60 tests)
- cargo-mutants config moved to .cargo/mutants.toml (v27 schema:
  exclude_globs/exclude_re, valid keys only); glob paths fixed to
  match from workspace root; CLI update_check also excluded
- 3 proven-equivalent mutants excluded with documented reasoning
- docs/mutation-testing.md: final scores, bug postmortem, timeout notes

Verify run: 164 mutants, 149 caught, 0 missed, 5 timeout, 10 unviable (97%)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Patch release: chunker heading duplication fix, multibyte infinite
loop fix, mutation testing hardening (PR #1024).

- Bump workspace version 0.14.0 -> 0.14.1
- Bump intra-workspace deps (cli/mcp/server -> core 0.14.1)
- CHANGELOG entry for 0.14.1

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…1030)

* fix(cli): embed bundled assets inside crate root for crates.io publish

include_str! paths pointed outside the package root (../../../.agents,
../../../extensions). cargo publish cannot bundle files outside the
package, so uteke-cli has failed to publish since June (stuck at 0.4.3)
while the release workflow hid the failure with continue-on-error.

Assets now live in crates/uteke-cli/assets/ and ship inside the .crate.
Verified locally: cargo package -p uteke-cli passes with full verify.

* ci(release): verify crates.io versions after publish

The continue-on-error on publish steps (added for the tag race fix)
also hides genuine publish failures. Verify all four crates report the
tagged version on crates.io; fail the job if any crate lags behind.

* style: cargo fmt

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
The v0.14.2 release reused the v0.13.0 notes because a committed
RELEASE_NOTES.md is preferred over auto-generation and nothing checked
which version it was for. The release shipped with wrong notes until
manually fixed.

The guard now requires the file to mention the tagged version. Also
remove the stale v0.13.0 file so the next release auto-generates from
the CHANGELOG unless someone writes fresh notes.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
, #1035) (#1038)

* fix(server,mcp): default recall strategy to hybrid, validate strategy at boundary (#1034, #1035)

HTTP: resolve strategy once (request > [recall] default_strategy config > hybrid). Invalid strategy returns 400 on all paths (bare recall, unified search, v1). The eager legacy recall that ran before strategy resolution is removed. Memory-only recall path routes through recall_hybrid with the same 3x over-fetch post-filter pattern used by recall_unified_memories (entity/category filters).

MCP: uteke_recall schema exposes strategy (vector|fts5|hybrid|graph). Default resolves to hybrid, invalid values return a loud JSON-RPC error (-32603) instead of silently falling back to vector.

Server startup: sanitize [recall] default_strategy from uteke.toml — invalid value warns and falls back to hybrid so a config typo cannot 400 every request with a message blaming the request.

Docs: api-reference.md and mcp.md now describe the hybrid default, HTTP 400 on invalid, and the config fallback chain.

Verified empirically against a scratch store: HTTP matrix 10/10, MCP harness 8/8 including engine parity (default == hybrid, warm cache) and loud bogus rejection.

* docs: regenerate api-reference via docgen (strategy hybrid default, 400 on invalid)

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…plate file (#1041)

* fix(ci): replace unquoted heredoc in release notes generation with template file

The unquoted heredoc << RELEASEEOF underwent shell expansion: markdown
backticks became command substitutions and executed on the runner.
v0.14.3 release: installer curl|sh ran, uteke-serve --port 8767 started
and blocked the job for 48 minutes (2 runs, deterministic).

Move the static tail (downloads table + quick start) to
scripts/release-notes-template.md and substitute __VER__ via sed.
Zero shell expansion over markdown content. Validated locally: generate
completes instantly, output byte-correct.

Fixes the release pipeline for all future releases.

* ci: re-trigger review bots (LLM API transient error)

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…pages, fix release-notes asset names (#1055)

* docs: sync stale version refs, roadmap v0.13–v0.14, merge comparison pages, fix release-notes asset names (#1043)

- README/README.id/AGENT.md/install.md: version + test-count updates (0.14.3, 530+ tests); AGENT.md now lists all 5 workspace crates incl. docgen
- docs/roadmap.md: add v0.13.0–v0.13.2 and v0.14.0–v0.14.3 entries from CHANGELOG
- comparison: merge comparison-2026.md (canonical long-form) into comparison.md, keep at-a-glance matrix + extraction table from the old page, drop dead /blog link
- extensions/hermes-memory-provider → extensions/hermes-uteke-memory (+ embedded assets copy and all path refs) — dir name no longer references the removed Mode B provider
- scripts/release-notes-template.md: download table filenames get v prefix to match actual release assets (#1043)

* fix(release): keep v prefix on pinned-install example in release notes template

Co-authored-by: VIVAAN-DHAWAN <VIVAAN-DHAWAN@users.noreply.github.com>

Same fix as #1046 — UTEKE_VERSION is used verbatim as the release tag by
install.sh, so the pin example needs the v prefix too. Picking it up here so
#1043 closes fully through this PR once the rest of the audit lands.

* Revert "fix(release): keep v prefix on pinned-install example in release notes template"

This reverts commit 222d067.
…1056)

Agents are advisory-mode by default: audit/check requests are not
authorization to mutate. Gate push/merge/cherry-pick from others' PRs,
comments/edits on others' PRs/issues, PR retargeting, and anything
irreversible or externally visible behind explicit maintainer approval.
Correct flow: analyze → present options → wait → execute approved scope
→ report. Real incident 2026-08-17 documented as cautionary example.
…1059)

Test hardcoded libonnxruntime.so; on macOS ORT_LIB_NAME is
libonnxruntime.dylib so the exact-match path returned None and the
assertion panicked. Use the platform constant instead.
All id call sites across uteke-core (remember, chunks, graph, edges,
timeline, orphans, import) now mint UUIDv7. Storage and wire format
unchanged (TEXT uuid); v4/v7 coexist — existing stores open unchanged.
Adds two tests: v7 version nibble + ascending order for consecutive
mints, and v4/v7 parse coexistence.
#1047) (#1061)

Root cause was NOT a partial delete — soft_forget() correctly marks the
row deprecated and removes the vector. The leak was read-side:
- list()/search_content() never filtered deprecated rows → ghosts in
  'uteke list' after forget
- store.count(None) counted deprecated rows → doctor/verify reported
  permanent DB/Index MISMATCH after any soft-forget
- load_all() (repair/verify source) included deprecated rows → repair()
  re-added soft-deleted vectors to the index, resurrecting them in recall

Fix, uniform active-only contract:
- list() (all 4 branches) + search_content(): AND deprecated = 0
- load_all(): AND deprecated = 0 (recompute_importance also stops
  wasting cycles on hidden rows)
- count(): active-only for both None and Some(ns) paths — directly
  comparable to index.len() in doctor/verify
- new count_all(): explicit include-deprecated totals for reporting

Regression test: isolated temp-dir store (':memory:' stores resolve the
vector index to a CWD file and cross-contaminate parallel test runs —
that shared uteke_index.usearch pollution is also why this bug hid).
Asserts soft-forgotten id absent from list/list-ns/load_all and doctor
reports no MISMATCH.
…ace keyword misses (#1051) (#1062)

uteke_search / CLI search go through store.search_content() (LIKE
substring), which mapped namespace=None to the 'default' namespace
instead of searching across all namespaces like list(None) does (#526).
Memories stored in any other namespace were invisible to keyword
search unless the caller explicitly passed that namespace.

- namespace=None now searches across all namespaces (deprecated rows
  still excluded)
- hyphenated identifiers keep working as literal substrings on the
  LIKE path (pinned by test), and the FTS5 phrase path already handles
  them (unicode61 adjacency) — probed both in-test

Regression test: cross-namespace hit via None, scoped hit via Some(ns),
full and partial hyphenated identifier matching.
… parity (#1037) (#1063)

recall_hybrid() applied salience/recency boosts only on the cache-miss
path; the cache-hit early return handed back raw cached scores. Same
query + strategy returned different scores cold vs warm (delta ~0.13).

Three-part fix:
- Cache-hit read path now re-applies boosts (boost → sort → truncate →
  min_score), identical post-processing to the miss path via shared
  apply_salience_recency_boosts() helper. Cache intentionally stores
  RAW scores — boosts are time-dependent and re-applied per read.
- Boost window: cache stores limit*4+16 candidates computed with
  min_score=0, so boosts can lift a memory from outside the raw top-N
  into the final top-N on warm reads too (cora finding — cached
  top-limit-only set would permanently exclude boostable candidates).
- min_score thresholding now happens AFTER boosts on BOTH paths
  (previously miss-path Vector/Fts5 filtered raw scores while hit-path
  filtered boosted scores).

Tests: cold/warm score parity (fails with max delta 0.125 pre-fix);
boost-reorder-across-limit; noop-config warm hits respect limit.
…umented (#1036) (#1064)

ExportEntry had no namespace field — every exported row lost its
namespace, so export→import collapsed multi-namespace stores into one.
Also root-caused the reporter's 36-row delta: export() reads load_all()
which filters deprecated=0 (soft-deleted rows excluded by design, but
undocumented).

- ExportEntry gains 'namespace' (serde default 'default' keeps old
  export files importable)
- export() serializes m.namespace on every row
- import(): caller-supplied namespace = explicit override for all rows;
  without it, per-row namespace wins → round-trips reconstruct
  namespaces
- docgen/api-reference regenerated (no route change, freshness check)

Test: 3-namespace × 2-row export shape (every row carries its ns),
parse-side attribution preservation, legacy-row default fallback.
…confirm to apply (#1050) (#1065)

A no-args uteke_dream call ran the maintenance pipeline with
dry_run=false against ALL namespaces while the tool description said
'Safe to run periodically'. Real incident: single exploratory call
mutated 4,067 rows store-wide.

- dry_run defaults to TRUE — a no-args call can only preview
- Applying requires explicit dry_run=false
- Unscoped applying runs refused unless confirm_large=true (two-flag
  decision for whole-store maintenance)
- Large-batch guard: applying runs projecting >100 changes refuse
  without confirm_large=true; preview computed first, so the refusal
  reports the projected count
- Output announces scope ([SCOPE: ALL NAMESPACES]) on both preview and
  apply paths
- Description rewritten: states destructive nature + dry-run-first
  guidance instead of 'Safe to run periodically'
- docs/mcp.md tool table updated
…doc_search scores, room ids (#1052) (#1066)

- uteke_stats: multi-line output — tiers (hot/warm/cold), pinned +
  deprecated split, recall cache hits/misses, and per-namespace
  breakdown when unscoped (was: single 'Total | Tags | DB' line)
- uteke_doc_search: per-result score, matched chunk heading + 120-char
  snippet (ranking was invisible; results were bare slug — title)
- uteke_room_memories: lines now include 8-char short id so the next
  tool call (pin/forget/graph edges) can act on the row
- uteke_room_recall description states the existing-room_id
  precondition instead of failing only at call time
- core: Store::count_pinned() + Uteke::{count_pinned, count_deprecated,
  namespace_counts} accessors (store field is private; MCP uses the
  public API surface)
…l ID-taking tools (#1048, #1049) (#1067)

MCP printed 8-char short ids in recall/list but every ID-consuming tool
required the full UUID (exact SQL match) — the basic loop recall → act
silently no-opped. resolve_id_prefix() existed in core (#794); MCP
never wired it.

- resolve_id() helper: full UUID passes through; any shorter prefix
  resolves via resolve_id_prefix(); ambiguous prefixes error loudly;
  unknown prefixes error instead of silent not-found
- Wired into uteke_forget, uteke_pin, uteke_unpin,
  uteke_graph_add_edge, uteke_graph_remove_edge
- NEW uteke_get {id} — full record by id/prefix, no truncation (fills
  the read-by-id gap; recall/search return ranked excerpts)
- NEW uteke_update {id, content?, tags?, metadata?, importance?,
  pinned?, memory_type?} — partial-update semantics matching HTTP PUT
  /memory (#659); content change re-embeds
- Tool schemas + docs/mcp.md: id params documented as UUID-or-prefix

Tests (5, scratch temp-dir stores): prefix + full + unknown resolution;
uteke_get full record via short id; pin via short id; forget short id
happy path + bogus prefix errors loudly; update partial fields leave
content untouched.
ajianaz and others added 23 commits September 15, 2026 14:45
GET /health was fully exempt from auth and returned version, memory
count, namespace count, and update info - letting any scanner
fingerprint an internet-exposed instance and size its memory store.

Health stays reachable WITHOUT a token (load balancers and uptime
probes keep working), but a request without valid credentials now
receives only {"status":"ok"}. A valid bearer token (admin or
read-only), or a server with auth disabled, still gets the full
payload - unchanged shape.

Closes #1252

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
* chore(release): v0.18.1 - version bump, changelog, docs sync

- Workspace + crate-level dependency versions 0.18.0 -> 0.18.1 (Cargo.lock synced)
- CHANGELOG: [Unreleased] -> [0.18.1] (#1243/#1251/#1245/#1252 fixes, #1246 footer)
- docs: upgrade keeps all artifacts in sync (install.md), /health auth
  semantics (configuration.md), health endpoint description (api_registry),
  api-reference.md regenerated via docgen
- README/AGENT.md/cli-reference/install.md version strings updated

* chore: retrigger PR checks after branch rename to chore/release-v0.18.1

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Bumps [toml](https://github.com/toml-rs/toml) from 1.1.5+spec-1.1.0 to 1.1.6+spec-1.1.0.
- [Commits](toml-rs/toml@toml-v1.1.5...toml-v1.1.6)

---
updated-dependencies:
- dependency-name: toml
  dependency-version: 1.1.6+spec-1.1.0
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.26.0 to 1.26.1.
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.26.0...v1.26.1)

---
updated-dependencies:
- dependency-name: uuid
  dependency-version: 1.26.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The weekly regeneration cron behind the MinIO-hosted chart no longer
exists, so the embed has been serving a stale image. Switch back to the
star-history.com live embed (theme-aware via <picture>); the self-hosted
pipeline stays as a backup artifact.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
* fix: doc list honors --namespace on CLI, HTTP, and MCP (#1268)

The documents List surface silently ignored the namespace on every
surface: the CLI variant had no namespace field at all (the global
--namespace flag was parsed but never used by the dispatcher), the
HTTP DocListParams struct lacked the field despite the main.rs help
text advertising it, and the MCP tool had no namespace argument.
All three returned byte-identical output regardless of the requested
namespace, making per-namespace document inventory impossible.

Changes:
- core: add Store::list_documents_ns(namespace, limit) with an exact
  namespace match in SQL; list_documents stays as the legacy global
  wrapper; doc_list/doc_list_roots now take Option<&str> namespace
- cli: doc list gains --namespace, falling back to the global
  --namespace flag; doc export stays global (None)
- server: DocListParams.namespace (serde default) wired to the core
  call - matches the already-documented help text
- mcp: uteke_doc_list accepts namespace
- regression test: scoped/global/NULL-namespace visibility

Verified: cargo check/test/clippy/fmt green (workspace 691 tests);
E2E against a backup-API snapshot - global 20 docs, default 12,
hermes 2, distinct outputs per namespace.

* fix: filter root docs by namespace in SQL before LIMIT (cora alert)

doc_list_roots fetched the N most-recent global roots and filtered by
namespace afterwards, so a scoped view could return short or empty
results when namespace matches fell outside the global top-N. Move the
filter into list_root_documents_ns SQL (parent_id IS NULL AND
(namespace = ?1 OR ?1 IS NULL)) applied before LIMIT - same semantics
as list_documents_ns.
…1270) (#1271)

* fix: unified recall scopes docs to namespace, reports honest scores (#1270)

recall_unified_all (the default CLI recall path) leaked documents
across namespaces and reported rank-derived scores that outranked
every memory:

- doc_search was called without a namespace (its ns param was _ns),
  so documents from any namespace - including NULL-namespace rows -
  appeared in every scoped recall
- doc scores were (k+1)/(k+1+rank): rank-0 reported 1.000 for every
  query, a pure rank function that beat all memory fusion scores
  (~0.16-0.19), flooding short-query results with the same doc set
- min_score was applied inside recall_hybrid against pre-boost
  rank-based scores (#1223), where it filters nothing meaningful

Changes:
- new Uteke::doc_search_in(query, limit, mode, namespace) retains
  only exact-namespace documents; NULL-namespace docs are global-
  view-only, matching the #1269 doc-list semantics
- unified doc arm keeps hybrid mode (index rebuilds evict chunk:
  vectors per #1110 - semantic-only would hide docs on affected
  stores) but reports the raw hybrid RRF sum (~0.016-0.033), same
  rank-based family as memory fusion base scores, never a fake 1.0
- memory arm called with min_score 0.0; the caller's threshold is
  applied post-merge on reported scores so --min/--strict work
- unified document results now carry their namespace

Verified: fmt/clippy clean; workspace 691 tests pass; E2E on a
PROD-snapshot store - short queries return only in-namespace
memories with honest scores, and 'memory lifecycle' surfaces the
ns=default chapter-6 document (0.016) instead of a cross-namespace
1.0 artifact.

* fix: over-fetch before namespace filter in doc_search_in (cora alert)

doc_search_in fetched the global top-limit results and only then
retained the requested namespace, so scoped searches could silently
return fewer results than exist when matching docs ranked below the
global top-N. Fetch 4x when scoping (mirrors the entity/category
post-filter heuristic on the memory path) and truncate to limit
after the retain.

* docs: correct stale comments on unified doc scoring (cora alert)

The score comment still said 'real cosine from the semantic doc arm'
from an earlier iteration of this change - it is the raw hybrid RRF
sum, and the min_score filter comment claimed both scales were honest
similarities. Spell out the actual caveat instead: both scales are
rank-based with different magnitudes (memory fusion ~0.2 max vs doc
hybrid ~0.033 max), so thresholds above ~0.033 filter all documents;
use --type memory + a vector strategy when cosine-style thresholding
is needed.
* feat: expose verify/repair over HTTP and MCP (#1266)

Issue #1266 reported that memories without a vector embedding are
invisible under the default fusion strategy. Triage against develop
showed the recall-side premise no longer holds: rrf_fuse_weighted
(fusion) and recall_rrf (hybrid) have been union merges since v0.16.0
(e27dbe5) - memories present only in the FTS5 arm are included. The
reported 'absent under fusion, found under fts5 rank 1' pattern
matches a stale vector index on a version-lagged serve binary (#1245
class): rows exist in SQLite but not in usearch, so query-time vector
arms degrade. uteke verify on a PROD snapshot confirmed exactly that
state: 10,675 rows vs 9,859 vectors = MISMATCH; repair rebuilt to
12,138 vectors (incl. 1,463 doc chunks) and re-verify is Consistent.

The actually missing pieces were write-path honesty and live-store
repairability:

- POST /verify and POST /repair expose the existing maintenance core
  over HTTP, so stores can be audited and repaired WITHOUT stopping
  uteke-serve (the old runbook required a restart, pitfall 0f lock
  contention). Write-token surface like other maintenance endpoints.
- MCP parity: uteke_verify / uteke_repair tools + execs, registered
  in the tool list (3-layer parity rule).
- api_registry entries added so the docgen parity test passes.

Verified: fmt/clippy clean; uteke-server + uteke-mcp test suites
green; registry parity test (registry_covers_handler_routes) green;
index rebuilt on a 12.5k-memory snapshot with verify read-back.

Refs #1266

* docs: regenerate api-reference for /verify and /repair (docgen)
The skill installed by 'uteke init' drifted from the release cadence
(0.11.0 vs 0.18.1 when #1267 was filed; the bundled copy had since
been refreshed to 0.16.0 but had no mechanism keeping it current).
Every newly onboarded agent starts from whatever release the skill
last mentioned.

Changes:
- bundled skill version line -> 0.18.1, plus a header note telling
  the reader the file tracks the CLI version and to re-run
  'uteke init' if it lags
- content refresh: stale-index pitfall 0g (fts5-finds-it / fusion-
  does-not symptom = index desync; verify then repair, now available
  over HTTP/MCP via #1272), the search-strategy guide (namespace =
  identity, tags = project scope, rooms = discussions; strategy
  table; rank-based score caveat; 2-3 keyword tip from #1267)
- CI gate: tests/skill_version_parity.rs fails when the bundled
  skill's version line lags CARGO_PKG_VERSION, and when the assets
  copy diverges from the canonical .agents/skills/uteke-memory copy
- canonical repo copy (.agents/skills/...) synced to the bundled one

Closes #1267
…trak-core-cloud) (#1275)

Co-authored-by: Anaz Satria Aji <ajianaz@users.noreply.github.com>
…uteke-cloud #81) (#1276)

Co-authored-by: Anaz Satria Aji <ajianaz@users.noreply.github.com>
#1273) (#1277)

* fix: report embedding write failures honestly across remember surfaces (#1273)

* test: stop polluting UTEKE_EMBEDDING_DIMS from remember status tests (#1273)

---------

Co-authored-by: Anaz Satria Aji <ajianaz@users.noreply.github.com>
)

* fix: use public Uteke wrappers instead of private store field

- Add room_add_document, room_remove_document, room_list_documents,
  document_list_rooms to Uteke public API (rooms.rs)
- Replace uteke.store.xxx with uteke.xxx in server handlers
- Add missing ns binding in /tags GET handler
- Apply cargo fmt

* feat: memory↔document cross-entity linking via [[doc-slug]] wikilinks

When [[slug]] in memory content doesn't match any memory, Uteke now
checks if it matches a document slug. If so, creates a 'references_doc'
edge (auto-backlinked as 'referenced_by').

New API:
- POST /memory/doc-refs → document slugs referenced by a memory
- POST /doc/mem-refs → memory IDs referencing a document
- Uteke::recall_memories_for_document(slug)
- Uteke::recall_documents_for_memory(memory_id)
- Store::edge_targets() / edge_sources() — generic typed edge queries

UnifiedSearchResult enriched with:
- linked_doc_slugs (for memory results)
- linked_memory_ids (for document results)

Refs #689

* fix: use read_body + typed deserialization, add missing ns binding

- Replace read_json() (nonexistent) with read_body<T>() pattern in
  /memory/doc-refs and /doc/mem-refs handlers
- Add missing let ns = parse_query_namespace(&path) in /tags handler
- Apply cargo fmt

* fix: use serde_json::json! instead of bare json! macro

The handlers used json!() which is not in scope — must be
serde_json::json!() to match the rest of handlers.rs.

* chore: remove bmad/wds skills, update docs for v0.7.3→v0.7.4 changes

- Remove _bmad/ folder (BMAD config/templates, not uteke-related)
- Remove .agents/skills/bmad-* (48 BMAD skill folders, ~14MB)
- Remove .agents/skills/wds-* (14 WDS skill folders, ~5MB)
- Remove .agents/skills/memory + sync (WDS session skills)
- Keep .agents/skills/uteke-memory (legitimate uteke skill, bump 0.6.7→0.7.3)

Docs updates (v0.7.3→HEAD):
- architecture.md: schema v13→v15, new endpoint tables (Memory Mutation,
  Room↔Document Junction, Cross-Entity References), room_documents info
- cli-reference.md: 9 new HTTP endpoints documented
- mcp.md: tool count 27→29, add graph_add_edge + graph_remove_edge
- CHANGELOG.md: populate [Unreleased] with all changes since v0.7.3
- README.md: add Partial Updates + Cross-Entity Linking features

* docs: fix Mode C handler — replace /proc with cwd-based agent resolution

The /proc/self/cmdline approach is unreliable because shell hooks run
as child subprocesses whose cmdline is the handler script, not the
gateway process. This caused agent name resolution to fail when hooks
were invoked from asyncio contexts (e.g., session expiry watcher).

Changes:
- Replace /proc/self/cmdline with cwd-based resolution from payload
- Dynamically resolve agent per invocation (not at module load time)
- Remove hardcoded UTEKE_BIN path check (assume uteke on PATH)
- Remove cron session skip (handler-level concern, not docs example)
- Pass agent name to recall function explicitly

* docs: fix docstring — remove false HERMES_PROFILE fallback claim

Cora review: docstring claimed 'Priority: cwd > HERMES_PROFILE env > fallback'
but code only checks cwd then returns 'default'. Fix docstring to match
actual behavior.

* docs: de-emphasize deprecated Mode B across Hermes integration docs

Mode B (memory-provider) was removed for Hermes on 2026-06-29 but the
docs still presented it as an active option alongside Mode A and C.

Changes:
- Architecture diagram: label Mode B as deprecated, add Mode C
- Comparison table: strikethrough Mode B column, reorder A/C first
- Mode B section: collapse 96 lines of deprecated content into 10-line
  blockquote with migration links
- Mode comparison summary: same strikethrough treatment
- Requirements: remove Mode B entry
- Non-Hermes agents section: unchanged (already has Hermes warning)

Result: 527 → 446 lines (-81 lines). Active modes (A+C) are now the
primary focus; Mode B is preserved as historical reference only.

* feat: add `uteke onboard` — interactive onboarding wizard

Guides new users from zero to productive in one command:
- Detects install (binary on PATH, existing store)
- Asks which AI agent they use (Hermes/Claude/Cursor/Pi/OpenCode)
- Picks integration mode (tool vs memory-provider)
- Toggles features on/off (Aging, Auto-maintenance, Graph rerank,
  Salience/Recency boost, Server mode)
- Writes uteke.toml config with selections
- Runs uteke init with selected agent automatically
- Prints a full feature showcase (all commands grouped by category)

Non-interactive mode: uteke onboard --yes --agent hermes --namespace default

Docs updated: getting-started.md, cli-reference.md, AGENT.md, CHANGELOG.md
New dep: which crate for PATH detection

* docs: add onboarding section to README.md and README.id.md

Add a prominent "🚀 Onboarding" section right after install, before
"Why Uteke?". Includes an agent-readable callout so when a user drops
the GitHub link to an AI agent (Hermes, Claude, etc.), the agent reads
the README and knows to run `uteke onboard.

* fix(docs): repair dangling Mode B anchor link

Rename of the Mode B heading (-> '~~Mode B~~ — memory-provider (deprecated)')
orphaned the cross-reference at line 245. Update the link target to the new
anchor #mode-b--memory-provider-deprecated.

Verified via github-slugger: 0 broken internal links.

* fix(docs): clean fragile '575577' anchor on Memory-Provider section

The heading 'Memory-Provider for Other Agents (#575/#577)' produced a
confusing concatenated anchor #memory-provider-for-other-agents-575577.
Drop the issue refs from the heading (move into the body) so the anchor
becomes the clean #memory-provider-for-other-agents. Fixes CodeCora alert.

Verified via github-slugger: 0 broken links; no other file references the
old anchor.

* fix(server): match Error::Validation instead of string in /memory/importance

The /memory/importance handler classified validation errors via
e.to_string().contains("importance must be"), coupling the 400/500
status to the exact wording of the validation message in store.rs.
If that wording changes, a 400 would silently degrade to a 500.

Match the typed Error::Validation(_) variant instead, mirroring the
pattern already used by PUT /memory.

Closes #697

* fix(core): validate room_id + doc_slug exist in room_add_document

The room_documents junction table has an FK on room_id (→ rooms) but
none on doc_slug, so POST /room/document/add accepted any doc_slug and
created dangling room→document links. A bogus room_id also surfaced as
a raw FK violation → 500.

Validate both room_id and doc_slug existence in room_add_document,
returning Error::Validation (→ 400) for unknown values. Update the
PUT /room/document/add handler to map Validation → 400 accordingly.

Closes #698

* fix: address PR #696 review feedback

🔴 Must Fix:
- AGENT.md: correct schema version v13 → v15 (room↔document junction, #689)
- onboard.rs: remove misleading get_stats() placeholder, drop count claim
- onboard.rs: write_config() now backs up existing uteke.toml to .bak and
  prompts for confirmation before overwriting (prevents credential loss)

🟡 Should Fix:
- prompt_integration_mode(): print message for custom agents (no longer silent)
- validate_agent(): now warns on unrecognized agents instead of being a no-op
- Banner boxes: replace misaligned Unicode box drawing with consistent ASCII
  print_banner() helper (fixes off-by-1 alignment, ambiguous em-dash width)
- --json flag: intentionally ignored in onboard to avoid mixing ASCII banners
  with parseable JSON output

🟢 Nice to Have:
- Install URL: main → develop (matches repo default branch convention)
- Add 7 unit tests for pure functions (get_toggle, validate_agent, print_banner,
  write_config TOML structure)

All tests pass: cargo fmt --check ✅, cargo clippy -D warnings ✅, cargo test (50 passed) ✅

Co-authored-by: ajianaz <reviewer>

* test: room operations test suite (#689 PR5)

Add comprehensive test coverage for room operations across two files:

memory/rooms.rs (33 tests, Store-level):
- CRUD: create, get, list (all + namespace filter), delete, duplicate error, cascade
- room_memories: link, idempotent link, updated_at propagation, recall with limit,
  author filter, empty room, limit=0 (all), author metadata enrichment
- get_room_memory_ids: with/without author filter
- room_stats: with memories (counts, participants, last_activity) + empty + nonexistent
- room_summary: empty room, with memories (clusters, tags, time_range), decisions,
  pinned highlights, nonexistent
- room_document: empty room, with memories (pinned section, type sections), nonexistent
- room_documents junction: add+list, idempotent add, remove, reverse lookup (document_list_rooms)

rooms.rs (14 tests, Uteke-level):
- CRUD roundtrip, namespace filter, delete
- room_stats (empty + nonexistent), room_summary (empty)
- room_document (empty + nonexistent)
- room_documents junction: add+list+remove, idempotent, reverse lookup
- remember_in_room + recall_room (4 tests, #[ignore] — requires ONNX embedder)

* fix: add missing Store import in rooms test module

* fix: resolve CI failures — unused imports + document validation in room tests

- Replace glob import  with explicit imports (Room, Document)
  to fix clippy unused-import error in both test modules
- Add  helper for creating valid documents
- Pre-create documents via  before attaching to rooms
  in 4 junction-table tests (room_add_document validates slug existence)

* style: rustfmt fixes

* fix: remove unused Room import + move junction tests to Store-level

- Remove unused super::Room import (clippy error)
- Move room↔document junction tests from rooms.rs to memory/rooms.rs
  because Uteke::doc_upsert requires ONNX embedder, but Store-level
  upsert_document works without it. Coverage is maintained.

* feat(theme): adopt @codecora/theme — Catppuccin Mocha, new base /uteke/docs/

- Replace custom theme with @codecora/theme (single-source Catppuccin tokens)
- Migrate config.ts to createConfig() helper
- Update base path: /docs/uteke/ → /uteke/docs/ (new routing scheme)
- Remove custom.css (now handled by shared theme)
- Accent: green

* feat: add enrich parameter to recall_unified for cross-entity linking (#689)

Add `enrich: bool` parameter to recall_unified() that populates
linked_doc_slugs and linked_memory_ids on UnifiedSearchResult using
the existing EDGE_REFERENCES_DOC infrastructure.

- Add enrich_memory_doc_links() and enrich_doc_memory_links() helpers
  that look up cross-entity edges and populate the appropriate fields
- Wire enrichment into recall_unified dispatcher (Memory/Document/All)
- Add enrich field to RecallRequest in HTTP API (default: false)
- Pass enrich through from server handler to recall_unified
- Update CLI and MCP callers with enrich=false for backward compat
- Add 3 integration tests (all #[ignore] -- require ONNX embedder)

Files modified:
- crates/uteke-core/src/lib.rs: signature, helpers, tests
- crates/uteke-server/src/types.rs: RecallRequest.enrich field
- crates/uteke-server/src/handlers.rs: pass enrich to recall_unified
- crates/uteke-cli/src/commands/recall.rs: backward compat
- crates/uteke-mcp/src/lib.rs: backward compat

* feat: add RoomSummary.referenced_documents and room_summary_with_docs (#689 PR3)

- Add referenced_documents field (Option<Vec<String>>) to RoomSummary struct
  with serde(default, skip_serializing_if) for backward compatibility
- Set referenced_documents: None at both RoomSummary construction sites
  in room_summary() for backward compat
- Add Store::room_summary_with_docs() that enriches a summary with
  document slugs from the room_documents junction table
- Add Uteke::room_summary_with_docs() high-level wrapper in rooms.rs
- Add 3 tests: with documents, empty room (None), nonexistent room (None)

* feat(cli): add --enrich flag for cross-entity recall links (#689 PR4)

Wire up the enrich parameter added by PR702 so users can opt into
cross-entity link resolution via uteke recall --enrich.

- Add --enrich bool flag to Recall subcommand in cli.rs
- Thread enrich from CLI dispatch → run_recall → recall_unified()
- Display linked_doc_slugs (📄 Docs) on memory results in human output
- Display linked_memory_ids count (🔗 Memories) on document results
- MCP recall left at enrich=false for now (separate enhancement)

* fix(theme): pin to codecora-theme with config.mjs (Node 24 compat)

* test: cross-entity integration tests (#689 PR6)

Store-level tests (no embedder needed, run in CI):
- cross_entity_doc_edge_round_trip: memory↔document edge CRUD
- cross_entity_doc_edge_with_backlink: backlink auto-generation
- cross_entity_doc_edge_idempotent: INSERT OR IGNORE dedup
- cross_entity_resolve_nonexistent_doc_slug_returns_none
- cross_entity_edge_targets_empty_for_no_edges

Room↔Document junction tests:
- room_doc_enrichment_full_flow: full link→list→summary→reverse
- room_doc_remove_unlink: unlink clears both directions
- room_doc_nonexistent_doc_rejected: Validation error
- room_doc_nonexistent_room_rejected: Validation error
- room_doc_shared_across_multiple_rooms: shared doc

E2E tests (#[ignore] = requires ONNX embedder):
- e2e_wikilink_creates_doc_edge_and_enriches: full wikilink→edge→enrich
- e2e_room_doc_memory_cross_entity: three-entity cross-linking

Closes #689

* style: rustfmt fixes for integration tests

* fix(theme): update codecora-theme pin (JSON import assertion fix)

* fix(docs): add ignoreDeadLinks to prevent broken link check failure

* fix(theme): pin codecora-theme to latest main (forward opts fix)

* docs: restructure — split getting-started, add install/comparison/feature pages

- Extract install.md from getting-started (curl, cargo, binary, docker)
- Extract rooms.md, time-travel.md, smart-decay.md, relationship-graph.md
- Extract benchmarks.md (from BENCHMARKS.md), add shell-hooks.md
- Add comparison.md with full feature comparison table
- Slim down index.md (ringkas 5-row comparison, link to /comparison)
- Update config.ts sidebar (halaman terpisah, bukan anchor links)
- Remove old BENCHMARKS.md (merged into benchmarks.md)

Install routes updated in CF Worker:
  /{product}/install -> 302 -> raw GitHub install.sh
  /install (legacy) -> 302 -> uteke install.sh

* feat: enable salience/recency boosts by default (opt-out) (#721)

Change SalienceRecencyConfig::default() weights from 0.0 to 0.1.

- Both salience and recency boosts are now ON by default (weight 0.1)
- CLI: absent flag = default 0.1, --salience/--recency = config 0.15,
  --no-salience/--no-recency = 0.0 (opt-out)
- Server/API: inherits the 0.1 default automatically
- Boost is additive and small enough to not dominate embedding similarity
- Adopted from Hermes holographic memory analysis

Breaking: none — the boost is additive and tiny (max +0.1).
Backward compatible: users can disable via --no-salience --no-recency.

* feat: Jaccard token similarity as post-RRF reranking signal (#719)

Add Jaccard token overlap as an orthogonal recall signal (#719):
- New jaccard.rs module with tokenize() and jaccard_similarity()
- Post-RRF additive boost when jaccard_weight > 0.0
- CLI config [recall].jaccard_weight (default 0.0 = off)
- Setter API: Uteke::set_jaccard_weight()
- Tag tokens included in content token set for richer overlap

Jaccard catches different cases than BM25 (IDF-weighted) and vector
cosine (semantic). When enabled (recommended 0.10-0.15), it boosts
results with high token overlap regardless of term rarity or
embedding distance.

Closes #719

* fix(docs): deprecate hermes-memory-provider for Hermes + add HTTP transport

- README: add deprecation notice for Hermes (removed 2026-06-29),
  clarify template is for pi/claude/cursor agents only
- README: add transport mode section (subprocess vs HTTP)
- plugin.yaml: bump to v1.1.0, add deprecation comment
- __init__.py.tmpl: add dual transport support (subprocess + HTTP),
  add UTEKE_SERVER_URL/UTEKE_TOKEN config, refactor recall/remember
  into separate _subprocess/_http methods, extraction guard for missing binary
- docs/integrations/hermes.md: link to extension template source in Mode B section

* feat: trust scoring with feedback API (#718)

Add helpful/unhelpful feedback mechanism to adjust memory importance:

Core (uteke-core):
- Uteke::feedback_helpful() → importance += 0.05
- Uteke::feedback_unhelpful() → importance -= 0.10
- Asymmetric: penalty > reward (adopted from Hermes trust scoring)
- Clamped to [0.0, 1.0], returns new importance value

CLI:
- uteke feedback <id> helpful|unhelpful
- JSON and human-readable output
- FeedbackAction enum (Helpful, Unhelpful)

Server API:
- POST /memory/feedback { id, feedback }
- Validates UUID, returns { id, feedback, delta, importance }

Closes #718

* style: fix cargo fmt formatting (#722)

* style: fix cargo fmt formatting (#723)

* fix: use raw SQL in feedback_adjust instead of non-existent store.get() (#725)

* fix: import FeedbackAction in commands/mod.rs (#725)

* fix: avoid redundant reference in feedback command (#725)

* feat: auto-contradiction scan as Dream pipeline phase (#720)

Add Phase 4 (Contradict) to the Dream maintenance pipeline.

Algorithm:
- Load top 200 most recently updated memories (O(n²) bounded)
- For each pair: check tag overlap (Jaccard ≥ 0.3) + embedding
  cosine similarity (≤ 0.6 threshold)
- High tag overlap + low content similarity = contradiction
- Creates graph_edges with relation 'contradicts' (older → newer)

Pipeline order: Lint → Backlinks → Dedup → **Contradict** → Orphans → Compact → Verify

Supports dry-run mode (reports without creating edges).
CLI: uteke dream --phases contradict

Closes #720

* fix: use GraphStore::new for add_edge in contradict phase (#726)

* style: fix cargo fmt formatting for contradict phase (#726)

* fix: prefix unused ns variable with underscore in load_recent_memories (#726)

* docs: update CHANGELOG, CLI reference, and architecture for v0.7.4 features

- CHANGELOG: 3 Added entries (trust scoring, jaccard, contradiction)
  2 Changed entries (salience default-on, dream 7 phases)
- cli-reference: updated recall flags (--salience/--recency default-on,
  --jaccard), dream phases (contradict), new feedback command + HTTP endpoint
- architecture: salience opt-out, dream pipeline 7 phases

* chore: release v0.8.0 — version bump, CHANGELOG, and docs update

- Bump workspace version 0.7.3 → 0.8.0
- Update all sub-crate internal deps to 0.8.0
- Finalize CHANGELOG: add missing PR entries, new Deprecated and Dependencies sections
- Rename [Unreleased] → [0.8.0] with 2026-07-17 date
- Update docs version refs: cli-reference, install, architecture (v0.7.4 → v0.8.0)

* refactor(api): rename POST /room/document → POST /room/summary (#735)

BREAKING: The room summary document endpoint is renamed from POST /room/document
to POST /room/summary to eliminate confusion with the room↔document junction
routes (/room/document/add, /room/document/list, /room/document/remove).

Changes:
- Server: POST /room/summary is the new primary endpoint
- Server: POST /room/document retained as deprecated alias with warn! log
- Core: room_document() → room_summary_document() across all crates
- CLI: 'uteke room document' command unchanged (help text updated)
- MCP: uteke_room_document tool updated to use new function
- Docs: cli-reference, docker, mcp, rooms updated

Closes #735

* fix: rename to POST /room/summary-document — avoid collision with /room/summary

Clippy caught unreachable pattern: POST /room/summary already used by
room_summary() (tag clustering). Renamed to POST /room/summary-document
to eliminate ambiguity with both junction routes AND the clustering endpoint.

Refs #735

* feat(api): URL prefix versioning /api/v1 and /api/v2 (#737)

Adds API versioning middleware to uteke-server.

Changes:
- ApiVersion enum (V1, V2) with path prefix parser
- /api/v1/* routes return v1 format (flat recall results for backward compat)
- /api/v2/* routes return current v2 format (wrapped UnifiedSearchResult)
- Unversioned routes (/recall, /remember, etc.) continue to work (→ latest)
- Health endpoint now includes api_versions and api_latest fields
- to_v1_flat() adapter converts UnifiedSearchResult → v1 flat format

v1 vs v2 differences:
- v1 recall: [{id, content, score, namespace, tags, ...}] (flat)
- v2 recall: [{memory: {id, content, ...}, score}] (wrapped)

Routes affected:
- /recall → /api/v1/recall (flat) or /api/v2/recall (wrapped)
- /remember, /memory, /forget, /list, /search, /stats, etc.
- /room/*, /doc/* — all sub-routes versioned
- /health — unversioned, includes version info

* feat(config): configurable dream pipeline thresholds (#731)

Replaces hardcoded dream pipeline constants with configurable values.

Changes:
- DreamConfig struct (uteke-core + uteke-cli config)
  - contradict_similarity_threshold: 0.6 (cosine > this → NOT contradiction)
  - contradict_tag_jaccard_min: 0.4 (up from 0.3, reduces false positives)
  - contradict_max_memories: 200 (O(n²) scan limit)
  - dedup_threshold: 0.92 (cosine > this → merge candidate)
  - orphan_importance_threshold: 0.15 (safer than old 0.3)
- MaintenanceConfig defaults changed to safer values:
  - auto_aging_enabled: true → false (opt-in)
  - auto_aging_interval_hours: 6 → 24 (daily)
  - auto_dream_interval_days: 3 → 7 (weekly)
- DreamConfig wired into CLI main.rs and server main.rs via set_dream_config()
- dream.rs reads from self.dream_config instead of const values
- DEFAULT_ORPHAN_THRESHOLD updated 0.3 → 0.15
- Server reads [dream] section from uteke.toml

Config example:
  [dream]
  contradict_similarity_threshold = 0.6
  contradict_tag_jaccard_min = 0.4
  contradict_max_memories = 200
  dedup_threshold = 0.92
  orphan_importance_threshold = 0.15

Closes #731

* fix: resolve type mismatch and format issues (#731)

- consolidate() expects f32 not f64 — remove incorrect cast
- Server dream config: unwrap_or_default() for Option<usize> returns 0
  (wrong), use unwrap_or(DreamConfig::default().*) instead
- Format: restructure server dream config block for rustfmt compliance

* fix(format): collapse consolidate call to single line per rustfmt

* fix(onboard): resolve clippy errors in test code

- Remove unused 'toggles' vec in test_write_config_generates_valid_toml
- Replace useless format! with raw string literal
- Remove stray closing parenthesis

* fix(core): robust embedding model download with timeout, retry, streaming (#740)

- Add connect timeout (30s) and read timeout (300s) to prevent
  infinite hangs on slow/unstable connections
- Retry up to 3 attempts on transient failures with cleanup
- Stream download to disk via 64KB chunks instead of buffering
  entire 187MB model_data file in RAM
- Add progress indicator (file size + percentage milestones)
- Add human-readable byte formatting (KB/MB/GB)
- Verify content-length matches downloaded bytes

* fix: use checked_div for clippy compliance (#744)

* docs: add SECURITY.md and PR template

- SECURITY.md: supported versions, vulnerability reporting process, SLA
- PULL_REQUEST_TEMPLATE.md: type checklist, CI verification, conventional commits

* fix: use GitHub Private Vulnerability Reporting instead of public issue

Cora caught that instructing reporters to open a public issue with
[SECURITY] prefix contradicts the 'do not open a public issue' policy.
GitHub issues are public by default — only Private Vulnerability Reporting
provides proper confidentiality.

* fix(core): prevent os error 33 on Windows by reading usearch index from locked file handle

* style(core): apply cargo fmt to fix CI check

* fix(core): filter deprecated memories in recall() (#748)

recall() vector search path was missing a deprecated filter, causing
deprecated memories to appear in search results (61.7% in reported case).

FTS5 path already filters at SQL level (m.deprecated = 0).
recall_at_time() already filters in post-filter.

Adding the filter in recall() fixes all downstream paths:
- Vector strategy
- Hybrid RRF (calls recall())
- Graph rerank (calls recall_rrf -> recall())

* chore: release v0.9.0 — version bump, CHANGELOG

v0.9.0 features:
- uteke onboard interactive wizard
- API URL versioning /api/v1, /api/v2
- Configurable dream pipeline thresholds
- SECURITY.md + PR template

v0.9.0 fixes:
- Deprecated memories in vector search (#748)
- Windows OS error 33 (#747)
- Embedding download robustness (#740)

* fix: bump intra-workspace dependency versions to 0.9.0

uteke-cli, uteke-mcp, and uteke-server had hardcoded uteke-core/mcp
version = "0.8.0" instead of using workspace version. Updated all
to 0.9.0 to match workspace.package.version.

* docs: add contributors section to v0.9.0 changelog

Thank @webhop123 for Windows OS error 33 fix (#747).

* fix(api): ensure leading slash on versioned API path after strip_prefix

ApiVersion::from_path() stripped '/api/v1/' prefix producing 'recall'
instead of '/recall', causing all /api/v1/* and /api/v2/* routes to
return 404. The fix ensures the stripped path always starts with '/'.

Also adds @gnoviawan to v0.9.0 CHANGELOG contributors.

* fix(api): ensure leading slash on versioned API path after strip_prefix

ApiVersion::from_path() stripped '/api/v1/' prefix producing 'recall'
instead of '/recall', causing all /api/v1/* and /api/v2/* routes to
return 404. The fix strips '/api/v1' (no trailing slash), keeping the
leading '/' in the remainder for correct route pattern matching.

Also adds @gnoviawan to v0.9.0 CHANGELOG contributors.

* chore: release v0.9.1 — patch fix for API versioning routes

- Fix ApiVersion::from_path() strip_prefix producing path without leading /
- Add @gnoviawan to CHANGELOG contributors
- Bump workspace + intra-workspace deps to 0.9.1

* chore: upgrade Rust edition 2021 → 2024 (#755)

- edition 2021 → 2024 (requires Rust 1.85+)
- rust-version 1.75 → 1.85 (edition 2024 MSRV)

Audit: no unsafe extern blocks, no gen keyword, no raw pointer derives.
Codebase uses explicit dyn, no edition-breaking patterns found.

Closes #755

* fix: edition 2024 — remove explicit ref bindings + apply rustfmt

Edition 2024 introduces implicitly-borrowing patterns, making
`Some(ref x)` an error. Also changes rustfmt import grouping.

- doc.rs:348: Some(ref json_str) → Some(json_str)
- room.rs:95: Some(ref q) → Some(q)
- cargo fmt --all (38 files, import reorder)

* fix: wrap set_var/remove_var in unsafe blocks (edition 2024)

Edition 2024 makes std::env::set_var and std::env::remove_var unsafe.
All test code using these functions now wraps calls in unsafe {} blocks.

- uteke-core/src/lib.rs: 5 set_var + 10 remove_var
- uteke-cli/src/config.rs: 14 set_var + 19 remove_var

* fix: clippy edition 2024 lints — repeat_n + is_none_or

- graph_rerank.rs: repeat(?).take(n) → repeat_n(?, n)
- lib.rs: .map_or(true, |_| true) → .is_none_or(|_| true)

* fix: clippy let_binding_from_block in slug_from_path (edition 2024)

Remove unnecessary let binding — return the expression directly.

* fix: expose room_remember via HTTP + forget returns 404 (#762)

Bug A: POST /remember ignored 'room' field because remember_in_room()
was never exposed via HTTP. Added POST /room/remember endpoint that
calls uteke.remember_in_room() — stores memory AND links to room.

Bug B: DELETE /forget returned 200 even when memory ID doesn't exist.
Now checks existence first and returns proper 404.

Tags field: verified code path is correct — deserialization and storage
both handle tags properly. The production 500 was an infrastructure
issue (embedder), not a code bug.

* chore: release v0.10.0 — edition 2024 + room/remember endpoint

- Rust edition 2021 → 2024, min Rust 1.85
- POST /room/remember HTTP endpoint
- DELETE /forget returns 404 for non-existent IDs
- README/docs Rust version badges updated

* feat: rewrite hermes-memory-provider as pre_llm_call plugin hook

* fix(test): update memory_provider tests for pre_llm_call plugin

* fix(plugin): remove stale @staticmethod, use context manager for file read

- @staticmethod on module-level function causes TypeError at runtime
- open() without context manager leaks file handle
Both found by CodeCora review.

* fix: uteke-tool template dynamic namespace and room ns params

* fix: skip DB open for upgrade command (#772), fix doc/delete query parsing (#776)

Fix #772: uteke upgrade hangs when database is locked
- Add Commands::Upgrade to early-exit block in main.rs (alongside
  Completions, Init, Onboard, Bench). Upgrade only needs network +
  filesystem — no store access required.

Fix #776: DELETE /doc/delete fails to parse query params
- doc_delete handler passed full URL to parse_query_param(), which
  only splits on '&' and '=' without stripping the path portion.
- Use req.url().query() instead, which returns just the query string.
  Matches the pattern already used in parse_query_namespace().

* fix CI: make upgrade module pub(crate), use split pattern for query string

- commands/mod.rs: mod upgrade → pub(crate) mod upgrade (was private,
  main.rs couldn't access it)
- handlers.rs: req.url().query() → req.url().split('?').nth(1) because
  tiny_http Request::url() returns &str, not url::Url

* feat: migrate default data dir ~/.uteke → ~/.codecora/uteke with auto-migration (#773)

- uteke_home() now defaults to ~/.codecora/uteke
- Auto-migrates legacy ~/.uteke on first run (rename + cross-device fallback)
- CLI global_config_path() uses uteke_core::uteke_home() instead of hardcoded path
- Updated all docs, CLI help text, and extension templates
- Test input strings for set_namespace_in_toml intentionally kept (simulates old user config)
- CHANGELOG.md historical entries untouched

* style: apply cargo fmt to lib.rs

* fix: remove redundant &format! borrow in Error::generic calls (clippy)

* fix: address review — Windows paths in INSTALL.md, sandbox test to temp dir

* fix: prevent env var test pollution between parallel test threads

Both uteke_home tests now save and restore HOME/UTEKE_HOME env vars
to prevent race conditions when Rust runs tests in parallel.

* style: use if-let instead of match for single-pattern clippy

* release: bump v0.10.1

* fix: isolate test_uteke_home_with_env from parallel env var pollution

Race condition: test_uteke_home_default_no_migration sets HOME and
removes UTEKE_HOME while test_uteke_home_with_env sets UTEKE_HOME.
When running in parallel, remove_var from one thread can clobber
set_var from another, causing the assertion to see the default path
instead of the UTEKE_HOME override.

Fix: also set HOME to a unique temp dir in the env test, matching
the pattern already used by the default-path test.

* docs: fix hermes integration examples and add API notes

* chore: bump quinn-proto 0.11.14 → 0.11.15 (GHSA-4w2j-m93h-cj5j)

Fixes Trivy HIGH vulnerability in transitive dependency chain:
reqwest → quinn → quinn-proto

Also syncs Cargo.lock with workspace version 0.10.1.

* chore(deps): bump which from 7.0.3 to 8.0.5

Bumps [which](https://github.com/harryfei/which-rs) from 7.0.3 to 8.0.5.
- [Release notes](https://github.com/harryfei/which-rs/releases)
- [Changelog](https://github.com/harryfei/which-rs/blob/master/CHANGELOG.md)
- [Commits](https://github.com/harryfei/which-rs/compare/7.0.3...8.0.5)

---
updated-dependencies:
- dependency-name: which
  dependency-version: 8.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix: filter deprecated memories from room operations (#784, #785, #786) (#790)

* fix: filter deprecated memories from room operations (#784, #785, #786)

#784 — room_stats, recall_room, get_room_memory_ids now filter
deprecated=0 via INNER JOIN. Previously counted deprecated memories
causing 76% stat inflation (620 vs 148). Added 3 test cases.

#785 — POST /room/recall query is now optional. When query is
None/empty, falls back to chronological recall_room instead of
returning 400 error.

#786 — Added docs/api-reference.md with full HTTP API reference
covering 30+ endpoints. Added to VitePress sidebar.

Closes #784, #785, #786

* style: cargo fmt

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix: runtime ORT dispatch for non-AVX2 CPUs + validation error mapping (#709, #789) (#792)

* feat(onnx): runtime ORT library dispatch for non-AVX2 CPUs (#709)

Switch from ort's download-binaries (which bundles AVX2-only lib) to
load-dynamic, enabling runtime selection between AVX2 and SSE4.2 ORT
shared libraries.

Changes:
- Cargo.toml: ort features = [load-dynamic, ndarray, api-18]
  (api-18 works around pykeio/ort#547 vitis EP compile error)
- New embed/ort_init.rs: CPU feature detection + library resolution
  (ORF_LIB_PATH env > ./libonnxruntime.so > ./ort-legacy/libonnxruntime.so)
- engine.rs: call init_ort_environment() before OnnxEmbedder::new()
- Non-ORT backends (custom, ollama, openai) are unaffected

CI packaging and legacy ORT sidecar build will follow in next commits.

* ci(release): add ORT sidecar packaging + legacy SSE4.2 build

Step 5 & 6 — CI pipeline and release packaging for load-dynamic ORT.

Release workflow changes:
- Add build-ort-legacy job: builds ORT 1.24.4 from source with
  onnxruntime_USE_AVX=OFF (SSE4.2 only) for SIGILL fix (#709)
- Add package-legacy job: assembles legacy Linux x64 bundle with
  ort-legacy/ sidecar alongside standard ORT libraries
- All platforms now download prebuilt ORT shared libs from GitHub
  releases (load-dynamic requires runtime .so/.dylib/.dll)
- Copy symlinks + actual .so files for proper dlopen resolution
- Docker build: arch-specific ort-amd64/ort-arm64 subfolders to
  avoid cross-arch .so contamination in multi-platform builds

Dockerfile changes:
- Copy ORT shared libs to /usr/local/lib/ with ldconfig
- Select arch-specific ORT libs via TARGETARCH
- Copies libonnxruntime_providers_shared.so too

ort_init.rs changes:
- Add system lib path fallback (/usr/local/lib, /usr/lib, /lib)
  for Docker containers where binary and .so are in different dirs
- Update module doc with full 5-step resolution order

Refs: #709

* fix: return 400 for Validation errors in /room/remember (#789)

* ci(release): add Windows legacy SSE4.2 ORT build (#709)

- Add build-ort-legacy-windows job: builds ORT from source on windows-latest
  with AVX/AVX2/AVX512 explicitly disabled (SSE4.2 only)
- Add package-legacy-windows job: combines standard bundle + legacy DLLs
- Update release job to depend on package-legacy-windows
- Add Windows legacy row to release notes table
- Guard Unix-only system lib paths with #[cfg(unix)] in ort_init.rs

* docs: update CHANGELOG for #709 #785 #789

* style: apply cargo fmt to engine.rs

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore(deps): bump uuid from 1.23.5 to 1.24.0

Bumps [uuid](https://github.com/uuid-rs/uuid) from 1.23.5 to 1.24.0.
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](https://github.com/uuid-rs/uuid/compare/v1.23.5...v1.24.0)

---
updated-dependencies:
- dependency-name: uuid
  dependency-version: 1.24.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* feat: auto-generated API reference docs via schemars (#786) (#795)

Add crates/docgen — a standalone binary that reads the route registry
and type schemas to generate docs/api-reference.md automatically.

Architecture:
- api_registry.rs: single source of truth for endpoint metadata
  (method, path, description, request/response types, related issues)
- types.rs: #[derive(JsonSchema)] behind docgen feature flag
- docgen binary: reads registry + generates JSON schemas via schemars,
  renders to structured markdown with field tables
- CI: docs-check job fails if api-reference.md is stale

The docgen feature flag ensures zero runtime overhead — schemars is
only compiled when generating docs, not in production builds.

Closes #786

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore(deps): bump thiserror from 2.0.18 to 2.0.19

Bumps [thiserror](https://github.com/dtolnay/thiserror) from 2.0.18 to 2.0.19.
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](https://github.com/dtolnay/thiserror/compare/2.0.18...2.0.19)

---
updated-dependencies:
- dependency-name: thiserror
  dependency-version: 2.0.19
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* chore(deps): bump serde_json from 1.0.150 to 1.0.151

Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.150 to 1.0.151.
- [Release notes](https://github.com/serde-rs/json/releases)
- [Commits](https://github.com/serde-rs/json/compare/v1.0.150...v1.0.151)

---
updated-dependencies:
- dependency-name: serde_json
  dependency-version: 1.0.151
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix: accept short ID prefix in DELETE /forget (#794) (#796)

list and room_recall display only 8-char UUID prefixes, but forget
required a full UUID — making it impossible to delete memories from
CLI output.

- Add resolve_id_prefix() to crud + operations (LIKE query, returns
  full ID for exact match, Err for ambiguous)
- Handler tries full UUID first, then resolves prefix on failure
- Ambiguous prefix (>1 match) returns 400 with count
- Still returns 404 if prefix doesn't match any memory

Closes #794

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore: v0.10.2 pre-release — version bump + docs sync (#797)

- Bump workspace version 0.10.1 → 0.10.2
- CHANGELOG: promote [Unreleased] → [0.10.2], add entries for
  #784 (deprecated memory filter), #785 (optional room/recall query),
  #794 (short ID prefix in forget), auto-generated API docs (#786),
  quinn-proto security patch
- README.md: v0.7.3 → v0.10.2, test count 206 → 431
- README.id.md: v0.7.2 → v0.10.2, test count 206 → 431,
  ~/.uteke → ~/.codecora/uteke
- INSTALL.md: version examples 0.0.2/0.0.7 → 0.10.2
- Regenerate docs/api-reference.md (version bump)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore(deps): bump clap from 4.6.1 to 4.6.4

Bumps [clap](https://github.com/clap-rs/clap) from 4.6.1 to 4.6.4.
- [Release notes](https://github.com/clap-rs/clap/releases)
- [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md)
- [Commits](https://github.com/clap-rs/clap/compare/clap_complete-v4.6.1...clap_complete-v4.6.4)

---
updated-dependencies:
- dependency-name: clap
  dependency-version: 4.6.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* Release v0.10.2 (#798)

* docs: fix hermes integration examples and add API notes

* chore: bump quinn-proto 0.11.14 → 0.11.15 (GHSA-4w2j-m93h-cj5j)

Fixes Trivy HIGH vulnerability in transitive dependency chain:
reqwest → quinn → quinn-proto

Also syncs Cargo.lock with workspace version 0.10.1.

* fix: filter deprecated memories from room operations (#784, #785, #786) (#790)

* fix: filter deprecated memories from room operations (#784, #785, #786)

#784 — room_stats, recall_room, get_room_memory_ids now filter
deprecated=0 via INNER JOIN. Previously counted deprecated memories
causing 76% stat inflation (620 vs 148). Added 3 test cases.

#785 — POST /room/recall query is now optional. When query is
None/empty, falls back to chronological recall_room instead of
returning 400 error.

#786 — Added docs/api-reference.md with full HTTP API reference
covering 30+ endpoints. Added to VitePress sidebar.

Closes #784, #785, #786

* style: cargo fmt

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix: runtime ORT dispatch for non-AVX2 CPUs + validation error mapping (#709, #789) (#792)

* feat(onnx): runtime ORT library dispatch for non-AVX2 CPUs (#709)

Switch from ort's download-binaries (which bundles AVX2-only lib) to
load-dynamic, enabling runtime selection between AVX2 and SSE4.2 ORT
shared libraries.

Changes:
- Cargo.toml: ort features = [load-dynamic, ndarray, api-18]
  (api-18 works around pykeio/ort#547 vitis EP compile error)
- New embed/ort_init.rs: CPU feature detection + library resolution
  (ORF_LIB_PATH env > ./libonnxruntime.so > ./ort-legacy/libonnxruntime.so)
- engine.rs: call init_ort_environment() before OnnxEmbedder::new()
- Non-ORT backends (custom, ollama, openai) are unaffected

CI packaging and legacy ORT sidecar build will follow in next commits.

* ci(release): add ORT sidecar packaging + legacy SSE4.2 build

Step 5 & 6 — CI pipeline and release packaging for load-dynamic ORT.

Release workflow changes:
- Add build-ort-legacy job: builds ORT 1.24.4 from source with
  onnxruntime_USE_AVX=OFF (SSE4.2 only) for SIGILL fix (#709)
- Add package-legacy job: assembles legacy Linux x64 bundle with
  ort-legacy/ sidecar alongside standard ORT libraries
- All platforms now download prebuilt ORT shared libs from GitHub
  releases (load-dynamic requires runtime .so/.dylib/.dll)
- Copy symlinks + actual .so files for proper dlopen resolution
- Docker build: arch-specific ort-amd64/ort-arm64 subfolders to
  avoid cross-arch .so contamination in multi-platform builds

Dockerfile changes:
- Copy ORT shared libs to /usr/local/lib/ with ldconfig
- Select arch-specific ORT libs via TARGETARCH
- Copies libonnxruntime_providers_shared.so too

ort_init.rs changes:
- Add system lib path fallback (/usr/local/lib, /usr/lib, /lib)
  for Docker containers where binary and .so are in different dirs
- Update module doc with full 5-step resolution order

Refs: #709

* fix: return 400 for Validation errors in /room/remember (#789)

* ci(release): add Windows legacy SSE4.2 ORT build (#709)

- Add build-ort-legacy-windows job: builds ORT from source on windows-latest
  with AVX/AVX2/AVX512 explicitly disabled (SSE4.2 only)
- Add package-legacy-windows job: combines standard bundle + legacy DLLs
- Update release job to depend on package-legacy-windows
- Add Windows legacy row to release notes table
- Guard Unix-only system lib paths with #[cfg(unix)] in ort_init.rs

* docs: update CHANGELOG for #709 #785 #789

* style: apply cargo fmt to engine.rs

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* feat: auto-generated API reference docs via schemars (#786) (#795)

Add crates/docgen — a standalone binary that reads the route registry
and type schemas to generate docs/api-reference.md automatically.

Architecture:
- api_registry.rs: single source of truth for endpoint metadata
  (method, path, description, request/response types, related issues)
- types.rs: #[derive(JsonSchema)] behind docgen feature flag
- docgen binary: reads registry + generates JSON schemas via schemars,
  renders to structured markdown with field tables
- CI: docs-check job fails if api-reference.md is stale

The docgen feature flag ensures zero runtime overhead — schemars is
only compiled when generating docs, not in production builds.

Closes #786

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix: accept short ID prefix in DELETE /forget (#794) (#796)

list and room_recall display only 8-char UUID prefixes, but forget
required a full UUID — making it impossible to delete memories from
CLI output.

- Add resolve_id_prefix() to crud + operations (LIKE query, returns
  full ID for exact match, Err for ambiguous)
- Handler tries full UUID first, then resolves prefix on failure
- Ambiguous prefix (>1 match) returns 400 with count
- Still returns 404 if prefix doesn't match any memory

Closes #794

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore: v0.10.2 pre-release — version bump + docs sync (#797)

- Bump workspace version 0.10.1 → 0.10.2
- CHANGELOG: promote [Unreleased] → [0.10.2], add entries for
  #784 (deprecated memory filter), #785 (optional room/recall query),
  #794 (short ID prefix in forget), auto-generated API docs (#786),
  quinn-proto security patch
- README.md: v0.7.3 → v0.10.2, test count 206 → 431
- README.id.md: v0.7.2 → v0.10.2, test count 206 → 431,
  ~/.uteke → ~/.codecora/uteke
- INSTALL.md: version examples 0.0.2/0.0.7 → 0.10.2
- Regenerate docs/api-reference.md (version bump)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): Windows legacy ORT C4875 suppress + Docker artifact download (#799)

- Add /wd4875 to Windows legacy ORT CMake to suppress C4875
  (non-string literal [[gsl::suppress]] deprecated) treated as error
- Remove merge-multiple from Docker artifact download — v7 auto-extracts
  which loses the .tar.gz wrapper the script expects

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): Windows legacy ORT C4875 suppress + Docker artifact download (#801)

- Add /wd4875 to Windows ORT cmake (C4875 gsl::suppress deprecated)
- Remove merge-multiple from Docker artifact download (v7 auto-extracts)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): Windows ORT CMP0091 + Docker/Windows skip-decompress (#802)

* docs: fix hermes integration examples and add API notes

* chore: bump quinn-proto 0.11.14 → 0.11.15 (GHSA-4w2j-m93h-cj5j)

Fixes Trivy HIGH vulnerability in transitive dependency chain:
reqwest → quinn → quinn-proto

Also syncs Cargo.lock with workspace version 0.10.1.

* fix: filter deprecated memories from room operations (#784, #785, #786) (#790)

* fix: filter deprecated memories from room operations (#784, #785, #786)

#784 — room_stats, recall_room, get_room_memory_ids now filter
deprecated=0 via INNER JOIN. Previously counted deprecated memories
causing 76% stat inflation (620 vs 148). Added 3 test cases.

#785 — POST /room/recall query is now optional. When query is
None/empty, falls back to chronological recall_room instead of
returning 400 error.

#786 — Added docs/api-reference.md with full HTTP API reference
covering 30+ endpoints. Added to VitePress sidebar.

Closes #784, #785, #786

* style: cargo fmt

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix: runtime ORT dispatch for non-AVX2 CPUs + validation error mapping (#709, #789) (#792)

* feat(onnx): runtime ORT library dispatch for non-AVX2 CPUs (#709)

Switch from ort's download-binaries (which bundles AVX2-only lib) to
load-dynamic, enabling runtime selection between AVX2 and SSE4.2 ORT
shared libraries.

Changes:
- Cargo.toml: ort features = [load-dynamic, ndarray, api-18]
  (api-18 works around pykeio/ort#547 vitis EP compile error)
- New embed/ort_init.rs: CPU feature detection + library resolution
  (ORF_LIB_PATH env > ./libonnxruntime.so > ./ort-legacy/libonnxruntime.so)
- engine.rs: call init_ort_environment() before OnnxEmbedder::new()
- Non-ORT backends (custom, ollama, openai) are unaffected

CI packaging and legacy ORT sidecar build will follow in next commits.

* ci(release): add ORT sidecar packaging + legacy SSE4.2 build

Step 5 & 6 — CI pipeline and release packaging for load-dynamic ORT.

Release workflow changes:
- Add build-ort-legacy job: builds ORT 1.24.4 from source with
  onnxruntime_USE_AVX=OFF (SSE4.2 only) for SIGILL fix (#709)
- Add package-legacy job: assembles legacy Linux x64 bundle with
  ort-legacy/ sidecar alongside standard ORT libraries
- All platforms now download prebuilt ORT shared libs from GitHub
  releases (load-dynamic requires runtime .so/.dylib/.dll)
- Copy symlinks + actual .so files for proper dlopen resolution
- Docker build: arch-specific ort-amd64/ort-arm64 subfolders to
  avoid cross-arch .so contamination in multi-platform builds

Dockerfile changes:
- Copy ORT shared libs to /usr/local/lib/ with ldconfig
- Select arch-specific ORT libs via TARGETARCH
- Copies libonnxruntime_providers_shared.so too

ort_init.rs changes:
- Add system lib path fallback (/usr/local/lib, /usr/lib, /lib)
  for Docker containers where binary and .so are in different dirs
- Update module doc with full 5-step resolution order

Refs: #709

* fix: return 400 for Validation errors in /room/remember (#789)

* ci(release): add Windows legacy SSE4.2 ORT build (#709)

- Add build-ort-legacy-windows job: builds ORT from source on windows-latest
  with AVX/AVX2/AVX512 explicitly disabled (SSE4.2 only)
- Add package-legacy-windows job: combines standard bundle + legacy DLLs
- Update release job to depend on package-legacy-windows
- Add Windows legacy row to release notes table
- Guard Unix-only system lib paths with #[cfg(unix)] in ort_init.rs

* docs: update CHANGELOG for #709 #785 #789

* style: apply cargo fmt to engine.rs

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* feat: auto-generated API reference docs via schemars (#786) (#795)

Add crates/docgen — a standalone binary that reads the route registry
and type schemas to generate docs/api-reference.md automatically.

Architecture:
- api_registry.rs: single source of truth for endpoint metadata
  (method, path, description, request/response types, related issues)
- types.rs: #[derive(JsonSchema)] behind docgen feature flag
- docgen binary: reads registry + generates JSON schemas via schemars,
  renders to structured markdown with field tables
- CI: docs-check job fails if api-reference.md is stale

The docgen feature flag ensures zero runtime overhead — schemars is
only compiled when generating docs, not in production builds.

Closes #786

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix: accept short ID prefix in DELETE /forget (#794) (#796)

list and room_recall display only 8-char UUID prefixes, but forget
required a full UUID — making it impossible to delete memories from
CLI output.

- Add resolve_id_prefix() to crud + operations (LIKE query, returns
  full ID for exact match, Err for ambiguous)
- Handler tries full UUID first, then resolves prefix on failure
- Ambiguous prefix (>1 match) returns 400 with count
- Still returns 404 if prefix doesn't match any memory

Closes #794

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore: v0.10.2 pre-release — version bump + docs sync (#797)

- Bump workspace version 0.10.1 → 0.10.2
- CHANGELOG: promote [Unreleased] → [0.10.2], add entries for
  #784 (deprecated memory filter), #785 (optional room/recall query),
  #794 (short ID prefix in forget), auto-generated API docs (#786),
  quinn-proto security patch
- README.md: v0.7.3 → v0.10.2, test count 206 → 431
- README.id.md: v0.7.2 → v0.10.2, test count 206 → 431,
  ~/.uteke → ~/.codecora/uteke
- INSTALL.md: version examples 0.0.2/0.0.7 → 0.10.2
- Regenerate docs/api-reference.md (version bump)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): Windows legacy ORT C4875 suppress + Docker artifact download (#799)

- Add /wd4875 to Windows legacy ORT CMake to suppress C4875
  (non-string literal [[gsl::suppress]] deprecated) treated as error
- Remove merge-multiple from Docker artifact download — v7 auto-extracts
  which loses the .tar.gz wrapper the script expects

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): Windows ORT CMP0091 policy + Docker/Windows skip-decompress

- Add CMAKE_POLICY_DEFAULT_CMP0091=NEW to ORT build so CMAKE_MSVC_RUNTIME_LIBRARY
  propagates to FetchContent deps (protobuf). Fixes LNK2038 RuntimeLibrary mismatch.
- Add skip-decompress: true to Docker download-artifact to preserve .tar.gz files
- Add skip-decompress: true to Windows legacy packaging to preserve .zip artifact

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): remove Windows legacy ORT build + upgrade download-artifact to v8 (#803)

- Remove build-ort-legacy-windows job (ORT v1.24.4 removed
  --enable_msvc_static_runtime, internal protobuf hardcodes /MT
  causing unfixable LNK2038)
- Remove package-legacy-windows job (depends on removed ORT build)
- Upgrade download-artifact v4→v8 in Docker job with skip-decompress:
  true (v4 doesn't support skip-decompress, was silently ignored)
- Update release notes: remove Windows legacy bundle reference
- Linux legacy bundle preserved (no CRT mismatch on Linux)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): simplify Docker artifact extraction - v4 default auto-extract (#804)

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): create binaries dir inside release-artifacts after cd (#806)

The mkdir -p binaries ran before cd release-artifacts, creating the
directory in the workspace root. Subsequent mv commands wrote to
release-artifacts/binaries/ instead, leaving the Docker context
binaries/ empty. Fix: cd first, then mkdir.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ci): keep binaries/ at workspace root for Docker context (#808)

Dockerfile does 'COPY binaries/ ./' expecting binaries/ at the build
context root (workspace root). The previous fix (#806) moved 'cd
release-artifacts' before 'mkdir binaries', which placed binaries/
inside release-artifacts/ — invisible to Docker build context.

Root cause: download-artifact@v4 downloads into release-artifacts/,
but Docker context is workspace root (.). Fix: don't cd. Create
binaries/ at workspace root, find artifacts via 'find release-artifacts'.

Fixes the 'COPY binaries/ not found' Docker buildx error.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* fix(ort): force /MD runtime for Windows legacy ORT build

ONNX Runtime v1.24.4 build from source on Windows fails with LNK2038
RuntimeLibrary mismatch: protobuf (MT_StaticRelease) vs onnxruntime
(MD_DynamicRelease). Add -DCMAKE_MSVC_RUNTIME_LIBRARY=MultiThreadedDLL
to force dynamic CRT across all dependencies.

Bump cache key v1→v2 to invalidate cached build without the flag.

* fix(ort): force /MD + /NODEFAULTLIB for Windows ORT build

CMAKE_MSVC_RUNTIME_LIBRARY alone insufficient — protobuf submodule
ignores it and compiles with /MT. Add explicit /MD to CMAKE_CXX_FLAGS
and CMAKE_C_FLAGS, plus /NODEFAULTLIB:LIBCMT;LIBCPMT to linker to
prevent static CRT symbols from being linked.

Bump cache key v2→v3.

* ci: drop Windows legacy ORT build and package jobs

Windows ORT build from source fails with CRT mismatch (LNK2038) —
protobuf submodule hardcodes /MT regardless of CMAKE_MSVC_RUNTIME_LIBRARY.

Removes:
- build-ort-legacy-windows job
- package-legacy-windows job
- package-legacy-windows from release needs
- Windows legacy bundle from release notes

99%+ Windows CPUs (Intel Haswell 2013+, AMD Excavator 2015+) support
AVX2. Pre-built AVX2 release already works. Linux legacy bundle
retained for server-grade old hardware (Celeron J4125/N4020).

* ci: filter release artifacts to avoid Docker buildx metadata

Download step used merge-multiple:true without pattern, downloading
ALL artifacts including Docker buildx metadata (.dockerbuild zip).
This corrupt artifact caused "download failed after 5 retries".

Fix: add pattern: uteke-* to only download release binary artifacts.

* ci: fix release notes template — heredoc with proper YAML escaping

* chore(deps): bump actions/cache from 4 to 6

Bumps [actions/cache](https://github.com/actions/cache) from 4 to 6.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/v4...v6)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* fix: ORT init cascade — AVX2 fallthrough, error message accuracy, embedder init cache

Fixes #820, #821, #822

#820 — ort_init.rs: AVX2 path no longer early-returns Err when standard
library is not found in exe_dir. Falls through to system paths
(/usr/local/lib, /usr/lib, /lib) which is the common Docker layout.
Added !avx2 guard on legacy path to prevent AVX2 CPUs from accidentally
loading SSE4.2-only library. Descriptive error at the end lists all
searched locations.

#821 — engine.rs: Replaced misleading 'CPU may lack required SIMD support'
error message with actionable 'Set ORT_LIB_PATH to the library file,
or use the standard release bundle.' The old message sent users down
the wrong debugging path (checking CPU capabilities instead of library
placement).

#822 — lib.rs: Added embedder_init_error: Mutex<Option<String>> field
that caches the first embedder initialization failure. Subsequent calls
to ensure_embedder() return immediately with the cached error instead
of retrying the expensive ORT/model init on every request. This prevents
log spam and CPU waste in Docker environments where the ORT library is
persistently missing. Uses String storage because Error type is not Clone.

Tests: 379 passed, 0 failed.

* fix: TTL-based error cache for transient network failures (#822 review)

- Change embedder_init_error from Mutex<Option<String>> to
  Mutex<Option<(String, Instant, bool)>> with permanent/transient flag
- ONNX failures (missing lib) cached permanently — no point retrying
- OpenAI/Ollama failures use 60s TTL — auto-retry after outage passes
- Address Cora code review: prevent permanent disable on transient errors
- Fix rustfmt string continuation in non-onnx error message

Fixes CodeCora review feedback on #822.

* release: v0.10.3 — ORT init fixes, dep bumps

* revert: undo PR #837 merge (develop → main)

Reverts all changes merged via PR #837 (develop → main).
Main restored to pre-merge state (8a12376).

Reason: PR was merged with --admin bypass on failing CI
(Branch Naming check failed for develop branch).
Must fix pr-checks.yml before re-merging.

* chore(release): v0.11.0 — code + docs changes from develop

Re-applies all v0.11.0 content that was reverted by PR #838.
Includes: version bump, changelog, code fixes (doc_move, recall score,
governance docs), issue templates, API reference.

* chore: merge develop to main for v0.14.0 release (#1020)

* fix(docs): standardize recall latency to ~45ms

3 files still referenced ~30ms (stale from early benchmarks).
Actual measured P50 at 1K-10K memories is ~45ms per benchmarks.md.
Updated: architecture.md, mcp.md, index.md

* chore: harden .gitignore + restructure repo for public safety

- Add internal/ to .gitignore (prevents future strategy/launch doc leaks)
- Add benchmarks/longmemeval/results_*/ to .gitignore (ephemeral data)
- Add docs/package-lock.json to .gitignore (VitePress build artifact)
- Move blog/comparison-2026.md → docs/comparison-2026.md (consolidate docs)
- Remove stale benchmarks/longmemeval/results_diverse/ (raw output, not summary)
- Remove docs/package-lock.json from tracking

Audit confirms: zero internal/ files in entire git history after filter-repo scrub.

* feat: hybrid as default recall strategy + import fixes (#1005, #1014) (#1015)

* feat(bench): batch import + strategy flag + API embedding auto-config

- Replace 53x individual remember calls with single JSONL batch import (10x speedup)
- Add --strategy flag to pass vector|hybrid to uteke recall
- Auto-configure embedding API from EMBED_API_KEY/EMBED_API_BASE env vars
- Add --chunk-sessions flag for session chunking (Tier 2 prep)
- Dedup recall results by session_id (first occurrence = highest rank)
- Raise subprocess timeout 120s -> 600s for large imports

Initial 5Q results: hybrid R@5=1.000 vs vector R@5=0.800 (+20pp)

* fix(bench): only mark sessions inserted after import succeeds

Address Cora findings:
- Move inserted_sids population to after batch import success
- Parse import response to verify imported_count > 0
- Log warning if import returns 0 inserted

* fix(bench): resolve uteke binary by absolute path to avoid x86_64 PATH clash

Background subprocess calls were resolving to /opt/data/.cargo/bin/uteke
(x86_64) instead of target/release/uteke (AArch64). Now resolves relative
to repo root with shutil.which fallback.

* docs(bench): add 50Q hybrid results — R@5 98.0%, R@10 100%

Strategy comparison (uteke only):
- Vector 500Q: R@5=85.4%, R@10=88.5%, NDCG@5=0.810
- Hybrid 50Q: R@5=98.0%, R@10=100%, NDCG@5=0.960
- Improvement: +12.6pp R@5

Hybrid uses RRF (k=60) fusion of vector + FTS5 search.
1 miss at R@5 (single-session-user), recovered at R@10.

run_eval.py changes:
- Add --strategy flag (vector|hybrid)
- Throttle: taskset -c 0-1 + nice -n 19
- Absolute binary path resolution
- Timeout: 900s per question

* fix(core): add dedup, retry, and auto_link to import path (#1005)

Import pipeline was missing 3 features that remember() has:
1. Dedup check — cosine >= 0.95 skips duplicate entries
2. Retry on embedding failure — 3 retries with backoff
3. Auto-link cosine edges — graph edges for imported memories

Changes:
- import_export.rs: call check_duplicate() before insert, use
  retry_embed() instead of single-attempt embed(), call
  auto_link_cosine() after successful insert
- operations.rs: make retry_embed() and check_duplicate() pub(crate)
  so they're accessible from import_export.rs

Import path is now semantically consistent with remember() path.

* fix(core): cross-compile ORT_LIB_NAME for Android/iOS (#1014)

Add target_os = "android" to Linux .so branch and target_os = "ios"
to macOS .dylib branch. Without these, uteke-core fails to compile
for mobile targets with E0425 (cannot find value ORT_LIB_NAME).

Android uses libonnxruntime.so (same as Linux, loaded via jniLibs).
iOS uses libonnxruntime.dylib (same as macOS, framework embedded).

This unblocks uteke-mobile cross-compilation.

* feat(core): hybrid as default recall strategy

Change default_strategy from vector to hybrid (RRF: vector + FTS5).

Benchmark justification (LongMemEval-S):
- Vector 500Q: R@5=85.4%, R@10=88.5%
- Hybrid 50Q:  R@5=98.0%, R@10=100.0%
- Improvement: +12.6pp R@5

Changes:
- config.rs: default_strategy = hybrid + assert in test
- cli.rs: update help text default to hybrid
- recall.rs: update comment to reflect new default
- configuration.md: update all references
- cli-reference.md: reorder examples, hybrid first as default

Users who want vector-only: set default_strategy = vector in config
or use --strategy vector flag.

* fix(bench): guard taskset/nice with sys.platform check

Cora finding: taskset is Linux-only, would FileNotFoundError on macOS.
Now conditionally applied only when sys.platform == 'linux'.

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* perf: Phase 2 — skip update check in batch mode, pre-truncate embedding text (#1006, #1002) (#1016)

#1006: CLI update check skipped when UTEKE_NO_UPDATE_CHECK env var is set.
Benchmark script sets this automatically, saving ~500ms per subprocess call.

#1002: Pre-truncate text before tokenizer to avoid wasted CPU on tokens
beyond MAX_SEQ_LEN (2048). Uses 4 chars/token heuristic with char-boundary
safety.

#1003: Already resolved — idx_memories_namespace index exists in SCHEMA_INDEXES.
#1004: Already resolved — compute_graph_signals uses single batched SQL query.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* feat: Phase 3 — lifecycle/deprecated, memory tools guide, source provenance (#1007, #1010, #1012, #1013) (#1017)

* feat: Phase 3 — lifecycle/deprecated endpoint, memory tools guide, source provenance (#1007, #1010, #1012, #1013)

#1007: GET /lifecycle/deprecated — list deprecated memories with sunset info
- list_deprecated() in aging.rs with DeprecatedMemoryInfo struct
- Handler + route + API registry entry

#1010: Memory tools guide injection
- guide.rs module with default_guide() for system prompt injection
- CLI: uteke guide command
- API: GET /guide endpoint

#1012: Implicit memory hierarchy docs
- docs/organizing-memories.md — type + importance pattern
- VitePress nav entry

#1013: Auto-populate source provenance
- CLI extraction: set source_label from input filename, source_type='extract'
- Server extraction: set_source on each extracted fact
- CLI output: display source_type alongside source in verbose mode

* docs: regenerate api-reference.md for new endpoints (#1007, #1010)

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* feat: scene-segmented extraction with priority scoring (#1009) (#1018)

SYSTEM_PROMPT now requests scene-segmented JSON output with type and
priority per fact. parse_facts handles three formats: scene-segmented
nested JSON, flat object array with type/priority, and legacy flat
string array (backward compatible).

ExtractedFact struct carries content, scene, fact_type, priority.
CLI and server callers use remember_typed + set_importance + scene tag.

Offline mode unaffected — ExtractedFact::flat wraps existing strings.
9 new tests cover nested parsing, backward compat, dedup, priority
range validation.

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* chore: bump version to 0.14.0 (#1019)

- Version bump to 0.14.0
- CHANGELOG entry for v0.14.0
- Docs: cli-reference scene-segmented extraction section
- Docs: memory-lifecycle deprecated endpoint

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>

* ci: trigger security workflow on PRs to main

------…
* chore(release): complete v0.18.2 metadata lost in #1278 squash

The #1278 squash carried AGENT.md and CHANGELOG (staged correctly) but lost
the in-place edits applied after staging: Cargo.toml/Cargo.lock stayed 0.18.1
and the README version strings kept v0.18.1. This restores them on top of
develop so the release line is consistent again.

Also moves the #1273 Unreleased changelog entry into [0.18.2] with a note:
both #1270/#1271 (this backport) and #1273 land on main together when the
release is tagged, so the shipped version section must list both.

* fix(release): 0.18.2 version lockstep — bundled skill asset + core contract

Follows #1274 (skill parity test) and #1276 (tiered api_registry / core
contract generation): both artifacts embed the workspace version and went
stale when the 0.18.2 bump was reapplied on top of develop. Bumps the
bundled uteke-memory-skill.md version line and regenerates
docs/core-contract.json via docgen.

* fix(release): sync .agents uteke-memory skill copy to 0.18.2

The skill_bundled_matches_repo_copy parity test requires the bundled asset
(crates/uteke-cli/assets/uteke-memory-skill.md) and the repo wiki copy
(.agents/skills/uteke-memory/SKILL.md) to be byte-identical; only the
bundled side was bumped in the previous commit.

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…d events, MCP tool (schema v20) (#1280)

* feat(core): audit-grade timeline — history survives forget, deprecated events, MCP tool (schema v20)

Owner decision 2026-09-18 (contract doc kontrak-core-cloud/03):
timeline is the audit layer and must survive memory deletion.

- migration v19->v20: rebuild timeline_events WITHOUT the FK
  ON DELETE CASCADE (defensive: creates the table if an old store
  never materialized it) + backfill `created` events (actor=backfill)
  for memories lacking one (~9.7k in PROD)
- deprecate_with_reason now records a `deprecated` event with reason
  (the fleet's dominant delete traffic — 1.4k deprecations — was
  previously unwired); idempotent re-deprecation writes no duplicate
- hard forget() writes a `forgot` tombstone BEFORE the delete so the
  audit trail exists even on pre-v20 stores
- new TimelineEventType::Deprecated variant (append-only enum rule)
- new MCP tool uteke_timeline (id + limit, mirrors uteke_provenance)
- tests: migration preserves rows/drops FK/backfills once; soft and
  hard forget event assertions (7 timeline tests + 567 lib tests green)

Next up (separate PR): actor plumbing from caller identity (CLI/MCP/
HTTP) — Created events still default to a NULL actor.

* fix(core): cora review — forget tombstone only for existing memories; v20 atomicity documented

---------

Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
…1283)

* chore(docs): evergreen README hero banner + install URL consistency (#1282)

The hero banner baked stale figures (v0.4.2, star count 16, 312 tests,
wrong org slug codecora/uteke, wrong install URL) and is the image
embedded in the launch tweet that new visitors see.

- Add docs/assets/uteke-banner.svg as the source of truth. Evergreen by
  design: no version/star/test numbers (those live in the shields
  badges); install URL codecora.dev/uteke/install; ~45ms claim per the
  conservative-claim decision.
- scripts/regen-banner.py renders the PNG at 2x via cairosvg; the
  generated PNG is committed because GitHub renders README images from
  the repo.
- Fix docs/comparison.md install URL (codecora.dev/install ->
  codecora.dev/uteke/install).
- Checklist note for AGENTS.md release rules is proposed in the PR body
  (agent-instruction file needs owner consent).

* chore(docs): use the official Uteke icon (uteke-mobile) as the banner mascot

Replaces the hand-drawn SVG mascot with the real product icon
(docs/assets/uteke-icon.png, from uteke-mobile website/icon-512.png):
the teal brainy-owl with the exposed brain and idea spark.

cairosvg cannot embed raster images, so scripts/regen-banner.py now
composites the icon into the avatar slot (rounded corners, PIL) after
the SVG render; the SVG carries a comment pinning the avatar slot
coordinates. Pillow >=10 resampling API.

* chore(docs): teal accent banner with mobile footer link

Adopt the winning dev-banner pattern (Turso/Neon league): bottom teal glow,
keyword highlighting in the headline, single teal accent across install
command and meta rows. Footer links the mobile app (https://uteke.app) with
a local-first privacy line. Still fully evergreen: no version/star/test
numbers baked in.
…1281 Phase 1) (#1284)

* feat(recall): budgeted context pack — --pack on CLI, HTTP, and MCP (#1281 Phase 1)

Adds a selection primitive over unified recall: rank-order preserving
greedy fill of a caller-supplied character budget.

- uteke-core: new pack_mode module (pack_context + ContextPack envelope
  {selected, skipped, budget_used, budget_chars}); Uteke::
  recall_unified_packed wraps recall_unified. Skip reasons: excluded
  (caller-supplied memory IDs already injected this turn) and budget
  (no longer fits). Char-counted (multibyte-safe), per-item overhead
  constant. Ranking untouched — fusion stays the default strategy;
  deterministic, LLM-free. 5 unit tests.
- CLI: recall --pack / --budget <chars> / --exclude-ids <ids> with
  human + --json output. Entity/category filters are honoured; the
  packed path loudly rejects --at/--related/--where instead of
  silently dropping them.
- HTTP: POST /recall accepts pack, budget_chars, exclude_ids; pack
  honours the caller's search_type with the same 400 validation as the
  plain path; integration test covers envelope shape, exclusion
  reporting, and an impossible budget.
- MCP: uteke_recall accepts pack/budget_chars/exclude_ids; tool schema
  updated.
- Docs: cli-reference.md flags + examples, mcp.md tool description,
  CHANGELOG [Unreleased].

Phase 2 (MMR diversity) intentionally NOT included — experiment gated
on LongMemEval + redundancy benchmarks per #1281.

Testing: pack_mode 5/5; uteke-server 37 live tests green incl. the new
pack API test; workspace suite green before test additions. Live E2E
against a scratch UTEKE_HOME with real ONNX embeddings: remember x3,
--pack human + JSON envelope (3 selected, 235/4000 chars), --exclude-ids
reports reason=excluded for the right IDs, --budget 120 fills 1 item at
60 chars and skips 2 as budget.

* fix(server): pack recall loudly rejects at/after/before + regen api docs

CodeCora review on #1284 flagged that the pack branch validated only
search_type: a request with pack+at silently returned non-time-travel
results while the plain path honours the filters (and the CLI pack path
already rejects --at loudly).

- POST /recall with pack + at/after/before now returns the same 400 as
  the CLI contract; integration test extended.
- docs/api-reference.md regenerated via docgen for the new public
  recall_unified_packed surface (API Docs Fresh gate).
Bumps [clap_complete](https://github.com/clap-rs/clap) from 4.6.9 to 4.6.11.
- [Release notes](https://github.com/clap-rs/clap/releases)
- [Changelog](https://github.com/clap-rs/clap/blob/main/CHANGELOG.md)
- [Commits](clap-rs/clap@clap_complete-v4.6.9...clap_complete-v4.6.11)

---
updated-dependencies:
- dependency-name: clap_complete
  dependency-version: 4.6.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [vecq-core](https://github.com/codecoradev/vecq) from 0.3.0 to 0.3.1.
- [Release notes](https://github.com/codecoradev/vecq/releases)
- [Changelog](https://github.com/codecoradev/vecq/blob/develop/CHANGELOG.md)
- [Commits](codecoradev/vecq@v0.3.0...v0.3.1)

---
updated-dependencies:
- dependency-name: vecq-core
  dependency-version: 0.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [clap](https://github.com/clap-rs/clap) from 4.6.6 to 4.6.7.
- [Release notes](https://github.com/clap-rs/clap/releases)
- [Changelog](https://github.com/clap-rs/clap/blob/main/CHANGELOG.md)
- [Commits](clap-rs/clap@clap_complete-v4.6.6...clap_complete-v4.6.7)

---
updated-dependencies:
- dependency-name: clap
  dependency-version: 4.6.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix(api): honor namespace filter on GET /room/memories (#1288)

GET /room/memories parsed only room_id, limit, and author; any
namespace query param was silently ignored, so callers asking for
their own namespace in a cross-namespace room got a 200 with the
full unfiltered list (issue reports a 6-namespace room returning
72 entries instead of 19).

Core: recall_room becomes a compatibility wrapper delegating to a
new recall_room_scoped(room_id, author, namespace, limit). The
duplicate 4-variant SQL collapses into one dynamically composed
WHERE clause — literal fragments stay in SQL text, every value is
bound as a parameter (same owned Box<dyn ToSql> pattern as
bulk.rs), so no string interpolation of inputs.

Server: parse the namespace query param and pass it through;
usage string and /tools endpoint-registry description updated
(docs regenerated).

Tests: core multi-namespace room test (scoped, combined
author+namespace, legacy signature unchanged, nonexistent ns
yields empty) and an HTTP-level server test. Validation: cargo
fmt --check, clippy -D warnings, full workspace tests EXIT=0,
feature-matrix checks, docgen fresh.

* docs(changelog): add #1288 fix entry to Unreleased
…#1291)

uteke-serve now serves the endpoint registry as JSON — method, path, tier, description, request/response types, and issues per route — serialized straight from api_registry::ENDPOINTS, the same single source of truth that generates docs/api-reference.md, so consumers can validate against the real contract instead of stale notes (GET vs POST, room_id vs room, body-vs-query params). mod api_registry is un-gated from the docgen feature (it is runtime data now); the registry entry is LAB tier so the CORE contract list is untouched; usage text, docgen grouping, and CHANGELOG updated; 3 new server tests cover payload shape, auth roles, and the 404 catch-all.
* chore(release): v0.19.0 — version bump, CHANGELOG, skill lockstep

* chore(release): regenerate core-contract.json for 0.19.0
@github-actions

github-actions Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

🔍 Cora AI Code Review

⚠️ Review could not complete. Cora produced an empty result. Check the workflow logs for errors.


Review powered by cora-code · BYOK · MIT

Comment thread Cargo.lock Outdated

[[package]]
name = "toml"
<<<<<<< HEAD
Comment thread Cargo.toml Outdated
]

[workspace.package]
<<<<<<< HEAD
Comment thread README.id.md Outdated
menjalankan suite penuh dengan **nol panggilan LLM di jalur retrieval**: embedding
lokal, satu CPU, deterministik.

<<<<<<< HEAD
Comment thread README.md Outdated
the full suite with **zero LLM calls in the retrieval path**: local embeddings,
one CPU, deterministic.

<<<<<<< HEAD
Comment thread crates/uteke-cli/Cargo.toml Outdated
vecq = ["uteke-core/vecq"]

[dependencies]
<<<<<<< HEAD
Comment thread crates/uteke-core/src/operations.rs Outdated
// row is stored FTS5-only and stays keyword-searchable. Vector
// search for this row becomes available once an embedding is
// supplied via the injected-embedding path or `uteke repair`.
<<<<<<< HEAD
Comment thread crates/uteke-core/src/timeline.rs Outdated
Tagged,
/// Memory deleted.
Forgot,
<<<<<<< HEAD
Comment thread crates/uteke-mcp/Cargo.toml Outdated
vecq = ["uteke-core/vecq"]

[dependencies]
<<<<<<< HEAD
Comment thread crates/uteke-mcp/src/lib.rs Outdated
tool_list(),
tool_get(),
tool_provenance(),
<<<<<<< HEAD
Comment thread crates/uteke-server/Cargo.toml Outdated
path = "src/main.rs"

[dependencies]
<<<<<<< HEAD
@ajianaz
ajianaz force-pushed the chore/release-v0.19.0 branch from cba5099 to 03a8fdd Compare September 28, 2026 23:53
@ajianaz
ajianaz merged commit 8adbb86 into main Sep 29, 2026
20 checks passed
@ajianaz
ajianaz deleted the chore/release-v0.19.0 branch September 29, 2026 00:03
@ajianaz ajianaz mentioned this pull request Oct 5, 2026
1 task done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants