claude-mem-lite 6.30.6 → 6.30.7

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "6.30.6",
+      "version": "6.30.7",
       "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.30.6",
+  "version": "6.30.7",
   "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/README.md

@@ -197,7 +197,7 @@ node install.mjs install
 2. **Register MCP server** -- `mem-lite` server with 19 tool definitions (10 core + 9 hidden-but-callable; `mem_search_feedback` is registered only when search telemetry is enabled). The pre-v2.78 generic server name `mem` is renamed to `mem-lite` for namespace hygiene; the tool names themselves (`mem_search`, `mem_recall`, ...) are unchanged.
 3. **Configure hooks** -- all seven lifecycle events: `SessionStart`, `PreCompact`, `PreToolUse`, `PostToolUse`, `PostToolUseFailure`, `Stop`, `UserPromptSubmit`
 4. **Create data directory** -- `~/.claude-mem-lite/` (hidden) for database, runtime, and managed resource files
-5. **Auto-migrate** -- `~/.claude-mem/claude-mem.db` (original claude-mem) is moved into `~/.claude-mem-lite/` as a `.legacy-backup-<time>` file and a fresh database is created. A database left in `~/claude-mem-lite/` (the unhidden directory of versions before the first release, 2.0.0) is moved into the data directory at the first open, when the data directory holds no database, log, snapshot or kept copy of a claude-mem-lite store yet; nothing else in either directory is moved or removed (the plugin install differs: see Migration)
+5. **Auto-migrate** -- `~/.claude-mem/claude-mem.db` (original claude-mem) is moved into `~/.claude-mem-lite/` as a `.legacy-backup-<time>` file and a fresh database is created. A database left in `~/claude-mem-lite/` (the unhidden directory of versions before the first release, 2.0.0) is moved into the data directory at the first open, when the data directory holds no database, log, snapshot or kept copy of a claude-mem-lite store yet; nothing else in either directory is moved or removed
 6. **Initialize database** -- SQLite with WAL mode, FTS5 indexes created on first server start
 
 Restart Claude Code after installation to activate.
@@ -208,12 +208,12 @@ All installation methods auto-detect and migrate from previous versions:
 
 **From claude-mem (original `~/.claude-mem/`):**
 - `claude-mem.db` and its `-wal`/`-shm` are moved into `~/.claude-mem-lite/` under `.legacy-backup-<time>` names (`claude-mem-lite.db.legacy-backup-<time>`, `claude-mem-lite.db-wal.legacy-backup-<time>`), when `~/.claude-mem-lite/claude-mem-lite.db` does not exist yet
+- The plugin install copies `claude-mem.db` alone into the data directory under the first of those names and leaves `~/.claude-mem/` as it is; it does so while the data directory holds neither a database nor such a backup
 - A fresh database is created: the original claude-mem schema has no upgrade path
 
 **From the unhidden directory of versions before the first release, 2.0.0 (`~/claude-mem-lite/`):**
 - Its database (`claude-mem-lite.db` or `claude-mem.db`, with its `-wal` and `-shm`) is moved into the data directory at the first open, when the data directory holds no database, log, snapshot or kept copy of a claude-mem-lite store yet. Nothing else is moved, and nothing in either directory is removed
 - The move is a rename: with `CLAUDE_MEM_DIR` on another filesystem it fails, and so does every open, until the database is moved there by hand together with its `-wal` and `-shm`
-- The plugin install differs: at session start, when `~/.claude-mem-lite/` does not exist, `scripts/setup.sh` moves the whole `~/claude-mem-lite/` directory there, whatever it holds; with `CLAUDE_MEM_DIR` set, nothing then reads the database it moved
 
 **In-place rename:**
 - Existing `claude-mem.db` in `~/.claude-mem-lite/` is automatically renamed to `claude-mem-lite.db`
@@ -1070,7 +1070,7 @@ claude-mem-lite/
   skill.md             # MCP skill definition (npx/git clone mode)
   package.json         # Dependencies and metadata
   scripts/
