claude-mem-lite 4.0.1 → 4.0.3

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "4.0.1",
+      "version": "4.0.3",
       "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": "4.0.1",
+  "version": "4.0.3",
   "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/README.md

@@ -145,7 +145,7 @@ How claude-mem-lite differs from the major neighbors in the LLM-memory space (ve
 
 ## Requirements
 
-- **Node.js** >= 20
+- **Node.js** >= 22
 - **Claude Code** CLI installed and configured (`claude` command available)
 - **SQLite3** support (provided by `better-sqlite3`, compiled on install)
 - **Platform**: Linux or macOS (see [Platform Support](#platform-support))

package/hook-update.mjs

@@ -23,6 +23,7 @@ import { pathToFileURL } from 'node:url';
 import { tmpdir, homedir } from 'node:os';
 import { DB_DIR, CODE_DIR } from './schema.mjs';
 import { debugCatch, debugLog } from './utils.mjs';
+import { NATIVE_BINDING_SOURCE_BUILD_CMD } from './lib/binding-probe.mjs';
 // Local manifest is fallback only — the active manifest is loaded from the
 // extracted tarball's own source-files.mjs inside installExtractedRelease.
 // See loadReleaseManifest below.
@@ -877,7 +878,27 @@ function smokeInstalledRelease(targetDir) {
         } catch {
           execSync('npm rebuild better-sqlite3', { cwd: targetDir, timeout: 120000, stdio: 'ignore' });
         }
-        execSync(probeCmd, { timeout: 20000, stdio: 'ignore' });
+        try {
+          execSync(probeCmd, { timeout: 20000, stdio: 'ignore' });
+        } catch {
+          // Both npm rebuilds healed nothing — which is what better-sqlite3 13 does on a
+          // platform it ships no prebuild for, because there is no install script for them to
+          // run. Without this step the re-probe threw, smoke failed, and the caller rolled the
+          // whole update back, so auto-update could never land again on those platforms
+          // (A20260906-R8b-P2-1, found by independent review of v4.0.0).
+          //
+          // The source build is `node-gyp clean && node-gyp rebuild`, i.e. it deletes build/
+          // first — which is why the SessionStart probe path must NOT run it. Here it is safe
+          // for two independent reasons: the binding is ALREADY unusable (the probe above just
+          // threw), so clean destroys nothing; and this whole function is a smoke gate whose
+          // failure rolls back to the previous, working install.
+          execSync(NATIVE_BINDING_SOURCE_BUILD_CMD, {
+            cwd: targetDir,
+            timeout: 300000,
+            stdio: 'ignore',
+          });
+          execSync(probeCmd, { timeout: 20000, stdio: 'ignore' });
+        }
       }
     }
     return true;

package/install.mjs

@@ -420,6 +420,12 @@ export function patchClaudeMdVersion(text, version) {
  * removes the link and leaves the target intact (a link to a populated dir, target still
  * readable afterwards) — following it would delete the developer's own scripts/.
  *
+ * It is `recursive`, so it also removes a REAL directory at `p`, not only a link to one.
+ * That is deliberate and pre-existing (the dev-mode sites already did this): running
+ * `install --dev` after a normal install finds a real `DATA_DIR/node_modules` where a link
+ * belongs. Named here because the one-line summary above says "before a symlink is written
+ * over it", which undersells what the call can delete.
+ *
  * @param {string} p
  * @returns {boolean}
  */
@@ -1581,13 +1587,9 @@ async function uninstall() {
   // 1b. Remove CLI symlink
   for (const binDir of [join(homedir(), '.local', 'bin'), '/usr/local/bin']) {
     const cliLink = join(binDir, 'claude-mem-lite');
-    try {
-      if (clearLinkPath(cliLink)) {
-        ok(`CLI symlink removed: ${cliLink}`);
-      }
-    } catch {
-      /* may not have permissions */
-    }
+    // No try/catch: clearLinkPath swallows a permissions failure and returns false, so the
+    // wrapper this used to have was unreachable once the existsSync gate moved inside it.
+    if (clearLinkPath(cliLink)) ok(`CLI symlink removed: ${cliLink}`);
   }
 
   // 2. Remove hooks from settings.json (match both npx and git-clone install paths)

package/lib/binding-probe.mjs

@@ -48,12 +48,17 @@ export const NATIVE_BINDING_SOURCE_BUILD_CMD = 'npm run --prefix node_modules/be
  * `&&`, never `||`: step 1 exits 0 whether or not it did anything, so an `||` chain would
  * never reach step 2 — the no-op is the whole trap. Sequencing unconditionally costs a
  * recompile in the case step 1 already fixed, which is the right trade for a manual repair.
+ * Precisely: `build-release` is `node-gyp clean && node-gyp rebuild`, so step 2 DISCARDS a
+ * binding step 1 had just produced and rebuilds it. `prebuilds/` is untouched either way, so
+ * the end state is a usable binding; the cost is time, not correctness.
  *
  * @param {string} root Directory whose node_modules holds better-sqlite3
  * @returns {string}
  */
 export function nativeBindingRepairHint(root) {
-  return `cd ${root} && ${NATIVE_BINDING_REBUILD_CMD} && ${NATIVE_BINDING_SOURCE_BUILD_CMD}`;
+  // 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}`;
 }
 
 // Set on a re-exec'd child so one failed heal cannot fork-bomb the CLI.
@@ -270,9 +275,24 @@ export async function ensureBetterSqlite3Working(installDir, deps = {}) {
   // get it appended — otherwise an injected strategy would silently grow a step its owner
   // never asked for, and (as the stub tests caught) a test that stubs `rebuild` without
   // stubbing `exec` would shell out for real.
+  //
+  // `sourceBuild: false` is the EXPLICIT opt-out, and it exists because the `deps.rebuild`
+  // test above was the wrong proxy for "this caller has a budget" (A20260906-R8b-P0-1, found
+  // by independent review). The one caller that is genuinely time-boxed — the SessionStart
+  // hook probe — injects `exec` with a 20 s cap and does NOT inject `rebuild`, so it landed
+  // outside the guard. That matters because this step is `node-gyp clean && node-gyp rebuild`:
+  // it DELETES build/ before compiling, so a truncated attempt is not a no-op, it is
+  // destructive. Measured on a tree whose compiled binding opened a DB — 20 s cap, SIGTERM at
+  // 20.02 s, no `.node` left, `DB opens: YES` → `NO`, repeating on every SessionStart because
+  // setup.sh writes its marker only on success. Callers with a time budget must opt out and
+  // leave the compile to a foreground path (`rebuild-binding`, `healAndReexec`) that has none.
   const sourceBuild =
-    deps.sourceBuild ||
-    (deps.rebuild ? null : () => exec(NATIVE_BINDING_SOURCE_BUILD_CMD, { cwd: installDir, stdio: 'pipe' }));
+    deps.sourceBuild === false
+      ? null
+      : deps.sourceBuild ||
+        (deps.rebuild
+          ? null
+          : () => exec(NATIVE_BINDING_SOURCE_BUILD_CMD, { cwd: installDir, stdio: 'pipe' }));
   if (!sourceBuild) return { ok: false, error: second.error || first.error };
 
   try {

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "claude-mem-lite",
-  "version": "4.0.1",
+  "version": "4.0.3",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "claude-mem-lite",
-      "version": "4.0.1",
+      "version": "4.0.3",
       "dependencies": {
         "@modelcontextprotocol/sdk": "^1.30.0",
         "better-sqlite3": "^13.0.3",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "4.0.1",
+  "version": "4.0.3",
   "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/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/launch.mjs

@@ -107,7 +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: ${nativeBindingRepairHint(`"${ROOT}"`)}\n`);
+    process.stderr.write(`[claude-mem-lite] Repair: ${nativeBindingRepairHint(ROOT)}\n`);
     process.exit(1);
   }
   if (verify.action === 'rebuilt') {