memex-mvp 0.10.4 → 0.10.6

package/lib/notify-click-action.js

@@ -213,8 +213,11 @@ function shellQuote(s) {
  *
  *   opts = {
  *     title, subtitle, message,
- *     target,           // 'auto' | 'claude-cli' | 'claude-desktop' | 'terminal' | 'none'
- *     env,              // optional override of detected env (for tests)
+ *     target,    // 'auto' | 'claude-cli' | 'claude-desktop' | 'terminal' | 'none'
+ *     env,       // optional override of detected env (for tests)
+ *     dryRun,    // if true → compute backend+target+command but DON'T spawn.
+ *                //   Used by unit tests so `npm test` doesn't spam real
+ *                //   macOS notifications. Also honors env MEMEX_NO_FIRE=1.
  *   }
  *
  * Returns { backend: 'terminal-notifier' | 'osascript' | 'noop',
@@ -226,13 +229,14 @@ export function fireClickableNotification(opts = {}) {
 
   const target = pickTarget(opts.target || 'auto', env);
   const click = buildClickCommand(target, env);
+  const dryRun = opts.dryRun === true || process.env.MEMEX_NO_FIRE === '1';
 
   const title = opts.title || 'memex';
   const subtitle = opts.subtitle || '';
   const message = opts.message || '';
 
   if (env.terminal_notifier && click) {
-    // terminal-notifier path — clickable
+    if (dryRun) return { backend: 'terminal-notifier', target, click_command: click };
     const args = [
       '-title', title,
       '-message', message,
@@ -240,7 +244,7 @@ export function fireClickableNotification(opts = {}) {
     ];
     if (subtitle) { args.push('-subtitle'); args.push(subtitle); }
     args.push('-sound', 'Pop');
-    args.push('-sender', 'com.apple.Terminal'); // groups under Terminal in NC
+    args.push('-sender', 'com.apple.Terminal');
     try {
       spawn(env.terminal_notifier, args, { detached: true, stdio: 'ignore' }).unref();
       return { backend: 'terminal-notifier', target, click_command: click };
@@ -248,6 +252,7 @@ export function fireClickableNotification(opts = {}) {
   }
 
   // Plain osascript fallback — banner is not clickable but text is informative
+  if (dryRun) return { backend: 'osascript', target: 'none', click_command: null };
   const esc = (s) => String(s || '').replace(/\\/g, '\\\\').replace(/"/g, '\\"');
   const sub = subtitle ? ` subtitle "${esc(subtitle)}"` : '';
   const script = `display notification "${esc(message)}" with title "${esc(title)}"${sub} sound name "Pop"`;

package/lib/telegram-notify.js

@@ -33,6 +33,7 @@ import {
   writeFileSync,
   renameSync,
   mkdirSync,
+  statSync,
 } from 'node:fs';
 import { createHash } from 'node:crypto';
 import { join, dirname } from 'node:path';
@@ -106,8 +107,26 @@ export function markCliTipShown(state, now = new Date()) {
 
 // ---------------------- Notification dedup ----------------------
 
+/**
+ * Stable hash of a pending export for notification dedup.
+ *
+ * v0.10.5+: hash now incorporates the file's mtime in addition to path.
+ *
+ * Why: Telegram Desktop reuses the same folder name on same-day re-exports
+ * (e.g. ChatExport_2026-05-16). After memex imports & removes that folder
+ * from pending, a fresh export with the same date creates the same path
+ * again. Path-only hash collided → notification was incorrectly deduped
+ * as "already shown".
+ *
+ * Including mtime makes the hash content-aware: same path + different
+ * mtime → fresh hash → notification fires. If the path doesn't exist
+ * (file was deleted), we fall back to path-only — it's an edge case
+ * (notifShownFor check before fire, file should exist).
+ */
 export function notifIdFor(path) {
-  return createHash('sha256').update(String(path)).digest('hex').slice(0, 16);
+  let mtimeKey = '';
+  try { mtimeKey = String(Math.floor(statSync(path).mtimeMs)); } catch (_) { /* path missing — fall back to path-only */ }
+  return createHash('sha256').update(String(path) + ':' + mtimeKey).digest('hex').slice(0, 16);
 }
 
 export function notifShownFor(state, path) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memex-mvp",
-  "version": "0.10.4",
+  "version": "0.10.6",
   "description": "Local-first MCP server for cross-agent AI memory. One SQLite + FTS5 corpus across Claude Code, Cowork, Cursor, Continue, Zed, Obsidian, and Telegram — passively captured, verbatim, searchable from any MCP-compatible client.",
   "type": "module",
   "main": "server.js",