Skip to content

Deja Vu v0.8.0: More Reliable, Bounded Recall

Latest
Latest

Choose a tag to compare

View all tags
@focaxisdev focaxisdev released this 18 Oct 03:36
v0.8.0
4222180
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Publication status

This GitHub source release is published from commit 4222180. @focaxisdev/deja-vu@0.8.0 is published on npm. Independent registry verification on 2026-10-18 confirmed version 0.8.0 and the observed latest dist-tag, with npm gitHead matching this release commit.

Highlights

  • Preserve the three-file adoption path and Protocol v0.4, with no memory-file migration or new runtime dependency.
  • Fix false no-memory results by qualifying candidates before hybrid ranking; separate candidate search breadth from returned-output budgets.
  • Cache lexical token sets with update/delete invalidation and validate limits before expensive work.
  • Add opt-in exact query aliases, bounded prompt projection, metadata-only embedding reuse, bounded embedding caches and per-memory cache ownership.
  • Improve deletion/supersession compensating recovery, source-retrieval guidance and qualifier-loss warnings. Include the previously unpublished 0.7.1 CLI/initialization reliability fixes.

Evidence and limitations

  • A specific 10,000-record shared-cue storage-search microbenchmark measured 30.74 → 2.61 ms. This is not a product-wide speedup.
  • Authored aliases improved 2/13 → 10/13 positive recalls in each split of a small same-author synthetic dataset. Exact aliases are not a multilingual semantic model.
  • The second-round default-mode resident API median increased about 12.4%; that measurement does not isolate ownership cost. Ownership separately increases provider calls while releasing entries after deletion.
  • Byte budgets are not token counts. Projection remains untrusted data; compensating recovery is not crash-safe or a multi-instance transaction; cache release is not verified secure erasure.

Validation

Final-commit Ubuntu and Windows CI passed: each platform ran 119 source tests, 119 compiled tests and one expanded package/install/CLI/API test, with zero failures or skips, plus type, recall-quality, cache, projection, documentation and synthetic-project checks. All 138 packed files were reviewed; candidate tarball SHA-512 matched across platforms. Registry-artifact verification and clean npm 0.8.0 installation also passed on Ubuntu and Windows: the downloaded archive matched the complete 138-file, 822,678-byte manifest and expected SHA-1/SHA-512 hashes, and fresh version-pinned registry installs passed CLI/API smoke checks. See the verification report and scope. These installed-artifact checks do not establish npm provenance attestation or a new product-wide performance result.

Introduction, opt-in examples and migration guidance · Changelog

The tagged preparation documents and published archive retain their pre-publication checkpoint. This release page and current repository documentation record completed GitHub and npm publication. The original tag and tarball are unchanged; later documentation commits are not npm gitHead.

Assets 2
Loading