claude-mem-lite 6.22.0 → 6.22.1

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "6.22.0",
+      "version": "6.22.1",
       "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.22.0",
+  "version": "6.22.1",
   "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

@@ -534,6 +534,20 @@ surface — reach them through the CLI column in the second table.
 | `mem_fts_check` | `claude-mem-lite fts-check <check\|rebuild>` | FTS5 integrity + rebuild. |
 | `mem_browse` | `claude-mem-lite browse` | Tier-grouped dashboard (working / active / archive). |
 
+**Headless runs (`claude -p`).** With no permission prompt to answer, Claude Code 2.1.292
+refused every `mem_*` call until the server's tools were allowed, and the model did not switch
+to the CLI by itself: in an 88-session headless run (2026-10-06) all 13 calls were refused and
+nothing was saved. On 2.1.284 (2026-09-29) the same flags let these calls through, so this
+depends on the Claude Code version. Allow the server once in the `settings.json` the run reads:
+
+```json
+{ "permissions": { "allow": ["mcp__plugin_claude-mem-lite_mem-lite"] } }
+```
+
+That is the server's name under a plugin install. An npx or git-clone install registers it as
+`mem-lite`, so the rule there is `mcp__mem-lite`. An interactive session asks instead; answering
+"always allow" there records a rule of its own.
+
 ### Skill Commands (in Claude Code chat)
 
 ```

package/README.zh-CN.md

@@ -439,6 +439,14 @@ README 和 `docs/ARCHITECTURE.md` 都钉在它上面。）
 | `mem_fts_check` | `claude-mem-lite fts-check <check\|rebuild>` | FTS5 完整性检查与重建。 |
 | `mem_browse` | `claude-mem-lite browse` | 分层仪表盘（working / active / archive）。 |
 
+**无人值守运行（`claude -p`）。** 没有权限确认可答时，Claude Code 2.1.292 拒绝了所有 `mem_*` 调用，直到服务的工具被放行；模型也没有自己改用 CLI。在 88 个无人值守会话里（2026-10-06），13 次调用全部被拒，什么都没存下。在 2.1.284 上（2026-09-29），同样的参数会放行这些调用，所以这取决于 Claude Code 版本。在这次运行读取的 `settings.json` 里放行一次即可：
+
+```json
+{ "permissions": { "allow": ["mcp__plugin_claude-mem-lite_mem-lite"] } }
+```
+
+这是插件安装方式下的服务名。npx 或 git clone 安装方式把服务注册为 `mem-lite`，对应的规则是 `mcp__mem-lite`。交互式会话会弹出确认；在那里选"始终允许"会另外记下一条规则。
+
 ### 技能命令（在 Claude Code 聊天中使用）
 
 ```

package/adopt-cli.mjs

