claude-mem-lite 2.32.1 → 2.32.3

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "2.32.1",
+      "version": "2.32.3",
       "source": "./",
       "description": "Lightweight persistent memory system for Claude Code — FTS5 search, episode batching, error-triggered recall"
     }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "2.32.1",
+  "version": "2.32.3",
   "description": "Lightweight persistent memory system for Claude Code — FTS5 search, episode batching, error-triggered recall",
   "author": {
     "name": "sdsrss"

package/README.md

@@ -279,6 +279,15 @@ Slash commands `/adopt` and `/unadopt` wrap the same CLI.
   / `Key Context` sections. `#ID` references and the `Recent` table still fire
   so `mem_get` remains reachable.
 
+**When does it take effect?**
+- The MEMORY.md sentinel and the hook-layer trim (`File Lessons` / `Key Context` /
+  lesson suffix) apply on the **next SessionStart** (any new Claude Code session
+  in the adopted project).
+- The MCP server instructions are built once at server boot and MCP has no
+  "push" protocol — the `WHEN TO USE` / `Decision rules` trim only applies
+  after Claude Code restarts and re-spawns the mem MCP server. A single
+  `/exit` + fresh session is enough. Same caveat applies to `unadopt`.
+
 **Safety:**
 - Hash-guarded: editing the sentinel body yourself blocks automatic rewrites
   unless you pass `--force`.

package/README.zh-CN.md

@@ -264,6 +264,14 @@ Slash 命令 `/adopt` 和 `/unadopt` 是上述 CLI 的包装。
   SessionStart 注入去掉 `File Lessons` / `Key Context`。`#ID` 引用与 `Recent`
   表保留，`mem_get` 仍可随时展开。
 
+**什么时候生效？**
+- MEMORY.md sentinel 和 hook 层瘦身（`File Lessons` / `Key Context` / lesson
+  后缀）**下一次 SessionStart** 生效（adopt 的项目下任一新会话）。
+- MCP server instructions 是**服务启动时构建一次**，MCP 协议无 "push" 机制，
+  所以 `WHEN TO USE` / `Decision rules` 两段的瘦身**只在 Claude Code 重启后**
+  才生效（mem MCP 服务被重新 spawn）。`/exit` 一次再开新会话即可。`unadopt`
+  同理。
+
 **安全性：**
 - Hash 守护：你手动改了 sentinel 段 → 下一次 adopt 报 `UserEditedError`，
   除非显式 `--force`。

package/commands/adopt.md

@@ -41,4 +41,20 @@ Code versions. Post-adopt the MCP `WHEN TO USE` section + the `File Lessons` /
 `Key Context` sections auto-trim since the sentinel line already carries the
 triggers at higher authority.
 
+## Restart required for MCP trim to take effect
+
+The MCP server builds its instructions once at server boot and the protocol
+has no way to push updated instructions to an already-connected Claude Code
+session. After running `adopt`:
+
+- The **MEMORY.md sentinel** appears on the **next SessionStart** automatically.
+- Hook-layer trim (`File Lessons` / `Key Context` / lesson suffix) applies
+  on the next SessionStart.
+- MCP-instructions trim (`WHEN TO USE` / `Decision rules` sections) only
+  takes effect after Claude Code itself restarts (or at least re-attaches
+  the mem MCP server). If you still see the verbose MCP instructions after
+  adopt, a `/exit` + fresh session is enough.
+
+Same caveat applies in reverse for `/unadopt`.
+
 !claude-mem-lite adopt $ARGUMENTS

package/commands/bug.md

@@ -0,0 +1,57 @@
+---
+name: bug
+description: "Use when: logging a known bug + repro steps you can't fix right now. Writes to the mem events table (NOT memdir). Skip for bugs you're actively fixing in the current turn — just fix them."
+---
+
+# /bug
+
+Record a known bug + reproduction steps. Writes to the mem `events` table
+with `event_type='bug'`. 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.
+
+## When to use
+
+- Bug is known but fix is blocked (waiting on upstream, needs discussion).
+- Bug is intermittent / race condition; you want a repro recipe recorded.
+- Edge case affecting only part of users; not priority now but must not
+  be silently re-discovered.
+
+Don't use for bugs you're actively fixing in the current turn — just fix
+them. Use `/lesson` afterward if there's a non-obvious root cause worth
+recording.
+
+## Arguments
+
+- Positional text: short bug description.
+- `--file <path>` or `--files f1,f2,...`: affected files. Triggers
+  pre-tool-recall warning when these files are edited later.
+- `--repro "step1; step2; step3"`: reproduction steps, semicolon-separated.
+- `--severity low|med|high`: maps to importance `1|2|3`. Default `med`.
+
+## Execution
+
+Map severity to importance:
+
+- `low` → importance 1
+- `med` → importance 2 (default)
+- `high` → importance 3
+
+Build the body as `<description>\n\nRepro:\n<repro-steps>` (or just
+`<description>` if `--repro` is absent).
+
+Run via Bash:
+
+    claude-mem-lite activity save \
+      --type bug \
+      --title "<first 60 chars of description>" \
+      --body "<body>" \
+      [--file <path> | --files f1,f2,...] \
+      --importance <1|2|3>
+
+Confirm to user with: `Bug logged: activity #<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.

package/commands/lesson.md

@@ -0,0 +1,53 @@
+---
+name: lesson
+description: "Use when: capturing a non-obvious lesson/gotcha/workaround after a tricky fix or surprising behavior. Writes to the mem events table (NOT memdir). Skip for typos, renames, or user-preference rules."
+---
+
+# /lesson
+
+Record a lesson / gotcha / workaround. Writes to the mem `events` table
+with `event_type='lesson'`. 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.
+
+## When to use
+
+After you (or the user) solve a tricky bug or discover a non-obvious behavior:
+
+- "you need to call X before Y or the test hangs"
+- "don't use this import path — it shadows the real module"
+- "the API returns null when you pass empty string, even though docs say it throws"
+
+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).
+
+## Arguments
+
+- Positional text: the lesson description (what went wrong + root cause + fix).
+- `--file <path>`: scope to a specific file. The lesson will surface via
+  pre-tool-recall the next time the file is opened via Edit/Write.
+- `--files f1,f2,f3`: comma-separated list for multiple files.
+- `--importance <1|2|3>`: default `2`. Use `3` for critical lessons you always
+  want surfaced; `1` for minor gotchas.
+
+## Execution
+
+Run via Bash — the CLI takes the lesson text as positional args and stores
+the full text as the title (the `activity save` command uses title-as-body
+when `--body` is absent):
+
+    claude-mem-lite activity save \
+      --type lesson \
+      --title "<first 60 chars of text>" \
+      --body "<full text>" \
+      [--file <path> | --files f1,f2,...] \
+      --importance <1|2|3>
+
+Confirm to user with: `Lesson saved: activity #<id>`.
+
+## Examples
+
+- `/lesson fix a bug now` — stores a short lesson for the current project; no file scope.
+- `/lesson --file src/auth.mjs "session cookies must be httpOnly or the e2e tests bleed across browsers"` — file-scoped.
+- `/lesson --files src/a.mjs,src/b.mjs --importance 3 "both modules share a cache via WeakMap; clearing one invalidates the other"` — multi-file, high importance.