@massa-ai/claude-plugin 1.52.0 → 1.54.1

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "massa-ai",
-  "version": "1.52.0",
+  "version": "1.54.1",
   "description": "massa-ai — semantic code search, durable memory, symbol graph, and context compression",
   "author": {
     "name": "Luiz Massa",

package/install.sh

@@ -185,8 +185,54 @@ try {
   }
 }
 
+// Ownership test. The `_massaAiOwned` marker is the precise signal, but it is
+// NOT the only way our hook entries reach settings.json: this plugin also ships
+// settings.json.template, a hand-merge guide whose blocks carry no marker and
+// whose command the reader is told to rewrite to an absolute path. Entries that
+// arrived that way were invisible to both directions of this merge — never
+// deduped on install, never removed when the marketplace route took over — so
+// they fired alongside the bundle's own hooks/hooks.json. Measured live
+// 2026-08-17: 5 unmarked massa-ai blocks in ~/.claude/settings.json beside a
+// registered marketplace plugin, and every event ingested twice.
+//
+// So recognise our entries by WHAT THEY ARE as well. Referencing the
+// massa-ai-hook binary is unambiguous — it is this project's own file name, in
+// every shape it is documented in (`bun run "<abs>/massa-ai-hook.ts" <sub>`,
+// `bun run "${CLAUDE_PLUGIN_ROOT}/hooks/massa-ai-hook.ts" <sub>`). A user hook
+// that merely mentions massa-ai elsewhere (`rtk hook claude`, an MCP tool name)
+// does not match and is preserved.
+const OWNED_COMMAND = /massa-ai-hook/;
+
+function commandIsOwned(h) {
+  return Boolean(h) && typeof h.command === "string" && OWNED_COMMAND.test(h.command);
+}
+
+// A matcher-group block is ours when it is marked, or when every command it
+// carries is ours. A block MIXING user and massa-ai commands is not owned
+// wholesale — stripOwnedHooks below removes only our commands from it.
+function blockIsOwned(b) {
+  if (!b || typeof b !== "object") return false;
+  if (b._massaAiOwned === true) return true;
+  return Array.isArray(b.hooks) && b.hooks.length > 0 && b.hooks.every(commandIsOwned);
+}
+
 function hasOwned(arr) {
-  return Array.isArray(arr) && arr.some((e) => e && e._massaAiOwned === true);
+  return Array.isArray(arr) && arr.some(blockIsOwned);
+}
+
+// Returns the event array with our entries removed: whole blocks that are ours,
+// and our individual commands out of blocks we share with the user.
+function stripOwnedHooks(arr) {
+  const kept = [];
+  for (const b of arr) {
+    if (blockIsOwned(b)) continue;
+    if (b && Array.isArray(b.hooks) && b.hooks.some(commandIsOwned)) {
+      kept.push({ ...b, hooks: b.hooks.filter((h) => !commandIsOwned(h)) });
+      continue;
+    }
+    kept.push(b);
+  }
+  return kept;
 }
 
 // Double-fire guard: true when massa-ai is already installed as a Claude Code
