claude-mem-lite 6.29.2 → 6.30.0

package/commands/adopt.md

@@ -6,10 +6,10 @@ description: "Use when: user asks to put the claude-mem-lite steering block into
 # /adopt
 
 Install the claude-mem-lite **steering block** into the current project's
-`CLAUDE.md` (the canonical home for project instructions — loaded by Claude Code
-at system-prompt authority). It does not go in the project's memory-dir
-`MEMORY.md`: that index belongs to the user's own memories, and it carries no
-more weight than `CLAUDE.md`.
+`CLAUDE.md` (the canonical home for project instructions — Claude Code loads it
+into every session, in a message after the system prompt). It does not go
+in the project's memory-dir `MEMORY.md`: that index belongs to the user's own
+memories.
 
 Auto-adopt does not add the block to `CLAUDE.md`: in a git repository it keeps the same block
 in `CLAUDE.local.md` at the repository root, excluded from git through `.git/info/exclude`.
@@ -59,10 +59,10 @@ doc). Other plugins' blocks (e.g. `code-graph-mcp:*`) and your own prose survive
 - `/unadopt` removes the CLAUDE.md block + `.claude/` detail doc (your prose stays),
   and the local block. The next session writes a local file if the plugin never
   created one in this repository; one it created before is not written back (the
-  text is injected instead) until `claude-mem-lite adopt --enable`. Beside an
+  text is injected instead) until `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" adopt --enable`. Beside an
   `AGENTS.md` that `CLAUDE.local.md` would switch off, no file is written unless
   `CLAUDE_MEM_RULES_STEERING=1`.
-- `claude-mem-lite adopt --disable` permanently stops auto-adopt for this project
+- `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" adopt --disable` permanently stops auto-adopt for this project
   (also for sessions started in its subdirectories) and removes the local block; a
   `CLAUDE.md` block stays until `/unadopt`.
 - `MEM_NO_AUTO_ADOPT=1` disables auto-adopt globally; blocks already written stay.
@@ -74,7 +74,7 @@ doc). Other plugins' blocks (e.g. `code-graph-mcp:*`) and your own prose survive
 Adoption does NOT remove the hook-based injection (SessionStart context,
 UserPromptSubmit related-memory). Those remain as fallback. Post-adopt the MCP
 `WHEN TO USE` section + the `File Lessons` / `Key Context` sections auto-trim,
-since the CLAUDE.md block already carries the triggers at higher authority.
+since the CLAUDE.md block already carries the triggers.
 
 ## Restart caveat for the MCP-instructions trim
 

package/commands/bug.md

@@ -3,7 +3,7 @@ name: bug
 description: "Use when: logging a known bug + repro steps you can't fix right now. Writes a searchable observation (findable via mem_search + surfaced by recall hooks; still NOT memdir). Skip for bugs you're actively fixing in the current turn — just fix them."
 ---
 
-# /bug
+# /claude-mem-lite:bug
 
 Record a known bug + reproduction steps. Writes a searchable **observation**
 (`type=bugfix`, description in `lesson_learned`) so future sessions can find it
@@ -59,5 +59,5 @@ Confirm to user with: `Bug logged: #<id>`.
 
 ## Examples
 
-- `/bug intermittent test flake when DB is under load --repro "run pnpm test -- --retry=0; fails ~1 in 20 runs when CPU is busy"`.
-- `/bug --file src/auth.mjs --severity high "session refresh drops the X-Forwarded-For header"` — no repro steps, just a high-severity note.
+- `/claude-mem-lite:bug intermittent test flake when DB is under load --repro "run pnpm test -- --retry=0; fails ~1 in 20 runs when CPU is busy"`.
+- `/claude-mem-lite:bug --file src/auth.mjs --severity high "session refresh drops the X-Forwarded-For header"` — no repro steps, just a high-severity note.

package/commands/lesson.md

@@ -8,9 +8,9 @@ description: "Use when: capturing a non-obvious lesson/gotcha/workaround after a
 Record a lesson / gotcha / workaround. Writes a searchable **observation**
 (`type=discovery` with the text as `lesson_learned`) so future sessions can
 find it via `mem_search` and the PreToolUse recall hooks surface it on the
