@massa-ai/cursor-plugin 1.52.0 → 1.53.0

package/.cursor-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "massa-ai",
-  "version": "1.52.0",
+  "version": "1.53.0",
   "description": "massa-ai — semantic code search, memory, and context compression for Cursor"
 }

package/install.sh

@@ -325,7 +325,11 @@ install_bundled_skills() {
   fi
 
   local installed=0 name src dest
-  for name in massa-ai persona-router; do
+  # Three harness skills, matching generate-skill-artifacts.ts:138's
+  # authoritative constant (D6/IPT-05) — not derived by scanning the bundle's
+  # skills/ directory, which would install 49 on cursor (every workflow skill
+  # ships as its own directory here).
+  for name in massa-ai persona-router profile; do
     src="$SCRIPT_DIR/skills/$name"
     [[ -d "$src" ]] || continue
     dest="$HARNESS_SKILLS_DIR/$name"
@@ -354,7 +358,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. installRoute (T9) is installer-owned but
 // written by a LATER step of this same install (record_plugin_version), so it
@@ -400,7 +404,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
@@ -617,12 +621,18 @@ fi
 # Flat agents and harness skills are written in BOTH branches (PAU-08/09):
 # Cursor discovers subagents only from the flat directory regardless of which
 # plugin-load path is active, and MCP/harness-skills ownership is independent
-# of it too. Prune-then-copy so a specialist deleted from the bundle cannot
-# linger installed. All of them, navigator included, are generated from
+# of it too. All of them, navigator included, are generated from
 # skills/agents/*/SKILL.md and owned by the massa-ai- name prefix (CRS-04) —
 # user-authored agents are untouched.
+#
+# Copy-then-prune (D1/IPT-02 AC-02.6), not prune-then-copy: this loop copies
+# the current set first, and only afterward sheds destination entries the
+# bundle no longer ships. `set -euo pipefail` is in force, so a mid-loop `cp`
+# failure aborts the script — under the old prune-first order that left the
+# user with fewer agents than before the upgrade (possibly none); under this
+# order the worst case is a retired agent lingering one run longer, which is
+# the pre-fix status quo this feature already tolerates.
 mkdir -p "$CURSOR_AGENTS_DIR"
-rm -f "$CURSOR_AGENTS_DIR/"massa-ai-*.md
 for src in "$SCRIPT_DIR/agents/"massa-ai-*.md; do
   [[ -f "$src" ]] || continue
   name="$(basename "$src")"
@@ -632,6 +642,19 @@ for src in "$SCRIPT_DIR/agents/"massa-ai-*.md; do
 done
 vecho "  + ${specialist_count} subagent specialists (generated from skills/agents/*/SKILL.md)"
 
+# Shed owned members the bundle no longer ships (D2): the removal population
+# is the destination directory; the bundle supplies only the keep-predicate.
+# Loop over the destination, consult the bundle only to decide whether to
+# keep — never loop over the bundle to decide removals. Ownership test is the
+# massa-ai- name prefix (D3), same as the uninstall loop above.
+for f in "$CURSOR_AGENTS_DIR/"massa-ai-*.md; do
+  [[ -f "$f" ]] || continue
+  name="$(basename "$f")"
+  [[ -f "$SCRIPT_DIR/agents/$name" ]] && continue   # keep-list: still shipped
+  rm -f "$f"
+  vecho "  - $name (retired, no longer shipped)"
+done
+
 # Skills bundling (PDO-08, 09): install massa-ai/persona-router into the
 # shared harness skills directory, unless scripts/install-skills.sh already
 # owns it for this platform. Runs in both branches (same reasoning as above).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@massa-ai/cursor-plugin",
-  "version": "1.52.0",
+  "version": "1.53.0",
   "description": "massa-ai plugin for Cursor — semantic code search, memory, 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