claude-mem-lite 4.0.0 → 4.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "4.0.0",
+  "version": "4.0.2",
   "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF search with episode batching. Single SQLite DB, no external services. A lighter, lower-cost alternative to claude-mem (episode batching + a smaller model; cost savings are an internal estimate, not a measured benchmark).",
   "type": "module",
   "packageManager": "npm@10.9.2",
@@ -217,13 +217,13 @@
   },
   "devDependencies": {
     "@eslint/js": "^10.0.1",
-    "@vitest/coverage-v8": "^4.1.11",
+    "@vitest/coverage-v8": "^5.0.0",
     "acorn": "8.18.0",
     "eslint": "^10.9.1",
     "fast-check": "^4.9.0",
     "knip": "^6.34.0",
     "picomatch": "^4.0.4",
     "prettier": "3.9.6",
-    "vitest": "^4.0.18"
+    "vitest": "^5.0.0"
   }
 }

package/scripts/binding-probe-cli.mjs

@@ -132,6 +132,14 @@ try {
     probe: () => first,
     exec: (cmd, opts) => execSync(cmd, { ...opts, timeout: 20000 }),
     verify: () => helpers.probeBindingInFreshProcess(ROOT, { timeoutMs: 8000 }),
+    // NOT on this path (A20260906-R8b-P0-1). The source build is
+    // `node-gyp clean && node-gyp rebuild`: it deletes build/ before compiling, and a full
+    // compile takes ~41 s against the 20 s cap above — so under this budget it does not fail
+    // harmlessly, it destroys a binding that was working (measured: DB opens YES → NO, .node
+    // gone, SIGTERM at 20.02 s), and repeats every SessionStart because setup.sh writes its
+    // marker only on success. The compile belongs on a foreground path with no cap:
+    // `claude-mem-lite rebuild-binding`, which is what the repair hints now print.
+    sourceBuild: false,
   });
 } finally {
   // process.exit skips finally blocks — every exit below this point, so the

package/scripts/hook-launcher.mjs

@@ -93,9 +93,15 @@ const NB_BROKEN_MARKER = join(HOOK_RUNTIME_DIR, 'native-binding-broken');
 const NB_HEAL_MARKER = join(HOOK_RUNTIME_DIR, 'native-binding-lastheal');
 // Literal, not imported: the pure-`node:` charter above forbids importing lib/
 // here (this file must survive a broken install). Kept in sync with
-// lib/binding-probe.mjs::NATIVE_BINDING_REBUILD_CMD, which is the single home
-// everywhere the charter allows an import.
-const NB_MANUAL_CMD = 'npm rebuild better-sqlite3 --dangerously-allow-all-scripts';
+// lib/binding-probe.mjs::nativeBindingRepairHint, which is the single home
+// everywhere the charter allows an import — and pinned to it by
+// tests/audit-r8-binding-repair-hint.test.mjs, because a literal kept in sync by
+// a comment is a literal that drifts (A20260906-R8-P1-1).
+//
+// BOTH commands, `&&` not `||`: `npm rebuild` exits 0 without compiling on
+// better-sqlite3 13, so it can neither heal nor signal failure on its own.
+const NB_MANUAL_CMD =
+  'npm rebuild better-sqlite3 --dangerously-allow-all-scripts && npm run --prefix node_modules/better-sqlite3 build-release';
 
 // Resolvable invocation of the bundled CLI's repair path. Absolute via
 // INSTALL_DIR (import.meta.url) so it works on a plugin-only install, where

package/scripts/launch.mjs

@@ -69,7 +69,8 @@ if (!existsSync(join(ROOT, 'node_modules', 'better-sqlite3'))) {
 // intact but the .node binary stale → server FATALs with "Could not locate
 // the bindings file" on first DB open. Probe + auto-rebuild before launching.
 try {
-  const { ensureBetterSqlite3Working, probeBindingInFreshProcess } = await import('../lib/binding-probe.mjs');
+  const { ensureBetterSqlite3Working, probeBindingInFreshProcess, nativeBindingRepairHint } =
+    await import('../lib/binding-probe.mjs');
   // The rebuild inside ensureBetterSqlite3Working mutates node_modules — the
   // same write class as install/repair/update, and this was the ONE rebuild
   // path outside the shared install.lock: a second MCP launch or a concurrent
@@ -106,9 +107,7 @@ try {
   }
   if (!verify.ok) {
     process.stderr.write(`[claude-mem-lite] better-sqlite3 binding unusable: ${verify.error}\n`);
-    process.stderr.write(
-      `[claude-mem-lite] Repair: cd "${ROOT}" && npm rebuild better-sqlite3 --dangerously-allow-all-scripts\n`,
-    );
+    process.stderr.write(`[claude-mem-lite] Repair: ${nativeBindingRepairHint(ROOT)}\n`);
     process.exit(1);
   }
   if (verify.action === 'rebuilt') {

package/scripts/setup.sh

@@ -187,7 +187,10 @@ if [[ -d "$ROOT/node_modules/better-sqlite3" ]]; then
     mark_deps_ok
   else
     log_warn "better-sqlite3 native binding unusable — hooks degraded until repaired (flag: $DEPS_FLAG)"
-    mark_deps_broken "better-sqlite3 binding probe/rebuild failed (npm >= 12 blocks compile scripts by default)" "npm rebuild better-sqlite3 --dangerously-allow-all-scripts"
+    # Both commands, `&&` not `||`: `npm rebuild` exits 0 without compiling on
+    # better-sqlite3 13 (no install script to run), so it never signals failure and
+    # an `||` chain would never reach the source build. A20260906-R8-P1-1.
+    mark_deps_broken "better-sqlite3 binding probe/rebuild failed (npm >= 12 blocks compile scripts by default)" "npm rebuild better-sqlite3 --dangerously-allow-all-scripts && npm run --prefix node_modules/better-sqlite3 build-release"
   fi
 fi