memtrace 0.6.30 → 0.6.46

package/lib/claude-integration.js

@@ -236,15 +236,32 @@ function applySettingsHooks(settings, hooksDir) {
  *      into the *first* matching block. Pre-existing duplicates in
  *      other blocks were never cleaned up, just left to compound.
  *
+ *   3. (issue #26) Both prior axes are install-path-sensitive: the
+ *      marker match needs the underscore keys to survive, and the
+ *      exact-command match only catches a hook at the SAME absolute
+ *      path we're about to write. When the install location moves
+ *      between versions (a version-pinned store dir, a different
+ *      global prefix, a `/private/tmp` upgrade-test root) the prior
+ *      entry sits at a different path with no markers, matches
+ *      nothing, and survives every re-inject — accumulating, and
+ *      dangling once that old path is pruned (its `command` then
+ *      shells out to a script that no longer exists, erroring on
+ *      every UserPromptSubmit / PostToolUse).
+ *
  * The new contract: regardless of how settings.json got into its
  * current shape, this function leaves it with exactly one of our
  * hooks installed under exactly one block. Running it 100 times
  * produces the same result as running it once — and self-heals
- * existing duplication on the way through.
+ * existing duplication (including stale, differently-pathed, and
+ * dangling copies) on the way through.
  *
  * Match strategy: a hook is "ours" if it has the managed markers
- * intact OR its command path matches one we generate. The
- * command-path match is what catches stripped-marker pollution.
+ * intact OR its command path matches one we generate OR its command
+ * ends in one of our hook script basenames. The basename match is
+ * the path-independent axis that catches stripped-marker pollution
+ * AND stale/dangling entries left at a previous install path (#26) —
+ * it mirrors the uninstaller's `isMemtraceHook` suffix test so inject
+ * and uninstall recognise exactly the same set of entries.
  *
  * @param {Array} existing
  * @param {object} ourEntry  shape `{ matcher?, hooks: [...] }`
@@ -252,10 +269,15 @@ function applySettingsHooks(settings, hooksDir) {
  * @returns {Array}
  */
 function mergeHookList(existing, ourEntry, ourHook) {
+    const ourBasename =
+        typeof ourHook.command === "string" ? path.basename(ourHook.command) : null;
     const isOurs = (h) =>
         !!h && (
             (h._managed_by === HOOK_MANAGED_TAG && h._hook_kind === ourHook._hook_kind) ||
-            (typeof h.command === "string" && h.command === ourHook.command)
+            (typeof h.command === "string" && h.command === ourHook.command) ||
+            (ourBasename !== null &&
+                typeof h.command === "string" &&
+                path.basename(h.command) === ourBasename)
         );
 
     // Phase 1: walk every block, strip every "ours" hook, drop blocks

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memtrace",
-  "version": "0.6.30",
+  "version": "0.6.46",
   "description": "Code intelligence graph — MCP server + AI agent skills + visualization UI",
   "keywords": [
     "mcp",
@@ -39,12 +39,12 @@
     "fs-extra": "^11.0.0"
   },
   "optionalDependencies": {
-    "@memtrace/darwin-arm64": "0.6.30",
-    "@memtrace/linux-x64": "0.6.30",
-    "@memtrace/linux-arm64": "0.6.30",
-    "@memtrace/win32-x64": "0.6.30",
-    "@memtrace/linux-x64-noavx2": "0.6.30",
-    "@memtrace/win32-x64-noavx2": "0.6.30"
+    "@memtrace/darwin-arm64": "0.6.46",
+    "@memtrace/linux-x64": "0.6.46",
+    "@memtrace/linux-arm64": "0.6.46",
+    "@memtrace/win32-x64": "0.6.46",
+    "@memtrace/linux-x64-noavx2": "0.6.46",
+    "@memtrace/win32-x64-noavx2": "0.6.46"
   },
   "engines": {
     "node": ">=18"