-relevant files. Does NOT touch memdir — so lessons never end up in the L1
-system-prompt memory section and do not conflict with Claude Code's auto-memory
-rules on what not to save there.
+relevant files. Does NOT touch memdir — so lessons never end up in the
+auto-memory index Claude Code loads into every session, and do not conflict with
+Claude Code's auto-memory rules on what not to save there.
 
 ## When to use
 

package/commands/mem.md

@@ -30,8 +30,8 @@ When the user invokes `/mem`, parse their intent:
 - `/mem save <text>` → call `mem_save` MCP tool with the text as content
 - `/mem stats` → run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" stats` via Bash
 - `/mem get <ids>` → run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" get <ids>` via Bash
-- `/mem cleanup` → run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain scan` via Bash, report pending purge count and stale items to user, ask for confirmation, then run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops purge_stale --confirm` via Bash if confirmed. **`--confirm` is required and is not optional politeness:** without it the command prints a dry-run PREVIEW and deletes nothing, while still succeeding — so you would report a cleanup that never happened.
-- `/mem cleanup Nd` (e.g. `60d`) → same as above but add `--retain-days N` to only purge items older than N days. **`--retain-days` must be between 7 and 365**; the CLI rejects anything outside that range, so `/mem cleanup 3d` cannot be honoured — say so rather than silently substituting the default.
+- `/mem cleanup` → run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain scan` via Bash and report the pending purge and stale counts to the user. Then run the purge command below without `--confirm` first: it prints how many rows it would delete and deletes nothing. If that count is 0, tell the user nothing is old enough to purge yet and stop. Otherwise report that count, not the scan's pending count, which includes rows too recent to purge. Ask for confirmation, and if confirmed run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops purge_stale --confirm` via Bash. **`--confirm` is required and is not optional politeness:** without it the command prints a dry-run PREVIEW and deletes nothing, while still succeeding — so you would report a cleanup that never happened.
+- `/mem cleanup Nd` (e.g. `60d`) → same as above but add `--retain-days N` to both purge runs to only purge items older than N days. **`--retain-days` must be between 7 and 365**; the CLI rejects anything outside that range, so `/mem cleanup 3d` cannot be honoured — say so rather than silently substituting the default.
 - `/mem cleanup keep Nd` (e.g. `keep 14d`) → same as above with `--retain-days N`, same 7–365 range.
 - `/mem <query>` (no subcommand) → treat as search, run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" search <query>` via Bash
 

package/commands/unadopt.md

