nexusmem 0.9.1 → 0.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/CHANGELOG.md +37 -1
  2. package/README.md +550 -529
  3. package/dist/cli/index.js +379 -72
  4. package/dist/cli/index.js.map +1 -1
  5. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -11,6 +11,39 @@ built from, matched by publish timestamp: `v0.1.0` → `67a4776`, `v0.1.1` → `
11
11
 
12
12
  No unreleased changes yet.
13
13
 
14
+ ## [0.10.1] — 2026-08-30
15
+
16
+ ### Added
17
+
18
+ - `nodes.retrieved_count`/`nodes.last_retrieved_at` (schema V12): retrieval outcomes are now recorded
19
+ instead of silently discarded. Bumped once per completed `nexusmem query`/MCP `search_memory` call,
20
+ for every node actually packed into the returned context (both CLI and MCP share one pipeline, so
21
+ both are covered from a single call site). Not yet folded into `rank.ts`'s score formula — every
22
+ existing ranking factor was tuned against real dogfooded queries and validated with `npm run eval`
23
+ before being trusted, and a new factor needs the same treatment. This release is the instrumentation
24
+ half only; confirmed eval-neutral (MRR 0.943 / Recall@5 0.964, unchanged).
25
+
26
+ ### Fixed
27
+
28
+ - `nexusmem precheck`'s "What already failed here" warning implied the failure was located in the
29
+ flagged file, but the match is against basename word-tokens (`tokensForFile`) — a failing `npm run
30
+ precheck` flagged every file whose name contained that word, not just the one actually responsible.
31
+ Reworded to state what's actually true ("commands naming this file failed").
32
+ - The high-churn warning in `nexusmem precheck` was rendered as a `WARN`, the same severity as the
33
+ dogfooded failure-correlation warning, despite `HIGH_CHURN_THRESHOLD` being an admitted, untuned
34
+ guess. Demoted to a lower-severity `note`, explicitly labeled as an untuned heuristic, so it no
35
+ longer reads as equally trustworthy.
36
+
37
+ ## [0.10.0] — 2026-08-29
38
+
39
+ ### Added
40
+
41
+ - New opt-in `github` source: `sources.github.enabled`, `nexusmem scan-github`, `sync --github`.
42
+ Reads issue/PR threads (title, body, comments) from this repo's github.com remote via the `gh`
43
+ CLI, one `github_thread` node per thread. First source with a real external dependency (needs `gh`
44
+ installed and authenticated) rather than reading only what's already on disk; a missing remote or
45
+ an unreachable `gh` is a silent no-op, matching how an unreachable Ollama degrades elsewhere.
46
+
14
47
  ## [0.9.1] — 2026-08-29
15
48
 
16
49
  Three ranking/retrieval correctness fixes, found and validated against a new 28-case retrieval-quality
@@ -565,7 +598,10 @@ First public release.
565
598
  there is no local-model summarization pass, and the conversation collector has never been audited
566
599
  for the stale-node bug that was found and fixed in the docs collector.
567
600
 
568
- [Unreleased]: https://github.com/yaminbkk/NexusMem/compare/v0.9.0...HEAD
601
+ [Unreleased]: https://github.com/yaminbkk/NexusMem/compare/v0.10.1...HEAD
602
+ [0.10.1]: https://github.com/yaminbkk/NexusMem/compare/v0.10.0...v0.10.1
603
+ [0.10.0]: https://github.com/yaminbkk/NexusMem/compare/v0.9.1...v0.10.0
604
+ [0.9.1]: https://github.com/yaminbkk/NexusMem/compare/v0.9.0...v0.9.1
569
605
  [0.9.0]: https://github.com/yaminbkk/NexusMem/compare/v0.8.0...v0.9.0
570
606
  [0.8.0]: https://github.com/yaminbkk/NexusMem/compare/v0.7.0...v0.8.0
571
607
  [0.7.0]: https://github.com/yaminbkk/NexusMem/compare/v0.6.0...v0.7.0