-    setup.sh           # Setup hook: npm install + migration (hidden dir + old dir)
+    setup.sh           # Setup hook: npm install + migration (original claude-mem DB, old file name)
     post-tool-use.sh   # Bash pre-filter: skips noise in ~5ms, tracks Read paths
     user-prompt-search.js # UserPromptSubmit hook: auto-search memory on user prompts
     pre-tool-recall.js   # PreToolUse hook: file lesson recall before Edit/Write

package/README.zh-CN.md

@@ -159,7 +159,7 @@ node install.mjs install
 > **想把托管块改写进 `CLAUDE.md`**（例如与团队共享）？运行 `claude-mem-lite adopt`：它向 `<cwd>/CLAUDE.md` 写入 slug 限定的托管块和详情文件，块以外的内容逐字保留，并删除自动写入的那份本地副本（`CLAUDE.local.md` 或 rules 文件）。`CLAUDE.md` 一存在，Claude Code 就不再读 `AGENTS.md`，所以 adopt 在 `AGENTS.md`（或 `.claude/AGENTS.md`）旁边新建 `CLAUDE.md` 时，会在文件开头导入它（`@AGENTS.md`，前面一行是 Claude Code 不加载的标记注释），`AGENTS.md` 因此继续加载；上层目录里的、或 git 跟踪在子目录里的 `AGENTS.md` 不能这样导入，adopt 会在输出里列出它们，并给出保留它们的设置（Project instructions 设为 `claude-md-and-agents-md`）。已经有你自己的 `CLAUDE.md` 时不导入，因为那里本来就不读 `AGENTS.md`。`unadopt` 会删除只剩这些行和托管块的 `CLAUDE.md`。带托管块的项目在**每次 SessionStart** 都会同步，出货模板变了会刷新，且不会再叠加本地副本或注入，从子目录启动的会话也一样。只有托管块的 `CLAUDE.md`（旧版本自动 adopt 写的）会在下一次从它所在目录启动的会话里补上同样的 `AGENTS.md` 导入，并给一次性提示。从子目录启动的会话看来，这个导入指向工作目录之外，Claude Code 会请你批准一次。插件创建过、又被你删掉（或被 `claude-mem-lite unadopt` 删掉）的本地托管块（`CLAUDE.local.md` 或 rules 文件）不会被写回，改为注入，直到运行 `claude-mem-lite adopt --enable`（在 `CLAUDE.local.md` 会让 `AGENTS.md` 失效的仓库里，还要设 `CLAUDE_MEM_RULES_STEERING=1` 才会再写文件）。关闭方式：项目级 `claude-mem-lite adopt --disable`（同时删除本地托管块；`CLAUDE.md` 托管块保留到 `unadopt`；重新启用用 `--enable`）；全局 `export MEM_NO_AUTO_ADOPT=1`（已写入的托管块保留并继续加载，直到 `unadopt`）；只冻结模板刷新用 `CLAUDE_MEM_NO_TEMPLATE_REFRESH=1`。`claude-mem-lite unadopt` 会移除 `CLAUDE.md` 托管块、详情文件，以及本地托管块（`CLAUDE.local.md` 或 `.claude/rules/claude-mem-lite.md`）和它的 exclude 条目。
 3. **配置钩子** -- 全部七个生命周期事件：`SessionStart`、`PreCompact`、`PreToolUse`、`PostToolUse`、`PostToolUseFailure`、`Stop`、`UserPromptSubmit`
 4. **创建数据目录** -- `~/.claude-mem-lite/`（隐藏目录），存放数据库与运行时文件
