claude-mem-lite 3.61.0 → 3.61.1

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
   "plugins": [
     {
       "name": "claude-mem-lite",
-      "version": "3.61.0",
+      "version": "3.61.1",
       "source": "./",
       "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF 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": "3.61.0",
+  "version": "3.61.1",
   "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF 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/cli/common.mjs

@@ -176,6 +176,11 @@ export const KNOWN_CLI_FLAGS = new Set([
   // stay silent about (`adopt --disable/--enable`, `activity --min-importance`,
   // `save --supersedes`). Verified by running each command and checking for a warning.
   'disable', 'enable', 'min-importance', 'supersedes',
+  // `doctor --benchmark --prompts-limit N` — read off raw argv in cli/doctor.mjs, so
+  // it never appeared in a `flags.x` grep. Caught by independent review after the
+  // warn-on-every-unknown-flag flip turned the omission into a false warning on a
+  // documented, working command.
+  'prompts-limit',
 ]);
 
 /** Levenshtein distance, early-exit past `max` (cheap enough for a handful of flags). */

package/mem-cli.mjs

@@ -3194,7 +3194,7 @@ export async function run(argv) {
   for (const { flag, suggestion } of suggestUnknownFlags(parseArgs(cmdArgs).flags)) {
     process.stderr.write(suggestion
       ? `[mem] Unknown flag --${flag}; did you mean --${suggestion}?\n`
-      : `[mem] Unknown flag --${flag} — ignored (it filtered nothing). Run "claude-mem-lite help" for this command's flags.\n`);
+      : `[mem] Unknown flag --${flag} — ignored, it had no effect. Run "claude-mem-lite help" for this command's flags.\n`);
   }
 
   // adopt / unadopt do pure filesystem work on ~/.claude/projects/<encoded>/memory/ —

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "claude-mem-lite",
-  "version": "3.61.0",
+  "version": "3.61.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "claude-mem-lite",
-      "version": "3.61.0",
+      "version": "3.61.1",
       "dependencies": {
         "@modelcontextprotocol/sdk": "^1.26.0",
         "better-sqlite3": "^12.6.2",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-mem-lite",
-  "version": "3.61.0",
+  "version": "3.61.1",
   "description": "Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF 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/user-prompt-search.js

@@ -114,7 +114,7 @@ const OR_TOP_BM25_FLOOR = TOP_REL_FLOOR === 0
   ? 0
   : Number(process.env.CLAUDE_MEM_UPS_OR_BM25_MIN || 30);
 
-// ─── Corpus-size normalization of the absolute floors (v3.60.2) ─────────────
+// ─── Corpus-size normalization of the absolute floors (v3.61.0) ─────────────
 //
 // Both floors above are ABSOLUTE magnitudes, but the quantity they gate is not
 // scale-free: FTS5 bm25 carries an IDF term ≈ ln(N/df), so the SAME hit scores

package/secret-scrub.mjs

@@ -30,16 +30,45 @@ export const SECRET_PATTERNS = [
   // value is covered (the hex-only assignment pattern below misses non-hex values).
   //   1a. `=` assignment → ALWAYS scrub (config syntax, never prose):
   [/((?:\b|_)(?:password|passwd|passphrase|token|bearer|secret)\s*=\s*)(?!process\.env\.)(?!new\s)(?!\w+\()(?!(?:null|undefined|true|false|None|nil|empty|""|''|0)\b)[^\s,;'"}\]]{6,}/gi, '$1***'],
-  //   1b. `:` separator, PASSWORD nouns → always scrub. The prose lookbehind below
-  //       was originally applied to the whole noun class, which meant any credential
-  //       noun preceded by an English word escaped — so a session narrative like
-  //       "deployed to staging, the db password: hunter2correct" persisted the
-  //       password in plaintext and re-injected it into every later context block
-  //       (R5 dogfood, 2026-08-13). Unlike `token`/`bearer`/`secret`, the pinned
-  //       prose set (#8283) contains no `password|passwd|passphrase` case: writing
-  //       "<word> password: <6+ chars>" names a credential, it is not conversational
-  //       usage. Letter-glued non-keywords (`mypassword:`) still miss via `(?:\b|_)`.
-  [/((?:\b|_)(?:password|passwd|passphrase)\s*:\s*)(?!process\.env\.)(?!new\s)(?!\w+\()(?!(?:null|undefined|true|false|None|nil|empty|""|''|0)\b)[^\s,;'"}\]]{6,}/gi, '$1***'],
+  //   1b. `:` separator, PASSWORD nouns. Position decides how permissive the value
+  //       class may be, because the two positions have opposite error costs.
+  //
+  //       CONFIG position (start of line, or not preceded by an English word +
+  //       space) is unambiguous assignment syntax → scrub any value, exactly as
+  //       before. Pinned by the `  password: hunter2` indent cases.
+  //
+  //       PROSE position ("<word> password: …") is where v3.61.0 first removed the
+  //       lookbehind outright, to stop "deployed to staging, the db password:
+  //       hunter2correct" from persisting a credential. That closed a leak by
+  //       trading it for something worse: scrubbing runs on the WRITE path, and the
+  //       value class matches ordinary English, so "Reset the password: instructions
+  //       are in the onboarding doc" was stored irreversibly as "password: *** are
+  //       in the onboarding doc" (caught by independent pre-tag review). The claim
+  //       that "<word> password: <6+ chars>" always names a credential was simply
+  //       false. So in prose position the VALUE must look like a credential: not a
+  //       run of lowercase letters. A digit, any uppercase, or a symbol qualifies —
+  //       `hunter2correct`, `S3cretValue`, `correct-horse-battery-staple` all scrub,
+  //       while `instructions` / `rotation` / `yesterday` are left alone.
+  //
+  //       "Credential-shaped" is spelled as: NOT a single run of ≤15 letters. The
+  //       patterns carry `i`, so the letter class is case-insensitive by
+  //       construction — deliberately, because prose capitalizes ("Reset the
+  //       password: Instructions are in the doc" must survive, and a
+  //       lowercase-only test would corrupt it). The length bound is what still
+  //       catches a letters-only secret: English words in prose run short, secrets
+  //       do not, so `aVeryLongOpaqueSecretToken` (26) scrubs while `instructions`
+  //       (12) does not.
+  //
+  //       Two known, accepted gaps: a short letters-only password in prose position
+  //       ("the password: hunter") survives, and an English word longer than 15
+  //       letters is over-scrubbed. Config position still catches the former; the
+  //       latter is rare in prose and errs toward protecting a secret. A value
+  //       indistinguishable from an English word cannot be told from one without
+  //       corrupting prose — which is exactly the error this arm exists to undo.
+  //       Both arms emit `***` (3 chars, under the {6,} floor), so they cannot
+  //       double-apply.
+  [/((?<![A-Za-z][ \t])(?:\b|_)(?:password|passwd|passphrase)\s*:\s*)(?!process\.env\.)(?!new\s)(?!\w+\()(?!(?:null|undefined|true|false|None|nil|empty|""|''|0)\b)[^\s,;'"}\]]{6,}/gi, '$1***'],
+  [/((?:\b|_)(?:password|passwd|passphrase)\s*:\s*)(?!process\.env\.)(?!new\s)(?!\w+\()(?!(?:null|undefined|true|false|None|nil|empty|""|''|0)\b)(?![A-Za-z]{1,15}(?=[\s,;'"}\]]|$))[^\s,;'"}\]]{6,}/gi, '$1***'],
   //   1c. `:` separator, prose-ambiguous nouns → keep the lookbehind ("the token: alice"):
   [/((?<![A-Za-z][ \t])(?:\b|_)(?:token|bearer|secret)\s*:\s*)(?!process\.env\.)(?!new\s)(?!\w+\()(?!(?:null|undefined|true|false|None|nil|empty|""|''|0)\b)[^\s,;'"}\]]{6,}/gi, '$1***'],
   // access_token / refresh_token are the canonical OAuth2 field names — they were

package/server.mjs

@@ -1745,7 +1745,10 @@ server.registerTool(
   },
   // verbatim: the export payload feeds `restore` — defanging it would silently
   // rewrite backed-up rows whose text legitimately contains these tags.
-  safeHandler(async (args) => runExport(db, args), { verbatim: true })
+  safeHandler(
+    async (args) => runExport(db, applyArgAliases(args, { from: 'date_from', to: 'date_to' })),
+    { verbatim: true },
+  )
 );
 
 // ─── Tool: mem_recall ────────────────────────────────────────────────────────

package/tool-schemas.mjs

@@ -100,7 +100,7 @@ export const memSearchSchema = {
   or: coerceBool.optional().describe('Force OR semantics between query terms from the start (default: AND with automatic OR-fallback when AND returns 0). Aligns with CLI --or.'),
   deep: coerceBool.optional().describe('Tri-state LLM multi-query/HyDE deep search (observations-only). true=force; false=never; omit=AUTO (default ON for mem_search): a normal search that returns weak/few results auto-escalates with ONE Haiku call (query rewritten to keyword/concept/HyDE variants, RRF-fused). Set CLAUDE_MEM_AUTO_DEEP=0 to disable AUTO. Passive recall stays single-query.'),
   rerank: coerceBool.optional().describe('Opt-in: LLM-rerank the deep-search candidates for ranking precision (one extra Haiku call, ~1.4s). Requires deep=true (no effect on AUTO/normal). Reserve for hard, ranking-sensitive queries where the right memory is likely retrieved but mis-ranked — skip for routine search. Default off.'),
-  // ── CLI-flag aliases (v3.60.2) ──────────────────────────────────────────────
+  // ── CLI-flag aliases (v3.61.0) ──────────────────────────────────────────────
   // A property the schema doesn't declare is STRIPPED by the validator, so a caller
   // using the CLI vocabulary (`--source` / `--from` / `--to` / `--since`) previously
   // got the UNFILTERED answer with nothing marking the filter as dropped — a wider
@@ -274,6 +274,11 @@ export const memExportSchema = {
   format: z.enum(['json', 'jsonl']).optional().describe('Output format (default: json)'),
   date_from: z.string().optional().describe('Start date (ISO 8601 or YYYY-MM-DD)'),
   date_to: z.string().optional().describe('End date (ISO 8601 or YYYY-MM-DD)'),
+  // CLI-flag aliases — `export` reads flags.from / flags.to (mem-cli.mjs). Same
+  // silent-drop defect the search/recent aliases fix, and the widest blast radius of
+  // the three: an ignored bound exports the whole DB instead of a date slice.
+  from: z.string().optional().describe('Alias for `date_from` (CLI `export --from`)'),
+  to: z.string().optional().describe('Alias for `date_to` (CLI `export --to`)'),
   include_compressed: coerceBool.optional().describe('Include compressed observations (default: false)'),
   limit: coerceInt.pipe(z.number().int().min(1).max(1000)).optional().describe('Max observations to export (default: 200, max: 1000)'),
 };