claude-mem-lite 5.3.0 → 5.3.1

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "5.3.0",
+      "version": "5.3.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.3.0",
+  "version": "5.3.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/lib/maintain-core.mjs

@@ -394,6 +394,21 @@ export function cleanupBroken(db, { projectFilter, baseParams, opCap = OP_CAP })
       -- lesson). Parity with the "lessons never auto-GC" guards in
       -- decayAndMarkIdle / selectCompressionCandidates / findSmartCompressCandidates.
       AND (lesson_learned IS NULL OR lesson_learned = '' OR lesson_learned = 'none')
+      -- D#4. The one HARD DELETE in this family, and until now the only site whose
+      -- exemption from liveObsFilterSql was a LIKELIHOOD argument rather than an
+      -- inertness proof: these rows have no title, narrative or lesson, so they are
+      -- absent from every injection surface, so an id that was never injected is not one
+      -- a #NN cites. Narrow, but reachable -- a hand-typed #NN, or a numeric
+      -- "save --supersedes" chain later blanked by a degenerate cluster-merge -- and what
+      -- the delete takes with it is the superseded_by that
+      -- citation-tracker.redirectSupersededIds (:1363) follows to credit a corrected
+      -- memory's #NN to its successor.
+      --
+      -- Deliberately NOT the full liveObsFilterSql. A retired row whose superseded_by is
+      -- null hands that redirect nothing: it falls through to out.add(id) (:1379-1381),
+      -- the same answer a missing row produces. Filtering on superseded_at instead would
+      -- strand every empty retired row here forever for no gain.
+      AND superseded_by IS NULL
       ${projectFilter} LIMIT ${opCap}
   `,
     )

package/npm-shrinkwrap.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "5.3.0",
+  "version": "5.3.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/hook-launcher.mjs

@@ -124,12 +124,23 @@ if (!entryArg) {
 
 const entryAbs = entryArg.startsWith('/') ? entryArg : join(INSTALL_DIR, entryArg);
 
-// Swap barrier. An auto-update / repair renames files into the install dir one at
-// a time — atomic per file, not per file SET — so a hook process that starts
-// mid-swap can resolve its entry from the old version and an import from the new
-// one. hook-update.mjs marks that window; skip the fire instead of importing a
-// mixed module graph. Hooks are best-effort and the swap lasts ~a second, so the
-// next fire runs against a settled install.
+// Swap barrier. An auto-update renames files into the install dir one at a time —
+// atomic per file, not per file SET — so a hook process that starts mid-swap can
+// resolve its entry from the old version and an import from the new one.
+// hook-update.mjs marks that window; skip the fire instead of importing a mixed
+// module graph. Hooks are best-effort and the swap lasts ~a second, so the next
+// fire runs against a settled install.
+//
+// This covers the AUTO-UPDATE path only, and the distinction is not pedantic:
+// `hook-update.mjs:719` is the sole writer of this marker in the whole tree (name set,
+// 2026-09-07), so the barrier is never armed for `install.mjs install` — which copies the
+// same file set in place with copyFileSync (`install.mjs:341-350`) and is what
+// `install.mjs repair` ends up executing (`:2388`, after verifying the release). A repair
+// spawned in the background at SessionStart therefore overwrites this tree while hooks
+// keep firing into it. That is R10 P2-12, still open: the mechanism is settled, the runtime
+// symptom is not reproduced, and R10 §8 asks for a repro in tests/sandbox/phaseB-npm.mjs
+// before install()'s main path is touched. An earlier draft of this comment said "auto-update
+// / repair", which reads as though the repair path were already covered — it is not.
 //
 // Stale-guarded on BOTH pid and ts: an updater killed mid-swap leaves the marker
 // behind, and a marker that outlives its writer must never mute hooks permanently.