-5. **自动迁移** -- `~/.claude-mem/claude-mem.db`（原版 claude-mem）以 `.legacy-backup-<时间>` 文件的形式移入 `~/.claude-mem-lite/`，并新建一个数据库。`~/claude-mem-lite/`（首个发布版 2.0.0 之前的非隐藏目录）里留下的数据库在第一次打开时移入数据目录，前提是数据目录里还没有 claude-mem-lite 的数据库、日志、快照或保留副本；两个目录里的其他文件都不移动、不删除（插件安装不同，见"迁移"）
+5. **自动迁移** -- `~/.claude-mem/claude-mem.db`（原版 claude-mem）以 `.legacy-backup-<时间>` 文件的形式移入 `~/.claude-mem-lite/`，并新建一个数据库。`~/claude-mem-lite/`（首个发布版 2.0.0 之前的非隐藏目录）里留下的数据库在第一次打开时移入数据目录，前提是数据目录里还没有 claude-mem-lite 的数据库、日志、快照或保留副本；两个目录里的其他文件都不移动、不删除
 6. **初始化数据库** -- SQLite WAL 模式，FTS5 索引在服务器首次启动时创建
 
 安装后重启 Claude Code 以激活。
@@ -169,14 +169,13 @@ node install.mjs install
 所有安装方式自动检测并从旧版本迁移：
 
 **从 claude-mem 原版（`~/.claude-mem/`）：**
-- 复制 `claude-mem.db` → `~/.claude-mem-lite/claude-mem-lite.db`（重命名）
-- 复制 `runtime/` 目录
-- **原 `~/.claude-mem/` 保持不变**（不删除、不覆盖）
+- `claude-mem.db` 连同 `-wal`/`-shm` 以 `.legacy-backup-<时间>` 的名字（`claude-mem-lite.db.legacy-backup-<时间>`、`claude-mem-lite.db-wal.legacy-backup-<时间>`）移入 `~/.claude-mem-lite/`，前提是 `~/.claude-mem-lite/claude-mem-lite.db` 还不存在
+- 插件安装只把 `claude-mem.db` 以上面第一个名字复制进数据目录，`~/.claude-mem/` 原样不动；数据目录里既没有数据库、也没有这样的备份时才复制
+- 新建一个数据库：原版 claude-mem 的 schema 没有升级路径
 
 **从首个发布版（2.0.0）之前的非隐藏目录（`~/claude-mem-lite/`）：**
 - 它的数据库（`claude-mem-lite.db` 或 `claude-mem.db`，连同 `-wal` 和 `-shm`）在第一次打开时移入数据目录，前提是数据目录里还没有 claude-mem-lite 的数据库、日志、快照或保留副本。其他文件都不移动，两个目录里都不删除任何东西
 - 移动用的是改名：`CLAUDE_MEM_DIR` 在另一个文件系统上时会失败，之后每次打开都失败，直到手动把数据库连同 `-wal` 和 `-shm` 移过去
-- 插件安装不同：会话开始时，如果 `~/.claude-mem-lite/` 不存在，`scripts/setup.sh` 会把整个 `~/claude-mem-lite/` 目录移过去，不管里面有什么；设了 `CLAUDE_MEM_DIR` 时，移过去的数据库之后没有人读
 
 **就地重命名：**
 - 已有的 `~/.claude-mem-lite/claude-mem.db` 会自动重命名为 `claude-mem-lite.db`
@@ -841,7 +840,7 @@ claude-mem-lite/
   skill.md             # MCP 技能定义（npx/git clone 模式）
   package.json         # 依赖和元数据
   scripts/
-    setup.sh           # Setup 钩子：npm install + 迁移（隐藏目录 + 旧目录）
+    setup.sh           # Setup 钩子：npm install + 迁移（原版 claude-mem 数据库、旧文件名）
     post-tool-use.sh   # Bash 预过滤器：~5ms 跳过噪声，追踪 Read 路径
     user-prompt-search.js # UserPromptSubmit 钩子：用户提问时自动搜索记忆
     pre-tool-recall.js   # PreToolUse 钩子：Edit/Write 前文件教训回忆

package/npm-shrinkwrap.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "6.30.6",
+  "version": "6.30.7",
   "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",

package/scripts/setup.sh