@@ -62,6 +62,7 @@ import {
   forgetLocalSteering,
   localSteeringRemembered,
   agentsMdForNewClaudeMd,
+  claudeMdSwitchesOffAgentsBelow,
   tildePath,
   RULES_MD,
   RULES_REFUSAL_TEXT,
@@ -190,6 +191,15 @@ function adoptOne(cwd, { force, dryRun }) {
       (p) =>
         `  ⚠ ${p} ${verb} loading in sessions here once CLAUDE.md exists; set Project instructions to claude-md-and-agents-md in /config to keep it`,
     );
+  // D#225: at $HOME or `/` the file is above every project there, which no list above can name.
+  // Written anyway (adopt was asked to), and said.
+  const switchesOffBelow = claudeMdSwitchesOffAgentsBelow(cwd, PLUGIN_SLUG);
+  const sharedNote = (verb) =>
+    switchesOffBelow
+      ? [
+          `  ⚠ ${claudeMdPath(cwd)} ${verb} Claude Code reading the AGENTS.md of every project below ${cwd} that has one; to steer one project, run adopt inside it instead${verb === 'stops' ? ' (`claude-mem-lite unadopt` here takes this back)' : ''}, or set Project instructions to claude-md-and-agents-md in /config`,
+        ]
+      : [];
 
   if (dryRun) {
     log(`[adopt --dry-run] ${cwd}`);
@@ -198,6 +208,7 @@ function adoptOne(cwd, { force, dryRun }) {
     if (imports.length > 0)
       log(`  AGENTS.md:        would import ${imports.join(', ')} at the top of CLAUDE.md`);
     for (const line of elsewhere('would stop')) log(line);
+    for (const line of sharedNote('would stop')) log(line);
     if (hasLegacyMemdirSentinel(cwd, PLUGIN_SLUG)) {
       log(`  legacy migrate:   would strip memory-dir sentinel @ ${memdirPath(cwd)}`);
     }
@@ -224,6 +235,7 @@ function adoptOne(cwd, { force, dryRun }) {
             : ` (+removed the block from ${local.path})`;
     log(`[adopt] ${cwd} → ${r.action}${migNote}${localNote}${importNote}`);
     for (const line of elsewhere('stops')) log(line);
+    for (const line of sharedNote('stops')) log(line);
     // The copy that could not come out loads beside CLAUDE.md: said, and not a success (R3-4).
     if (local.action === 'failed') {
       if (local.residue) log(`  ⚠ ${local.residue}`);

package/install.mjs

@@ -10,7 +10,6 @@ import {
   rmSync,
   mkdirSync,
   mkdtempSync,
-  copyFileSync,
   renameSync,
   symlinkSync,
   unlinkSync,
@@ -98,7 +97,7 @@ import { detectInstallShape, probeRuntimeRoots, hasAnyManagedCode } from './lib/
 import { probeSchemaCompat, schemaSkewRemedy } from './lib/schema-skew.mjs';
 import { clearNativeBindingBreakage, readNativeBindingBreakage } from './lib/native-binding-hint.mjs';
 import { acquireLock } from './lib/proc-lock.mjs';
-import { atomicWriteFileSync } from './lib/atomic-write.mjs';
+import { atomicWriteFileSync, atomicCopyFileSync } from './lib/atomic-write.mjs';
 import { shellWord } from './cli-path.mjs';
 import { claudeStatePath } from './lib/data-paths.mjs';
 import { isMemHook, isMemHookCommand, stripMemHooks, launcherEntryPath } from './lib/hook-prune.mjs';
@@ -118,7 +117,8 @@ export { probeBetterSqlite3Binding, ensureBetterSqlite3Working };
 export function copyHookScripts(srcDir, destDir) {
   for (const name of HOOK_SCRIPT_FILES) {
     const src = join(srcDir, name);
-    if (existsSync(src)) copyFileSync(src, join(destDir, name));
+    // By rename, not in place: hooks import these while install runs (D#223).
+    if (existsSync(src)) atomicCopyFileSync(src, join(destDir, name));
   }
 }
 
@@ -454,7 +454,38 @@ const importFromInstall = (rel) => import(pathToFileURL(join(INSTALL_DIR, rel)).
 const requireFromInstall = createRequire(pathToFileURL(join(INSTALL_DIR, 'package.json')).href);
 
 // ─── install() step helpers (audit P1-9) ──────────────────────────────────────
-function installSourceFiles(IS_DEV) {
+
+// Swap barrier (R10 P2-12, D#223). Hooks import this code tree on every tool call, and
+// `install` — also what a background `repair` ends in — rewrites it while a session runs.
+// hook-update.mjs arms this same marker around its renames and scripts/hook-launcher.mjs
+// skips a fire while it is present, so a fire that starts mid-deploy is dropped instead of
+// importing a mix of two versions. The marker carries pid + ts because the launcher ignores
+// one whose writer is gone or which is older than two minutes. Callers hold install.lock,
+// which hook-update's swap takes too, so the two never arm it at once.
+const SWAP_MARKER = join(MEM_DATA_DIR, 'runtime', 'swap-in-progress'); // runtime-dir:stays-put — installation identity; the launcher reads it here
+
+export async function withSwapBarrier(fn) {
+  try {
+    mkdirSync(dirname(SWAP_MARKER), { recursive: true });
+    writeFileSync(SWAP_MARKER, JSON.stringify({ pid: process.pid, ts: Date.now() }));
+  } catch {
+    /* best-effort: without it hooks fire unbarriered, as before */
+  }
+  try {
+    return await fn();
+  } finally {
+    try {
+      rmSync(SWAP_MARKER, { force: true });
+    } catch {
+      /* a marker left behind expires with its writer */
+    }
+  }
+}
+
+// Creates the data dirs the swap barrier then writes its marker into. The legacy-dir migration
+// here runs only under CLAUDE_MEM_DIR relocation: in the default shape runLockedInstall's
+// install.lock has created ~/.claude-mem-lite before install() starts (pre-existing, D#238).
+function prepareInstallDirs() {
   // Auto-migrate unhidden dir (~/claude-mem-lite/ → ~/.claude-mem-lite/)
   const oldUnhidden = join(homedir(), 'claude-mem-lite');
   if (!existsSync(DATA_DIR) && existsSync(oldUnhidden)) {
@@ -466,7 +497,9 @@ function installSourceFiles(IS_DEV) {
   if (!existsSync(DATA_DIR)) mkdirSync(DATA_DIR, { recursive: true });
   // Under relocation the DB/managed/runtime live here, not in the code dir — create it too.
   if (!existsSync(MEM_DATA_DIR)) mkdirSync(MEM_DATA_DIR, { recursive: true });
+}
 
+export function deployCodeTree(IS_DEV) {
   if (IS_DEV) {
     log('Dev mode — creating symlinks in ~/.claude-mem-lite/...');
     // Symlink individual source files
@@ -512,7 +545,7 @@ function installSourceFiles(IS_DEV) {
         // Ensure parent dir exists for subdir entries (e.g. 'lib/activity.mjs')
         const dstParent = dirname(dst);
         if (!existsSync(dstParent)) mkdirSync(dstParent, { recursive: true });
-        copyFileSync(src, dst);
+        atomicCopyFileSync(src, dst); // by rename, not in place (D#223)
       }
     }
     // Copy hook scripts (settings.json hook commands point at these — must
@@ -1250,8 +1283,15 @@ async function install() {
   // 1. Install source files to ~/.claude-mem-lite/
   const IS_DEV = flags.has('--dev');
 
-  installSourceFiles(IS_DEV);
-  await installDependencies(IS_DEV);
+  prepareInstallDirs();
+  // Both steps rewrite the tree hooks import — the code, then node_modules — so one swap
+  // barrier spans them (D#223), for its first two minutes: the launcher ignores an older marker,
+  // and npm install has no timeout. installDependencies may process.exit(1): the marker it leaves
+  // names a dead pid, which the launcher ignores.
+  await withSwapBarrier(async () => {
+    deployCodeTree(IS_DEV);
+    await installDependencies(IS_DEV);
+  });
   createCliSymlink();
   registerMcpServer();
   // configureHooks BEFORE dedupe, and its result feeds the dedup gate: dedupe now

package/lib/atomic-write.mjs

@@ -95,3 +95,29 @@ export function atomicWriteFileSync(filePath, data, { backup = false, mode: newF
     throw e;
   }
 }
+
+/**
+ * Replace `dst` with a copy of `src` by rename, so a concurrent reader sees the old file or
+ * the new one, never a truncated one. copyFileSync onto a live file opens it with O_TRUNC and
+ * then writes: a hook importing it in between gets an empty or half-written module (D#223).
+ * Unlike atomicWriteFileSync this does NOT write through a symlink at `dst`: the targets are
+ * installed code files, where a link left by a dev-mode install must be replaced, not used to
+ * overwrite the developer's checkout. The source's mode bits come along (copyFileSync keeps
+ * them), so an executable hook script stays executable.
+ * @param {string} src
+ * @param {string} dst
+ */
+export function atomicCopyFileSync(src, dst) {
+  const tmp = `${dst}.tmp-${process.pid}`;
+  try {
+    copyFileSync(src, tmp);
+    renameSync(tmp, dst);
+  } catch (e) {
+    try {
+      unlinkSync(tmp);
+    } catch {
+      /* nothing written, or already gone */
+    }
+    throw e;
+  }
+}

package/lib/local-steering.mjs

@@ -382,6 +382,24 @@ export function agentsMdForNewClaudeMd(dir, slug) {
   return AGENTS_MD_UNAFFECTED.has(userInstructionFiles()) ? null : { imports, elsewhere };
 }
 
+/**
+ * Whether a CLAUDE.md written in `dir` switches AGENTS.md off in every project below it, beyond the
+ * files agentsMdForNewClaudeMd can list (D#225): `dir` is $HOME or `/`, no CLAUDE.md or
+ * CLAUDE.local.md of the user's at or above it has done so already, and Project instructions is not
+ * a value that reads AGENTS.md regardless.
+ * @param {string} dir where CLAUDE.md is written
+ * @param {string} slug
+ * @returns {boolean}
+ */
+export function claudeMdSwitchesOffAgentsBelow(dir, slug) {
+  const d = resolve(dir);
+  return (
+    isSharedAncestor(d) &&
+    !instructionFileAtOrAbove(d, slug) &&
+    !AGENTS_MD_UNAFFECTED.has(userInstructionFiles())
+  );
+}
+
 function instructionFileAtOrAbove(start, slug) {
   const home = realOrResolved(homedir());
   const usersFile = (p) => existsSync(p) && !holdsOnlyOwnLines(p, slug);

package/npm-shrinkwrap.json

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

package/package.json

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

@@ -155,16 +155,12 @@ const entryAbs = entryArg.startsWith('/') ? entryArg : join(INSTALL_DIR, entryAr
 // 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.
+// Two writers arm it: hook-update.mjs around its renames, and install.mjs's install()
+// around deploying the code tree and its npm install — also what `install.mjs repair`
+// ends in, which SessionStart can spawn in the background while hooks keep firing. The
+// install side came late (R10 P2-12, D#223): it copied in place with copyFileSync, and
+// tests/sandbox/phaseB-npm.mjs B10 caught a fire importing a truncated module on a
+// same-version re-install. Its copies now go through a rename as well.
 //
 // 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.