@@ -223,20 +269,54 @@ function pluginAlreadyInstalled() {
 if (mode === "uninstall") {
   const hooks = cfg.hooks;
   if (hooks && typeof hooks === "object" && !Array.isArray(hooks)) {
-    for (const [evt] of EVENTS) {
+    // Back up before removing. The install path has always done this; removal
+    // did not, and now that it deletes unmarked entries it did not necessarily
+    // write, the asymmetry is not defensible.
+    if (existed) {
+      fs.copyFileSync(file, `${file}.massa-ai.bak-${ts}`);
+    }
+    // Every event, not just the 5 we write. The predicate identifies our
+    // commands rather than a location, so an entry parked under an event this
+    // release does not use is still ours, and a user's is still not.
+    for (const evt of Object.keys(hooks)) {
       if (Array.isArray(hooks[evt])) {
-        hooks[evt] = hooks[evt].filter((e) => !(e && e._massaAiOwned === true));
+        hooks[evt] = stripOwnedHooks(hooks[evt]);
         if (hooks[evt].length === 0) delete hooks[evt];
       }
     }
     if (Object.keys(hooks).length === 0) delete cfg.hooks;
   }
 } else if (pluginAlreadyInstalled()) {
-  console.error(
-    "  ↷ massa-ai is installed as a Claude Code plugin — skipping settings.json" +
-      " hooks (the plugin already provides them; wiring both would double-fire)",
-  );
-  process.exit(0);
+  // Not writing is only half the guard. If settings.json ALREADY carries our
+  // entries — from an older release, or from a hand-merge of
+  // settings.json.template — declining to add more still leaves both sources
+  // live. This branch is reached with the plugin registered but no usable
+  // `claude` CLI, so the marketplace route (which removes them) never runs.
+  // Strip them here and fall through to the write.
+  const hooks = cfg.hooks;
+  let removed = 0;
+  if (hooks && typeof hooks === "object" && !Array.isArray(hooks)) {
+    for (const evt of Object.keys(hooks)) {
+      if (!Array.isArray(hooks[evt])) continue;
+      const before = JSON.stringify(hooks[evt]);
+      hooks[evt] = stripOwnedHooks(hooks[evt]);
+      if (JSON.stringify(hooks[evt]) !== before) removed++;
+      if (hooks[evt].length === 0) delete hooks[evt];
+    }
+    if (Object.keys(hooks).length === 0) delete cfg.hooks;
+  }
+  if (removed > 0) {
+    if (existed) fs.copyFileSync(file, `${file}.massa-ai.bak-${ts}`);
+    console.error(
+      `  ↷ massa-ai is installed as a Claude Code plugin — removed ${removed} stale` +
+        " settings.json hook event(s) that would have fired alongside the plugin's own",
+    );
+  } else {
+    console.error(
+      "  ↷ massa-ai is installed as a Claude Code plugin — skipping settings.json" +
+        " hooks (the plugin already provides them; wiring both would double-fire)",
+    );
+  }
 } else {
   // install: backup before first write if file existed
   if (existed) {
@@ -309,7 +389,7 @@ install_bundled_skills() {
   fi
 
   local installed=0 name src dest
-  for name in massa-ai persona-router; do
+  for name in massa-ai persona-router profile; do
     src="$SCRIPT_DIR/skills/$name"
     [[ -d "$src" ]] || continue
     dest="$HARNESS_SKILLS_DIR/$name"
@@ -338,7 +418,7 @@ if (typeof data.platforms !== "object" || data.platforms === null || Array.isArr
 }
 data.version = 2;
 const prev = data.platforms[host];
-data.platforms[host] = { root, skillsOwner: "plugin", skills: ["massa-ai", "persona-router"] };
+data.platforms[host] = { root, skillsOwner: "plugin", skills: ["massa-ai", "persona-router", "profile"] };
 // The whole-record replace must not drop fields a previous successful install
 // wrote (R2) — re-attach them. modelProfile (T10, MPS-03 round-trip
 // obligation) is engine-owned; installRoute is installer-owned but written by
@@ -385,7 +465,7 @@ NODE
   )"
   [[ "$raw_owner" == "plugin" ]] && {
     local name
-    for name in massa-ai persona-router; do
+    for name in massa-ai persona-router profile; do
       rm -rf "$HARNESS_SKILLS_DIR/$name"
     done
     rmdir "$HARNESS_SKILLS_DIR" 2>/dev/null || true
@@ -734,10 +814,16 @@ remove_file_route_artifacts() {
   if [[ -f "$SETTINGS_JSON" ]]; then
     merge_settings_hooks "$SETTINGS_JSON" "uninstall"
   fi
+  # Prefix-glob against the INSTALLED directory, not the source bundle (IPT-03
+  # site 6, D2): deriving removals from $SCRIPT_DIR/commands/*.md misses
+  # installed copies whenever the bundle is absent or stale (normal under
+  # AD-016). Mirrors the agents loop directly below, which already does this
+  # correctly. The keep-list here is empty by design — the marketplace bundle
+  # serves its own commands, so every loose file-route copy is removed.
   if [[ -d "$TARGET/commands" ]]; then
-    for src in "$SCRIPT_DIR/commands/"*.md; do
-      [[ -f "$src" ]] || continue
-      rm -f "$TARGET/commands/massa-ai-$(basename "$src" .md).md"
+    for f in "$TARGET/commands/"massa-ai-*.md; do
+      [[ -f "$f" ]] || continue
+      rm -f "$f"
     done
   fi
   if [[ -d "$TARGET/agents" ]]; then
@@ -824,6 +910,21 @@ else
     command_count=$((command_count + 1))
   done
 
+  # Shed commands retired from the bundle (IPT-02 site 2, D1 copy-then-prune):
+  # copy the current set first, then remove owned destination entries the
+  # bundle no longer ships — never the reverse, so an interrupted run never
+  # leaves the user with fewer commands than before. Removal population is the
+  # destination directory (D2); ownership test is the massa-ai- name prefix
+  # (install.sh:765).
+  for f in "$TARGET/commands/"massa-ai-*.md; do
+    [[ -f "$f" ]] || continue
+    prune_name="$(basename "$f" .md)"
+    prune_name="${prune_name#massa-ai-}"
+    [[ -f "$SCRIPT_DIR/commands/${prune_name}.md" ]] && continue
+    rm -f "$f"
+    vecho "  - removed retired command $(basename "$f")"
+  done
+
   # Subagent specialists (generated from skills/agents/*/SKILL.md, navigator
   # included). The massa-ai- name prefix is the ownership marker used by uninstall.
   #
@@ -859,6 +960,20 @@ else
   done
   vecho "  + ${specialist_count} subagent specialists (generated from skills/agents/*/SKILL.md)"
 
+  # Shed specialists retired from the bundle (IPT-02 site 1, D1
+  # copy-then-prune): copy the current set first, then remove owned
+  # destination entries ACTIVE_AGENTS_SRC (the bundle, or the active
+  # model-profile variant) no longer ships. Never prune-then-copy — an
+  # interrupted run must never leave the user with fewer agents than before.
+  # Removal population is the destination directory (D2); ownership test is
+  # the massa-ai- name prefix (install.sh:775-777).
+  for f in "$TARGET/agents/"massa-ai-*.md; do
+    [[ -f "$f" ]] || continue
+    [[ -f "$ACTIVE_AGENTS_SRC/$(basename "$f")" ]] && continue
+    rm -f "$f"
+    vecho "  - removed retired specialist $(basename "$f")"
+  done
+
   install_variant_tree
 fi
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@massa-ai/claude-plugin",
-  "version": "1.52.0",
+  "version": "1.54.1",
   "description": "massa-ai plugin for Claude Code — semantic code search, durable memory, symbol graph, and context compression",
   "files": [
     "agents",

package/skills/massa-ai/SKILL.md

@@ -46,7 +46,7 @@ Before reading any massa-ai file:
   Never pass `workflowSessionId` in that field. Use `synapse_task_begin`/`synapse_task_end`
   for task envelopes and `synapse_prefetch` to warm the buffer on file open.
 - Prefer the shared v2 retrieval order; fall back gracefully if the massa-ai
-  server or Synapse is unavailable. The full tool surface includes 54 tools
+  server or Synapse is unavailable. The full tool surface includes 59 tools
   (see `references/mcp-tools.md`): indexing, search, symbol graph
   (`trace_path`, `impact_analysis`, `get_architecture`), memory CRUD
   (`remember`, `recall`, `memory_update`, `memory_delete`), checkpoints

package/skills/massa-ai/references/mcp-tools.md

@@ -1,4 +1,4 @@
-# massa-ai Tool Contracts (54 Tools)
+# massa-ai Tool Contracts (59 Tools)
 
 Load when exact MCP schemas, REST fallbacks, response modes, or
 polling rules are needed. Prefer the active tool declaration over copied
@@ -103,6 +103,8 @@ depends on exact content.
 | `handoff_accept` | Accept an open handoff (open→accepted) | Req: `id`. Opt: `projectId`. |
 | `handoff_cancel` | Cancel/expire an open handoff | Req: `id`. Opt: `projectId`. |
 | `handoff_list_pending` | List open handoffs, oldest-first | Req: `projectId`. Opt: `targetAgent`. |
+| `handoff_update` | Edit targetAgent/summary/openQuestions/nextSteps/files by id | Req: `id`. Opt: `projectId`, `targetAgent`, `summary`, `openQuestions`, `nextSteps`, `files` — at least one editable field required. Unknown/restricted fields (`status`, `acceptedAt`, etc.) are rejected by name. |
+| `handoff_delete` | Hard-delete a handoff, any status | Req: `id`. Opt: `projectId`. |
 
 ## MCP Capability Matrix — Auto-improvement (Proposals)
 
@@ -111,6 +113,9 @@ depends on exact content.
 | `list_proposals` | List pending auto-improvement proposals, newest-first | Req: `projectId`. |
 | `approve_proposal` | Approve a proposal; applies the memory edit | Req: `id`. Opt: `projectId`, `source`. |
 | `reject_proposal` | Reject a proposal (no edit applied) | Req: `id`. Opt: `projectId`, `reason`. |
+| `create_proposal` | Create a pending proposal by hand | Req: `projectId`, `kind` (`memory.create`\|`memory.update`\|`memory.tag`), `payload`. Opt: `rationale`, `targetMemoryId`. `payload` is validated against the same per-kind rules the store enforces on read. |
+| `update_proposal` | Edit rationale/payload by id, any status | Req: `id`. Opt: `projectId`, `rationale`, `payload` — at least one editable field required. `kind`/`targetMemoryId`/`status`/`decidedAt` are immutable. A `payload` edit re-validates against the row's existing `kind`. |
+| `delete_proposal` | Hard-delete a proposal, any status | Req: `id`. Opt: `projectId`. Deleting an approved proposal does not reverse its applied memory edit. |
 
 ## MCP Capability Matrix — Passive Capture