claude-mem-lite 6.29.1 → 6.29.2

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "6.29.1",
+      "version": "6.29.2",
       "source": "./",
       "homepage": "https://github.com/sdsrss/claude-mem-lite",
       "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. FTS5 BM25 keyword 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": "6.29.1",
+  "version": "6.29.2",
   "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. FTS5 BM25 keyword 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/commands/adopt.md

@@ -7,9 +7,9 @@ description: "Use when: user asks to put the claude-mem-lite steering block into
 
 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). This replaces the pre-v3.13 scheme that seeded the
-project's memory-dir `MEMORY.md`; that polluted an index meant for the user's own
-memories, and `MEMORY.md` carries no more weight than `CLAUDE.md` anyway.
+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`.
 
 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`.

package/commands/bug.md

@@ -10,8 +10,7 @@ Record a known bug + reproduction steps. Writes a searchable **observation**
 via `mem_search` and the PreToolUse recall hooks warn when the affected files
 are edited. Does NOT touch memdir. Useful for bugs you can't fix immediately
 but want future sessions (or yourself after `/clear`) to know about and avoid
-re-investigating. (Redirected v3.39: was the `events` table, which `mem_search`
-never read.)
+re-investigating.
 
 ## When to use
 

package/commands/lesson.md

@@ -9,9 +9,8 @@ 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 the `WHAT_NOT_TO_SAVE`
-semantics sdscc enforces. (Redirected v3.39: was the `events` table, which
-`mem_search` never read.)
+system-prompt memory section and do not conflict with Claude Code's auto-memory
+rules on what not to save there.
 
 ## When to use
 
@@ -23,7 +22,7 @@ After you (or the user) solve a tricky bug or discover a non-obvious behavior:
 
 Don't use for trivial fixes (typos, renames), for rules that belong in memdir
 (user preferences, project-wide conventions), or for general project notes
-(use `/mem:memory` or `mem_save` instead).
+(use `/claude-mem-lite:memory` or `mem_save` instead).
 
 ## Arguments
 

package/commands/mem.md

@@ -30,9 +30,9 @@ 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 `mem_maintain(action="scan")`, report pending purge count and stale items to user, ask for confirmation, then run `mem_maintain(action="execute", operations=["purge_stale"], confirm=true)` if confirmed. **`confirm=true` is required and is not optional politeness:** without it the call returns 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**; anything outside that range is rejected by the schema, 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 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 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
 
 Use Bash commands first. For detailed data, use `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" get <id>` via Bash.

package/commands/memory.md

@@ -9,12 +9,12 @@ Save important content to your long-term memory database.
 
 ## Commands
 
-- `/mem:memory <content>` — Save the given content directly to memory
-- `/mem:memory` (no args) — Auto-summarize recent session highlights and save key findings
+- `/claude-mem-lite:memory <content>` — Save the given content directly to memory
+- `/claude-mem-lite:memory` (no args) — Auto-summarize recent session highlights and save key findings
 
 ## Instructions
 
-When the user invokes `/mem:memory`, determine the intent:
+When the user invokes `/claude-mem-lite:memory`, determine the intent:
 
 ### With explicit content
 

package/commands/update.md

@@ -1,6 +1,7 @@
 ---
 name: update
 description: "Use when: search results seem noisy or for periodic memory maintenance"
+disable-model-invocation: true
 ---
 
 # Memory Maintenance
@@ -9,23 +10,25 @@ Run intelligent maintenance on the memory database.
 
 ## Usage
 
-- `/mem:update` — Run full maintenance cycle
+- `/claude-mem-lite:update` — Run full maintenance cycle
 
 ## Instructions
 
-When the user invokes `/mem:update`, perform the following maintenance cycle:
+When the user invokes `/claude-mem-lite:update`, perform the following maintenance cycle:
 
 ### Phase 1: Memory Maintenance
 
-1. Call `mem_maintain(action="scan")` to analyze maintenance candidates
+Run each command below via Bash; the CLI reaches the maintenance operations whether or not their MCP tools are in your tool list.
+
+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. Call `mem_maintain(action="execute", operations=["cleanup","decay","boost"])` to apply safe automatic changes
-4. If duplicates were found in scan, review them and call `mem_maintain(action="execute", operations=["dedup"], merge_ids=[[keepId, removeId1, ...], ...])` — keep the more important/recent observation in each pair
-5. Run `mem_compress(preview=false)` for old low-value observations
-6. **If pending purge items > 0**: Report the count to the user and ask for confirmation. If confirmed, call `mem_maintain(action="execute", operations=["purge_stale"], confirm=true)`. **`confirm=true` is required:** without it the call returns a dry-run preview and deletes nothing while still succeeding, so you would report a purge that never happened. User may optionally specify `retain_days` (default 30, allowed range 7–365) to control how many days of data to keep. Do NOT purge without explicit user confirmation.
+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.
+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
+6. Run `node "${CLAUDE_PLUGIN_ROOT}/cli.mjs" compress --execute` for old low-value observations (without `--execute` it only previews)
 
 ### Phase 2: Summary
 
-Summarize all maintenance actions taken in zh-CN:
-- Memory: observations cleaned, decayed, boosted, deduplicated, compressed
+Summarize all maintenance actions taken in the user's language:
+- Memory: observations cleaned, decayed, boosted, demoted, deduplicated, compressed
 - Overall health assessment

package/npm-shrinkwrap.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "6.29.1",
+  "version": "6.29.2",
   "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. FTS5 BM25 keyword 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",