claude-mem-lite 5.1.0 → 5.1.1

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "5.1.0",
+      "version": "5.1.1",
       "source": "./",
       "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)."
     }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "5.1.0",
+  "version": "5.1.1",
   "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).",
   "author": {
     "name": "sdsrss"

package/install.mjs

@@ -2545,6 +2545,12 @@ async function rebuildBinding() {
       const verify = await ensureBetterSqlite3Working(root);
       if (verify.ok) {
         ok(`better-sqlite3 binding ${verify.action} for Node ${process.version} — ${label} (${root})`);
+        if (verify.quarantined) {
+          // Say it out loud: the heal renamed a file inside the user's node_modules because
+          // the shipped prebuild was present and would not load. A silent move inside a
+          // dependency is the kind of thing that reads as corruption six months later.
+          log(`  the shipped prebuild would not load — moved aside to ${verify.quarantined}.unusable`);
+        }
       } else {
         fail(`better-sqlite3 binding still unusable in ${label}: ${verify.error}`);
         log(`Try manually: ${nativeBindingRepairHint(root)}`);

package/lib/binding-probe.mjs

@@ -7,6 +7,7 @@
 // sufficient — the binding can be present-but-stale after a Node upgrade.
 
 import { execSync, spawnSync } from 'node:child_process';
+import { existsSync, renameSync } from 'node:fs';
 import { createRequire } from 'node:module';
 import { join } from 'node:path';
 
@@ -58,7 +59,16 @@ export const NATIVE_BINDING_SOURCE_BUILD_CMD = 'npm run --prefix node_modules/be
 export function nativeBindingRepairHint(root) {
   // Quoted: INSTALL_DIR / a plugin-cache root can contain spaces, and an unquoted `cd`
   // hands the user a command that fails on exactly the machines least able to debug it.
-  return `cd "${root}" && ${NATIVE_BINDING_REBUILD_CMD} && ${NATIVE_BINDING_SOURCE_BUILD_CMD}`;
+  const npmPair = `cd "${root}" && ${NATIVE_BINDING_REBUILD_CMD} && ${NATIVE_BINDING_SOURCE_BUILD_CMD}`;
+  // The pair above heals a platform better-sqlite3 ships NO prebuild for. It cannot heal a
+  // prebuild that is present and will not load — 13 selects `prebuilds/<target>.node` on
+  // existence alone and prefers it over `build/`, so the addon those two commands compile
+  // stays shadowed. Only ensureBetterSqlite3Working moves the dead prebuild out of the way
+  // first, and `rebuild-binding` is how a human reaches it — so it goes FIRST, because a user
+  // runs the first command they are given and stops looking when it reports success.
+  const cli = join(root, 'cli.mjs');
+  if (!existsSync(cli)) return npmPair;
+  return `node "${cli}" rebuild-binding   (or, without the CLI: ${npmPair})`;
 }
 
 // Set on a re-exec'd child so one failed heal cannot fork-bomb the CLI.
@@ -193,6 +203,45 @@ export function probeBindingInFreshProcess(installDir, { timeoutMs = 30_000 } =
   };
 }
 
+// Suffix for a prebuilt addon that is present and will not load. Renamed, never deleted:
+// the file is evidence for whoever debugs the machine, and `npm install` puts a fresh
+// prebuild back at the original name regardless.
+const UNUSABLE_PREBUILD_SUFFIX = '.unusable';
+
+/**
+ * The prebuilt addon better-sqlite3 would choose under `installDir`, or null.
+ *
+ * ASKED OF THE DEPENDENCY, never computed here. Which file gets loaded depends on
+ * platform, arch and a musl probe, and this repo has already paid twice for guessing it:
+ * `tests/install-bsqlite-probe.test.mjs` matched a v12 filename that v13 does not produce
+ * (its main assertion went vacuously true), and both sandbox phases corrupted
+ * `build/Release/better_sqlite3.node` for a year of releases while the resolver loaded a
+ * prebuild. `lib/binding.js` exports the selector itself, so use it.
+ *
+ * Out of process, like every other probe here: this runs on a path that is about to dlopen
+ * the result, and `getPrebuildPath()` is existence-only today but is not ours to promise.
+ * `lib/binding.js` is absent from the package's `exports` map, hence the file path.
+ *
+ * @param {string} installDir Directory whose node_modules holds better-sqlite3
+ * @returns {string|null}
+ */
+function resolvedPrebuildPath(installDir) {
+  const bindingJs = join(installDir, 'node_modules', 'better-sqlite3', 'lib', 'binding.js');
+  if (!existsSync(bindingJs)) return null;
+  const r = spawnSync(
+    process.execPath,
+    [
+      '-e',
+      `const b=require(${JSON.stringify(bindingJs)});` +
+        `process.stdout.write((b.getPrebuildPath&&b.getPrebuildPath())||'')`,
+    ],
+    { stdio: 'pipe', encoding: 'utf8', timeout: 10_000 },
+  );
+  if (r.error || r.status !== 0) return null;
+  const p = String(r.stdout || '').trim();
+  return p && existsSync(p) ? p : null;
+}
+
 /**
  * Verify better-sqlite3 binding works in `installDir`; if not, run
  * `npm rebuild better-sqlite3` and re-probe. Returns
@@ -295,15 +344,52 @@ export async function ensureBetterSqlite3Working(installDir, deps = {}) {
           : () => exec(NATIVE_BINDING_SOURCE_BUILD_CMD, { cwd: installDir, stdio: 'pipe' }));
   if (!sourceBuild) return { ok: false, error: second.error || first.error };
 
+  // A prebuild that is present and unloadable SHADOWS everything the source build is about
+  // to produce: better-sqlite3 13 picks `prebuilds/<target>.node` on existence alone and
+  // prefers it over `build/`. Measured 2026-09-06 with a control — corrupt prebuild +
+  // healthy build/Release → `wrong ELF class`; the same tree with the prebuild moved aside →
+  // opens; with neither → fails. Until this, `rebuild-binding` (the foreground repair doctor
+  // prints, deliberately given no time budget) exited 1 on that shape and the manual command
+  // it offered instead could not fix it either. Reproduced end-to-end in
+  // tests/sandbox/phaseB-npm.mjs before the fix.
+  //
+  // Deliberately inside this branch and after the npm step: quarantining without a compile to
+  // follow it turns "broken addon" into "no addon", which is strictly worse — so the
+  // time-budgeted SessionStart path (sourceBuild: false) never reaches this.
+  const shadowingPrebuild = resolvedPrebuildPath(installDir);
+  let quarantined = null;
+  if (shadowingPrebuild) {
+    try {
+      renameSync(shadowingPrebuild, shadowingPrebuild + UNUSABLE_PREBUILD_SUFFIX);
+      quarantined = shadowingPrebuild;
+    } catch {
+      // A read-only or otherwise unwritable tree. The compile below is still worth trying:
+      // on a platform with no prebuild it is the whole fix, and failing here would turn a
+      // recoverable case into a hard stop.
+    }
+  }
+  /** Put the tree back exactly as found — an install we could not repair must not lose a file. */
+  const restorePrebuild = () => {
+    if (!quarantined) return;
+    try {
+      renameSync(quarantined + UNUSABLE_PREBUILD_SUFFIX, quarantined);
+    } catch {
+      // Nothing better to do; the error the caller gets already says the heal failed.
+    }
+  };
+
   try {
     await sourceBuild();
   } catch (e) {
+    restorePrebuild();
     return { ok: false, error: `source build failed: ${e.message}` };
   }
 
   const third = await verify();
-  if (third.ok) return { ok: true, action: 'compiled' };
+  if (third.ok)
+    return quarantined ? { ok: true, action: 'compiled', quarantined } : { ok: true, action: 'compiled' };
 
+  restorePrebuild();
   return { ok: false, error: third.error || second.error || first.error };
 }
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "claude-mem-lite",
-  "version": "5.1.0",
+  "version": "5.1.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "claude-mem-lite",
-      "version": "5.1.0",
+      "version": "5.1.1",
       "os": [
         "darwin",
         "linux"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "5.1.0",
+  "version": "5.1.1",
   "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",

package/scripts/setup.sh

@@ -190,7 +190,20 @@ if [[ -d "$ROOT/node_modules/better-sqlite3" ]]; then
     # 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"
+    #
+    # …and the pair alone is still not enough. It heals a platform 13 ships no prebuild
+    # for; it cannot heal a prebuild that is PRESENT and will not load, because 13 prefers
+    # `prebuilds/<target>.node` over anything the source build produces. This string is what
+    # the SessionStart dashboard prints as `Repair:`, so it leads with the CLI, which is the
+    # only path that moves the dead prebuild aside first (lib/binding-probe.mjs). Mirrors
+    # nativeBindingRepairHint(); this file may not import lib/, hence the duplication —
+    # tests/audit-r8-binding-repair-hint.test.mjs pins the set of files allowed to do that.
+    # mark_deps_broken already prefixes `cd <root> && `, so these are root-relative.
+    NB_REPAIR="npm rebuild better-sqlite3 --dangerously-allow-all-scripts && npm run --prefix node_modules/better-sqlite3 build-release"
+    if [[ -f "$ROOT/cli.mjs" ]]; then
+      NB_REPAIR="node cli.mjs rebuild-binding   (or, without the CLI: $NB_REPAIR)"
+    fi
+    mark_deps_broken "better-sqlite3 binding probe/rebuild failed (npm >= 12 blocks compile scripts by default)" "$NB_REPAIR"
   fi
 fi