@@ -43,10 +43,10 @@ project (slug-scoped — other plugins' blocks survive).
 
 `/unadopt` removes files, not the steering. A local block the plugin created is not
 written back; the text is added to each session's context instead
-(`claude-mem-lite adopt --enable` lets it write the file again). A project whose
+(`node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" adopt --enable` lets it write the file again). A project whose
 `CLAUDE.md` block you removed gets a local file on the next session, unless the
 plugin created one there before. Beside an `AGENTS.md` that `CLAUDE.local.md` would
-switch off, no file is written unless `CLAUDE_MEM_RULES_STEERING=1`. To stop the steering: `claude-mem-lite adopt --disable`
+switch off, no file is written unless `CLAUDE_MEM_RULES_STEERING=1`. To stop the steering: `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" adopt --disable`
 (per project) or `MEM_NO_AUTO_ADOPT=1` (global).
 
 ## Aftermath

package/commands/update.md

@@ -22,9 +22,9 @@ Run each command below via Bash; the CLI reaches the maintenance operations whet
 
 1. Run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain scan` to analyze maintenance candidates
 2. Report scan results to the user (duplicates, stale items, broken items, boostable items, **pending purge** items)
-3. **If pending purge items > 0**: first run the purge command below without `--confirm`: it prints how many rows it would delete and deletes nothing. Report that count to the user and ask for confirmation. If confirmed, run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops purge_stale --confirm`. **`--confirm` is required:** without it the command prints a dry-run preview and deletes nothing while still succeeding, so you would report a purge that never happened. User may optionally add `--retain-days N` (default 30, allowed range 7–365) to both runs to control how many days of data to keep; the CLI rejects a value outside that range, so tell the user instead of substituting the default. Do NOT purge without explicit user confirmation. The purge comes before the next step on purpose: decay there queues more rows for purge, and those wait for a later run, so what gets deleted is what the user approved.
+3. **If pending purge items > 0**: first run the purge command below without `--confirm`: it prints how many rows it would delete and deletes nothing. If that count is 0, tell the user nothing is old enough to purge yet and go on to the next step. Otherwise report that count to the user and ask for confirmation. If confirmed, run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops purge_stale --confirm`. **`--confirm` is required:** without it the command prints a dry-run preview and deletes nothing while still succeeding, so you would report a purge that never happened. User may optionally add `--retain-days N` (default 30, allowed range 7–365) to both runs to control how many days of data to keep; the CLI rejects a value outside that range, so tell the user instead of substituting the default. Do NOT purge without explicit user confirmation. The purge comes before the next step on purpose: decay there queues more rows for purge, and those wait for a later run instead of joining the purge the user approved.
 4. Run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute` to apply safe automatic changes — with no `--ops` it runs the default set: cleanup, decay, boost, then demote_pinned (left out when `CLAUDE_MEM_SKIP_DEMOTE_PINNED=1`)
-5. If duplicates were found in scan, review them and run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops dedup --merge-ids keepId:removeId,...` — keep the more important/recent observation in each pair. Groups are comma-separated and the first id in each is kept (`10:11,20:21:22`). For pairs similar enough to merge without review the scan prints a ready-made list after `--merge-ids`; pass it to the command above, since the command the scan prints uses a bare `claude-mem-lite`, which may not be installed
+5. If duplicates were found in scan, review them and run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" maintain execute --ops dedup --merge-ids keepId:removeId,...` — keep the more important/recent observation in each pair. Groups are comma-separated and the first id in each is kept (`10:11,20:21:22`). For pairs similar enough to merge without review the scan prints a ready-to-run command after `Ready-to-use:`; run it as printed. Judge each pair under `Needs review:` from the two lines the scan prints below it; do not read them with `get`: that counts as an access and can raise a row's importance
 6. Run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" compress --execute` for old low-value observations (without `--execute` it only previews)
 
 ### Phase 2: Summary

package/commands/verify.md

@@ -1,9 +1,9 @@
 ---
 name: verify
-description: "Use when: the user explicitly asks to verify, audit or correct their stored memories against the current code (e.g. \"check my memories for stale ones\", /verify). You check each memory with read-only repo tools and propose corrections; nothing is written until the user approves the exact plan. Not for routine recall or saving."
+description: "Use when: the user explicitly asks to verify, audit or correct their stored memories against the current code (e.g. \"check my memories for stale ones\", /claude-mem-lite:verify). You check each memory with read-only repo tools and propose corrections; nothing is written until the user approves the exact plan. Not for routine recall or saving."
 ---
 
-# /verify — check memories against the code, then correct the stale ones
+# /claude-mem-lite:verify — check memories against the code, then correct the stale ones
 
 Memories go stale: a bug recorded as open gets fixed, a measurement gets retracted, a
 mechanism is replaced. Measured on 118 live memories across 7 repos, ~10% were STALE and
@@ -12,8 +12,6 @@ this — cheap single-shot models misjudged it (precision 0.36) and model-writte
 were false in 28 of 72 cases. What works is YOU reading the code: you propose, the user
 approves the exact plan, and `verify-apply` is the only thing that writes.
 
-(If another plugin also defines `/verify`, this one is `/claude-mem-lite:verify`.)
-
 ## Arguments
 
 - `--from <YYYY-MM-DD>`: only memories saved on or after this date (default: all live).

package/haiku-client.mjs

@@ -832,7 +832,11 @@ function claudeArgs(modelName) {
  * their output tokens and latency (measured above, 2026-09-29; the model the CLI ran then was
  * not recorded). Claude Code 2.1.301 does not change its request for Claude Haiku 5.5 on this
  * variable: the body carries adaptive thinking either way (D#334). Earlier versions were not
- * checked.
+ * checked. CLAUDE_CODE_DISABLE_AUTO_MEMORY=1 drops Claude Code's auto-memory section, about 2.2 KB
+ * of every system prompt that tells the model about a memory directory these calls never use
+ * (stub-probed on 2.1.304: system 8,964 -> 6,688 B). The 2026-10-20 A/B on the cli leg, gate set
+ * before the run (D#483): usable 8/8, 8/8, 7/8 against the same without it; kept lessons 3 vs 4
+ * at n=8, inside floor(0.9 x 4).
  */
 function cliSpawnEnv() {
   return {
@@ -840,6 +844,7 @@ function cliSpawnEnv() {
     CLAUDE_MEM_HOOK_RUNNING: '1',
     DISABLE_CLAUDEMD_HOOKS: '1',
     MAX_THINKING_TOKENS: '0',
+    CLAUDE_CODE_DISABLE_AUTO_MEMORY: '1',
   };
 }
 

package/hook-context.mjs

@@ -690,8 +690,8 @@ export function buildSessionContextLines(
 
     // Phase A (QUIET_HOOKS) + Phase D (adopted sentinel): drop descriptive
     // File Lessons / Key Context sections when the user has opted into low-noise
-    // hooks OR adopted invited-memory (MEMORY.md sentinel carries the triggers
-    // at higher system-prompt authority). The Recent table still fires so #IDs
+    // hooks OR adopted invited-memory (the steering block carries the triggers
+    // in the project's instructions). The Recent table still fires so #IDs
     // remain reachable via mem_get. The collector sees only rows that survive
     // BOTH the quiet gate and the per-section slice — rendered rows, nothing else.
     const quiet = effectiveQuiet();

package/hook-llm.mjs

@@ -93,15 +93,19 @@ export function retractPreSavedObs(db, obsId, where) {
   // Both statements run in one transaction so a crash between them cannot leave that state
   // either; nesting under persistHaikuSummary's transaction is safe (better-sqlite3 uses
   // savepoints).
-  return db.transaction(() => {
-    const live = db.prepare(`SELECT 1 FROM observations WHERE id = ? AND ${liveObsFilterSql('')}`).get(obsId);
-    if (!live) {
-      debugLog('DEBUG', 'llm-episode', `${where}: pre-saved obs #${obsId} no longer live — left in place`);
-      return false;
-    }
-    recoverChildrenOf(db, [obsId]);
-    return db.prepare('DELETE FROM observations WHERE id = ?').run(obsId).changes > 0;
-  })();
+  return db
+    .transaction(() => {
+      const live = db
+        .prepare(`SELECT 1 FROM observations WHERE id = ? AND ${liveObsFilterSql('')}`)
+        .get(obsId);
+      if (!live) {
+        debugLog('DEBUG', 'llm-episode', `${where}: pre-saved obs #${obsId} no longer live — left in place`);
+        return false;
+      }
+      recoverChildrenOf(db, [obsId]);
+      return db.prepare('DELETE FROM observations WHERE id = ?').run(obsId).changes > 0;
+    })
+    .immediate();
 }
 // T9: memdir-incompatible types live in the `events` table, not `observations`.
 // Set lookup is O(1) — authoritative source is lib/activity.mjs::EVENT_TYPES.
@@ -544,13 +548,15 @@ export function persistHaikuSummary(db, summary, ctx) {
       });
 
     if (ctx.preSavedObsId) {
-      const id = db.transaction(() => {
-        // Same live-row guard as the in-place upgrade (FLOW-7); the event gets written
-        // either way. Shared helper since audit 2026-09-02 P0-6 — this was the only one
-        // of the three retraction sites that carried the guard.
-        retractPreSavedObs(db, ctx.preSavedObsId, 'upgrade-delete');
-        return insertEvent();
-      })();
+      const id = db
+        .transaction(() => {
+          // Same live-row guard as the in-place upgrade (FLOW-7); the event gets written
+          // either way. Shared helper since audit 2026-09-02 P0-6 — this was the only one
+          // of the three retraction sites that carried the guard.
+          retractPreSavedObs(db, ctx.preSavedObsId, 'upgrade-delete');
+          return insertEvent();
+        })
+        .immediate();
       return { table: 'events', id };
     }