@@ -99,8 +99,6 @@ if [[ -n "${CLAUDE_MEM_DIR:-}" || -n "${CLAUDE_MEM_RUNTIME_DIR:-}" ]] && [[ -f "
   unset _resolved _db _rt
 fi
 
-OLD_UNHIDDEN_DIR="$HOME/claude-mem-lite"
-
 # Colors
 if [[ -t 2 ]]; then
   GREEN='\033[0;32m'; YELLOW='\033[0;33m'; BLUE='\033[0;34m'; RED='\033[0;31m'; NC='\033[0m'
@@ -120,17 +118,12 @@ log_warn() { echo -e "${YELLOW}⚠${NC} $*" >&2; }
 # day GitHub bumps the runner image. Keep SC2317 for anyone on an older shellcheck.
 log_err()  { echo -e "${RED}✗${NC} $*" >&2; }
 
-# 1. Migrate unhidden dir (~/claude-mem-lite/ → ~/.claude-mem-lite/)
-#    CODE_DIR, not DB_DIR, and deliberately: the unhidden directory of versions before the
-#    first release held the INSTALL — server.mjs, hook.mjs, package.json — and CODE_DIR is the
-#    one location that must never follow the relocation env var. Moving it into a relocated
-#    DB_DIR would strand every absolute path settings.json and the MCP registration baked.
-if [[ -d "$OLD_UNHIDDEN_DIR" && ! -d "$CODE_DIR" ]]; then
-  mv "$OLD_UNHIDDEN_DIR" "$CODE_DIR"
-  log_ok "Migrated ~/claude-mem-lite/ → ~/.claude-mem-lite/"
-fi
+# 1. ~/claude-mem-lite/ (the unhidden dir of versions before the first release) is not moved
+#    here: the first open moves a store left there into DB_DIR, and only the store
+#    (schema.mjs migrateUnhiddenStore). This script moved the whole directory into a missing
+#    CODE_DIR, and a git clone of this repository made in ~ is at that path (D#568).
 
-# 2. Ensure both locations exist (runtime created after migration check)
+# 2. Ensure both locations exist
 mkdir -p "$CODE_DIR"
 mkdir -p "$DB_DIR"
 if [[ "$DB_DIR" == "$CODE_DIR" ]]; then
@@ -150,8 +143,19 @@ fi
 #    a relocation it never closed — nothing ever writes a database THERE — so this block
 #    copied the legacy database again on every single SessionStart, without bound. Measured
 #    2026-09-14: control arm stable at 1 backup across three runs, relocated arm 1 → 3.
+#    A backup already in DB_DIR closes it as well: while every open fails before creating the
+#    database (D#569's EXDEV did), the first condition never closes (D#573). Only the suffix is a
+#    pattern, so a `[` or `*` in DB_DIR's own path is matched as itself.
 OLD_DIR="$HOME/.claude-mem"
-if [[ -f "$OLD_DIR/claude-mem.db" && ! -f "$DB_DIR/claude-mem-lite.db" && ! -f "$DB_DIR/claude-mem.db" ]]; then
+has_legacy_backup() {
+  local f
+  for f in "$DB_DIR"/claude-mem-lite.db.legacy-backup-*; do
+    [[ -e "$f" ]] && return 0
+  done
+  return 1
+}
+if [[ -f "$OLD_DIR/claude-mem.db" && ! -f "$DB_DIR/claude-mem-lite.db" && ! -f "$DB_DIR/claude-mem.db" ]] &&
+  ! has_legacy_backup; then
   BACKUP="$DB_DIR/claude-mem-lite.db.legacy-backup-$(date +%s)"
   if cp "$OLD_DIR/claude-mem.db" "$BACKUP" 2>/dev/null; then
     log_info "Legacy ~/.claude-mem/ DB is schema-incompatible; backed up to $(basename "$BACKUP") (a fresh DB will be created). Old ~/.claude-mem/ preserved."
@@ -169,7 +173,7 @@ if [[ -f "$DB_DIR/claude-mem.db" && ! -f "$DB_DIR/claude-mem-lite.db" ]]; then
   log_ok "Database renamed: claude-mem.db → claude-mem-lite.db"
 fi
 
-# 5. Ensure runtime directories exist (after migration to not mask migration check).
+# 5. Ensure runtime directories exist.
 #    Both: RUNTIME_DIR carries the cross-component flag below, while CODE_DIR/runtime keeps
 #    the two run-once install markers at the bottom of this file.
 mkdir -p "$RUNTIME_DIR"