@massa-ai/claude-plugin 1.60.1 → 1.62.0

package/agents/test-engineer.md

@@ -0,0 +1,101 @@
+---
+name: test-engineer
+description: Testing agent. Plan unit, integration, edge-case, negative-scenario, and acceptance-coverage tests, run the findings-only tests audit lens, and implement test fixes from a saved tests audit report. Mode is selected by the capability packet (plan, audit, or fix). Audit mode writes nothing; plan mode is read-only unless explicitly scoped to write test files; fix mode writes only test files, always with a disjoint write set. Focuses only on testing; no production code changes outside test files.
+model: sonnet
+effort: high
+---
+<!-- massa-ai-owned: true -->
+# Test Engineer Agent Skill
+
+## Mission
+Make a test suite catch the five distinct error classes it must cover — business-logic errors, code no test touched, hardcoded-example brittleness, built-the-wrong-thing, and drift over time — by planning the tests, auditing the ones that exist, and implementing test fixes.
+
+## Responsibilities
+- Run exactly one mode per dispatch, selected by the packet `mode` field: `plan`, `audit`, or `fix`.
+- Map acceptance coverage to spec criteria.
+- Design variation/property-style test cases — vary inputs beyond the fixture example (bounds, parameter changes) — technique-level, library-neutral.
+
+## Restrictions
+- Unknown `mode`: return `Blocked` naming the valid modes `plan`, `audit`, `fix`; a missing `mode` takes the default in Inputs.
+- Focus only on testing.
+- No production code changes outside test files.
+- Write only in `fix` mode (or `plan` mode when explicitly scoped to write test files), always with a disjoint write set (same constraint as `builder`); `audit` mode writes nothing.
+- Never weaken, skip, or delete an existing test assertion to make a suite pass.
+- Never load the `massa-ai` router skill; the dispatching workflow owns routing.
+
+## Inputs
+- `mode`: `plan` | `audit` | `fix` (defaults to `plan`).
+- `lens`: `audit` mode only — one of `tests` (the single lens this charter runs; optional).
+- `scope`: the feature, module, spec, audit target, or saved-report findings to handle.
+- `inputs`: acceptance criteria, recalled facts, existing test conventions, the saved tests audit report (`fix` mode).
+- `permissions`: read-only default; write test files only when explicitly scoped + disjoint, and never in `audit` mode.
+- `sensors`: test runner commands, coverage tools.
+
+## Modes
+
+### Mode: `plan`
+Testing strategy before or after implementation.
+
+- Define unit test cases for core logic and integration test cases for boundaries.
+- Identify edge cases and negative scenarios.
+- Produce a test plan aligned with acceptance criteria.
+
+Output:
+- Status: Complete | Partial | Blocked
+- Scope: test plan or test files written
+- Evidence: test commands, coverage output, acceptance-criteria mapping
+- Findings: test plan (unit, integration, edge, negative, acceptance)
+- Risks and skipped checks
+- Exact next step
+
+### Mode: `audit`
+Findings-only tests lens: coverage, regression protection, assertion quality, fixture reliability, variation, and missing deterministic sensors in a concrete target. Shares `references/audit-scope.md` (scope rules) and `references/audit-report-io.md` (report format) with every audit lens; per-lens reference `workflows/tests/tests-audit.md`. Read-only; no fix actions are taken.
+
+Output:
+- Status: Complete | Partial | Blocked
+- Scope: area audited + tests lens
+- Evidence: `path:line` pointers, test-run and coverage results
+- Findings: ranked list (severity, location, problem, suggestion) in the project audit-report format
+- Risks and skipped checks
+- Exact next step
+
+### Mode: `fix`
+Implement the confirmed findings of a saved tests audit report inside test files only, per `workflows/tests/tests-fix.md`.
+
+Output:
+- Status: Complete | Partial | Blocked
+- Scope: test files changed, per finding ID
+- Evidence: test commands and results, proof each new or changed test fails without the behavior it guards
+- Findings: per-finding implementation summary
+- Risks and skipped checks
+- Exact next step
+
+## Invocation
+### Use when
+- A workflow needs a test strategy before or after implementation, or acceptance criteria need coverage mapping (`plan`).
+- A workflow needs a findings-only tests audit (`audit`).
+- The `tests-fix` workflow closes saved tests audit findings (`fix`).
+- The user asks for a test plan or test cases.
+
+### Do not use when
+- No acceptance criteria, spec, or audit report exists.
+- The task is a docs-only change with no testable behavior.
+- The fix needs production code changes (route to `builder`).
+
+## massa-ai Integration
+- Context Firewall: summarize test output; return the plan, coverage map, or findings, not raw logs.
+- Verification Ladder: behavioral (tests) and file-integrity (no validation assets weakened).
+- Massa-ai Memory: suggest durable test-pattern memories only when a testing convention is established; main agent persists.
+- Synapse: none (test work is not a repeated-search task).
+- References (paths relative to the `massa-ai` skill directory): `references/verification-ladder.md`, `references/code-annotation.md`, `references/root-cause-scripts.md`, `references/audit-scope.md`, `references/audit-report-io.md`.
+
+## Validation Sensors
+- Every acceptance criterion maps to at least one test case.
+- Edge cases and negative scenarios are enumerated.
+- Test runner commands are named.
+- `audit`: every finding has a `path:line` pointer and follows `references/audit-report-io.md`; no file written.
+- `fix`: the diff stays inside test files and the assigned write set; no validation asset weakened.
+
+## Memory Boundary
+Suggest durable memories only when a reusable testing convention or fixture pattern is established. The main agent persists. Do not persist one-off test plans or audit results.
+

package/commands/{adr.md → create-adr.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow to record a finalized or being-finalized architecture decision; route open options to rfc and implementation planning to tdd. — explicit massa-ai 'adr' workflow"
+description: "Use this workflow to record a finalized or being-finalized architecture decision; route open options to create-rfc and implementation planning to create-tdd. — explicit massa-ai 'create-adr' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `adr`.
+Explicit massa-ai workflow invocation: `create-adr`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `adr` under routing precedence 1 (explicit route) —
+route to workflow `create-adr` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/commands/{to-prd.md → create-prd.md}

@@ -1,13 +1,13 @@
 ---
-description: "Turn the current conversation into a PRD. Use when the user asks to create, synthesize, or convert existing discussion and codebase context into a Product Requirements Document without another interview. Do NOT use for implementation plans, architecture design docs, RFCs, TDDs, or discovery interviews that require new product questioning. — explicit massa-ai 'to-prd' workflow"
+description: "Turn the current conversation into a PRD. Use when the user asks to create, synthesize, or convert existing discussion and codebase context into a Product Requirements Document without another interview. Do NOT use for implementation plans, architecture design docs, RFCs, TDDs, or discovery interviews that require new product questioning. — explicit massa-ai 'create-prd' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `to-prd`.
+Explicit massa-ai workflow invocation: `create-prd`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `to-prd` under routing precedence 1 (explicit route) —
+route to workflow `create-prd` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/commands/{rfc.md → create-rfc.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow when a significant technical, process, product, vendor, tool, or policy decision is still open and stakeholders need a structured proposal before committing. — explicit massa-ai 'rfc' workflow"
+description: "Use this workflow when a significant technical, process, product, vendor, tool, or policy decision is still open and stakeholders need a structured proposal before committing. — explicit massa-ai 'create-rfc' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `rfc`.
+Explicit massa-ai workflow invocation: `create-rfc`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `rfc` under routing precedence 1 (explicit route) —
+route to workflow `create-rfc` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/commands/{tdd.md → create-tdd.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow to write a Technical Design Document once one product direction is selected and no unresolved API, data, security, or rollout decision blocks implementation. — explicit massa-ai 'tdd' workflow"
+description: "Use this workflow to write a Technical Design Document once one product direction is selected and no unresolved API, data, security, or rollout decision blocks implementation. — explicit massa-ai 'create-tdd' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `tdd`.
+Explicit massa-ai workflow invocation: `create-tdd`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `tdd` under routing precedence 1 (explicit route) —
+route to workflow `create-tdd` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/commands/{ticket.md → create-ticket.md}

@@ -1,13 +1,13 @@
 ---
-description: "Use this workflow to draft, review, create, or resume creation of Jira Epics, issues, or sub-tasks through Atlassian MCP, the only tracker and mutation path. — explicit massa-ai 'ticket' workflow"
+description: "Use this workflow to draft, review, create, or resume creation of Jira Epics, issues, or sub-tasks through Atlassian MCP, the only tracker and mutation path. — explicit massa-ai 'create-ticket' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `ticket`.
+Explicit massa-ai workflow invocation: `create-ticket`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `ticket` under routing precedence 1 (explicit route) —
+route to workflow `create-ticket` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/commands/{discovery.md → product-discovery.md}

@@ -1,13 +1,13 @@
 ---
-description: "Product discovery and brainstorming workflow — act as a sharp product thinking partner to explore problem spaces, generate and stress-test ideas, and spar on strategy before anything is spec-ready, ending with a mandatory offer to synthesize the conversation into a PRD via the to-prd workflow. Use when the user wants to brainstorm a product problem, idea, opportunity, or direction with no concrete code target. Do NOT use for codebase understanding (exploration), converting a finished discussion into a PRD (to-prd), or any implementation work. — explicit massa-ai 'discovery' workflow"
+description: "Product discovery and brainstorming workflow — act as a sharp product thinking partner to explore problem spaces, generate and stress-test ideas, and spar on strategy before anything is spec-ready, ending with a mandatory offer to synthesize the conversation into a PRD via the create-prd workflow. Use when the user wants to brainstorm a product problem, idea, opportunity, or direction with no concrete code target. Do NOT use for codebase understanding (exploration), converting a finished discussion into a PRD (create-prd), or any implementation work. — explicit massa-ai 'product-discovery' workflow"
 argument-hint: "[task description]"
 ---
 <!-- massa-ai:generated workflow-command -->
 
-Explicit massa-ai workflow invocation: `discovery`.
+Explicit massa-ai workflow invocation: `product-discovery`.
 
 Load the massa-ai router skill if not already loaded (dedupe guard), then
-route to workflow `discovery` under routing precedence 1 (explicit route) —
+route to workflow `product-discovery` under routing precedence 1 (explicit route) —
 do not reclassify. Pass the following as the task description; if empty,
 the workflow's own intake gathers it.
 

package/hooks/massa-ai-hook.ts

@@ -227,7 +227,7 @@ function readModelLine(filePath: string): string | null {
 
 /**
  * The ≤2-line session-start drift report (agent-runtime-drift): version
- * drift (live bundle vs recorded state), agent drift (active investigator
+ * drift (live bundle vs recorded state), agent drift (active code-reviewer
  * model vs the recorded profile's variant), and the host env override that
  * nullifies every per-agent model at runtime. Null when every recording
  * agrees — silent when healthy. Read-only (INV5); every failure degrades to
@@ -253,13 +253,13 @@ export function buildSessionStartDoctorLine(
 
   const profile = claude?.modelProfile?.profile;
   if (typeof profile === "string" && profile) {
-    const activeModel = readModelLine(path.join(pluginRoot, "agents", "massa-ai-investigator.md"));
+    const activeModel = readModelLine(path.join(pluginRoot, "agents", "code-reviewer.md"));
     const variantModel = readModelLine(
-      path.join(pluginRoot, "agent-profiles", profile, "massa-ai-investigator.md"),
+      path.join(pluginRoot, "agent-profiles", profile, "code-reviewer.md"),
     );
     if (activeModel && variantModel && activeModel !== variantModel) {
       lines.push(
-        `[massa-ai] agent drift: investigator ${activeModel} vs ${profile} variant ${variantModel} — re-run the profile switch`,
+        `[massa-ai] agent drift: code-reviewer ${activeModel} vs ${profile} variant ${variantModel} — re-run the profile switch`,
       );
     }
   }

package/install.sh

@@ -350,7 +350,7 @@ NODE
 # ── Skills bundling (PDO-08, 09 / D3 two-writer ownership) ──────────────────
 # scripts/install-skills.sh remains the single writer once it has already
 # claimed this platform (skillsOwner: "repo" in the shared install-state.json).
-# This plugin installs its bundled massa-ai/persona-router skills into the
+# This plugin installs its bundled massa-ai/profile/bootstrap skills into the
 # SAME harness skills directory (~/.claude/skills, not this plugin's cache)
 # only when that has not happened, mirroring the MCP single-writer precedent
 # (test-mcp-single-writer.sh). A repo checkout's own --apply always takes
@@ -374,6 +374,44 @@ try {
 NODE
 }
 
+# C4: line 1 is the enumerated owner ("plugin" | "none" — never the raw
+# recorded value, so a hostile multi-line skillsOwner cannot smuggle a name
+# into the list); every further line is a harness skill this plugin recorded
+# as installed and no longer ships. The recorded list is the ownership proof,
+# so an unrecorded directory of the same name is never touched.
+plugin_skills_record() {
+  local runner="$1"
+  "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" <<'NODE'
+const fs = require("fs");
+const [, , file, host] = process.argv;
+try {
+  const data = JSON.parse(fs.readFileSync(file, "utf8"));
+  const rec = data && data.platforms && data.platforms[host];
+  const owned = !!rec && rec.skillsOwner === "plugin";
+  const current = ["massa-ai", "profile", "bootstrap"];
+  const retired = owned && Array.isArray(rec.skills)
+    ? rec.skills.filter((s) => typeof s === "string" && /^[a-z0-9][a-z0-9-]*$/.test(s) && !current.includes(s))
+    : [];
+  process.stdout.write([owned ? "plugin" : "none", ...retired].join("\n"));
+} catch {
+  process.stdout.write("none");
+}
+NODE
+}
+
+# Removes every retired name in a plugin_skills_record output. The subshell
+# body scopes `set -f` and a newline-only IFS, so no name is ever
+# glob-expanded or split on a space.
+remove_retired_skills() (
+  set -f
+  IFS=$'\n'
+  state_retired_skills="$(printf '%s\n' "$1" | sed 1d)"
+  for name in $state_retired_skills; do
+    rm -rf "$HARNESS_SKILLS_DIR/$name"
+    vecho "  - removed retired harness skill $HARNESS_SKILLS_DIR/$name"
+  done
+)
+
 install_bundled_skills() {
   local runner=""
   if command -v node &>/dev/null; then runner="node"
@@ -389,7 +427,7 @@ install_bundled_skills() {
   fi
 
   local installed=0 name src dest
-  for name in massa-ai persona-router profile bootstrap; do
+  for name in massa-ai profile bootstrap; do
     src="$SCRIPT_DIR/skills/$name"
     [[ -d "$src" ]] || continue
     dest="$HARNESS_SKILLS_DIR/$name"
@@ -404,6 +442,11 @@ install_bundled_skills() {
   done
   vecho "  + ${installed} harness skills installed to $HARNESS_SKILLS_DIR (plugin-owned)"
 
+  # C4: retired skills go BEFORE the record is rewritten — the recorded list
+  # is the only ownership proof, so a removal that fails (set -e aborts here)
+  # leaves it in place for the next run to retry.
+  remove_retired_skills "$(plugin_skills_record "$runner")"
+
   "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" "$TARGET" <<'NODE'
 const fs = require("fs");
 const path = require("path");
@@ -418,7 +461,8 @@ 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", "profile", "bootstrap"] };
+const current = ["massa-ai", "profile", "bootstrap"];
+data.platforms[host] = { root, skillsOwner: "plugin", skills: current };
 // 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
@@ -448,26 +492,16 @@ uninstall_bundled_skills() {
   else return 0
   fi
 
-  # harness_skills_owner collapses to "repo" | "none"; uninstall only ever
-  # acts on an exact "plugin" record, so query the raw value directly.
-  local raw_owner
-  raw_owner="$("$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" <<'NODE'
-const fs = require("fs");
-const [, , file, host] = process.argv;
-try {
-  const data = JSON.parse(fs.readFileSync(file, "utf8"));
-  const rec = data && data.platforms && data.platforms[host];
-  process.stdout.write(rec ? String(rec.skillsOwner) : "none");
-} catch {
-  process.stdout.write("none");
-}
-NODE
-  )"
-  [[ "$raw_owner" == "plugin" ]] && {
+  # Line 1 of the record is the enumerated owner; uninstall only ever acts on
+  # an exact "plugin" record.
+  local record
+  record="$(plugin_skills_record "$runner")"
+  [[ "${record%%$'\n'*}" == "plugin" ]] && {
     local name
-    for name in massa-ai persona-router profile bootstrap; do
+    for name in massa-ai profile bootstrap; do
       rm -rf "$HARNESS_SKILLS_DIR/$name"
     done
+    remove_retired_skills "$record"
     rmdir "$HARNESS_SKILLS_DIR" 2>/dev/null || true
     echo "  - removed plugin-owned harness skills from $HARNESS_SKILLS_DIR"
   }
@@ -678,16 +712,20 @@ apply_recorded_profile_after_update() {
     return 0
   fi
   mkdir -p "$install_path/agents"
-  for f in "$variant_dir/"massa-ai-*.md; do
+  for f in "$variant_dir/"*.md; do
     [[ -f "$f" ]] || continue
     name="$(basename "$f")"
+    if [[ -e "$install_path/agents/$name" || -L "$install_path/agents/$name" ]] && ! is_owned_agent "$install_path/agents/$name"; then
+      echo "  ⚠ $install_path/agents/$name exists and is not massa-ai-owned — skipped" >&2
+      continue
+    fi
     cp "$f" "$install_path/agents/$name"
     copied=$((copied + 1))
   done
   if [[ "$copied" -gt 0 ]]; then
     vecho "  ↷ re-applied recorded model profile '$profile' (${copied} files) to $install_path/agents"
   else
-    vecho "  ↷ recorded model profile '$profile' variant directory has no massa-ai-*.md files — nothing to re-apply"
+    vecho "  ↷ recorded model profile '$profile' variant directory has no agent files — nothing to re-apply"
   fi
 }
 
@@ -827,13 +865,49 @@ remove_file_route_artifacts() {
     done
   fi
   if [[ -d "$TARGET/agents" ]]; then
-    for src in "$TARGET/agents/"massa-ai-*.md; do
-      [[ -f "$src" ]] || continue
+    for src in "$TARGET/agents/"*.md; do
+      is_owned_agent "$src" || continue
       rm -f "$src"
     done
   fi
 }
 
+# >>> massa-ai agent ownership predicates >>>
+# Byte-identical in every plugin installer and scripts/lib/installer-shared.sh
+# (plugin tarballs cannot source repo-only libs); the TS twin is
+# packages/shared/src/profile-switch/ownership.ts, and
+# scripts/__tests__/agent-ownership-parity.test.ts holds all copies and both
+# languages to identical verdicts. Ownership is a content marker, never a
+# filename; the legacy rule lets an upgrade prune the pre-rename
+# massa-ai-<name> files — exact names only, never an open massa-ai-* glob.
+MASSA_AI_OWNED_MARKER_MD='<!-- massa-ai-owned: true -->'
+MASSA_AI_LEGACY_AGENT_NAMES=" architecture-specialist audit-specialist builder context-curator designer documentation-agent furps-analyst investigator judge meta-judge mobile-specialist navigator plan-critic planner requirements-analyst reviewer test-engineer verification-agent "
+is_legacy_agent() {
+  local b="${1##*/}"
+  b="${b%.*}"
+  [[ "$b" == massa-ai-* && "$MASSA_AI_LEGACY_AGENT_NAMES" == *" ${b#massa-ai-} "* ]]
+}
+has_owned_marker() {
+  awk -v m="$MASSA_AI_OWNED_MARKER_MD" 'NR==1{if($0!="---")exit;next} !c&&$0=="---"{c=1;next} c{ok=($0==m);exit} END{exit !ok}' "$1" 2>/dev/null
+}
+is_owned_agent() {
+  [[ -f "$1" && ! -L "$1" ]] || return 1
+  is_legacy_agent "$1" || has_owned_marker "$1"
+}
+is_owned_agent_toml() {
+  [[ -f "$1" && ! -L "$1" ]] || return 1
+  [[ "$(head -n1 "$1")" == "# massa-ai-owned" ]]
+}
+is_owned_agent_link() {
+  [[ -L "$1" ]] || return 1
+  is_legacy_agent "$1" && return 0
+  local b="${1##*/}" t
+  t="$(readlink "$1")"
+  [[ "$t" == */opencode-plugin/agents/"$b" || "$t" == */plugins/massa-ai/agent-profiles/*/"$b" ]] && return 0
+  [[ -f "$1" ]] && has_owned_marker "$1"
+}
+# <<< massa-ai agent ownership predicates <<<
+
 # ── Uninstall ───────────────────────────────────────────────────────────────
 if [[ "$UNINSTALL" -eq 1 ]]; then
   echo "Uninstalling massa-ai Claude Code plugin (scope: $SCOPE)..."
@@ -856,15 +930,15 @@ if [[ "$UNINSTALL" -eq 1 ]]; then
     done
     echo "  - removed massa-ai-* commands from $TARGET/commands/"
   fi
-  # Remove every massa-ai-owned subagent specialist. All of them are generated
-  # from skills/agents/*/SKILL.md, so the massa-ai- name prefix is the ownership
-  # marker; user agents without that prefix are untouched.
+  # Remove every massa-ai-owned subagent specialist: the body marker, or a
+  # legacy massa-ai-<name> file (is_owned_agent). A user's own agent, even
+  # one named like a massa-ai agent, is untouched.
   if [[ -d "$TARGET/agents" ]]; then
-    for src in "$TARGET/agents/"massa-ai-*.md; do
-      [[ -f "$src" ]] || continue
+    for src in "$TARGET/agents/"*.md; do
+      is_owned_agent "$src" || continue
       rm -f "$src"
     done
-    echo "  - removed massa-ai-* subagent specialists from $TARGET/agents/"
+    echo "  - removed massa-ai-owned subagent specialists from $TARGET/agents/"
   fi
   echo ""
   echo "Done. User hooks, keys, and non-massa-ai agents preserved."
@@ -892,7 +966,7 @@ if [[ "$PLUGIN_ROUTE" -eq 1 ]]; then
   for src in "$SCRIPT_DIR/commands/"*.md; do
     [[ -f "$src" ]] && command_count=$((command_count + 1))
   done
-  for src in "$SCRIPT_DIR/agents/"massa-ai-*.md; do
+  for src in "$SCRIPT_DIR/agents/"*.md; do
     [[ -f "$src" ]] && specialist_count=$((specialist_count + 1))
   done
   remove_file_route_artifacts
@@ -925,8 +999,8 @@ else
     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.
+  # Subagent specialists (generated from skills/agents/*/SKILL.md). Each carries the body ownership marker used by prune and
+  # uninstall; a same-named file the user owns is skipped, never overwritten.
   #
   # Model-profile re-apply (T8, MPS-04): if a switch previously recorded a
   # profile for this host, and the bundle ships that profile's variant, the
@@ -951,9 +1025,13 @@ else
     fi
   fi
 
-  for src in "$ACTIVE_AGENTS_SRC/"massa-ai-*.md; do
+  for src in "$ACTIVE_AGENTS_SRC/"*.md; do
     [[ -f "$src" ]] || continue
     name="$(basename "$src")"
+    if [[ -e "$TARGET/agents/$name" || -L "$TARGET/agents/$name" ]] && ! is_owned_agent "$TARGET/agents/$name"; then
+      echo "  ⚠ $TARGET/agents/$name exists and is not massa-ai-owned — skipped" >&2
+      continue
+    fi
     cp "$src" "$TARGET/agents/$name"
     vecho "  + $name"
     specialist_count=$((specialist_count + 1))
@@ -966,10 +1044,10 @@ else
   # 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
+  # is_owned_agent — so legacy massa-ai-<name> files are pruned on upgrade.
+  for f in "$TARGET/agents/"*.md; do
     [[ -f "$ACTIVE_AGENTS_SRC/$(basename "$f")" ]] && continue
+    is_owned_agent "$f" || continue
     rm -f "$f"
     vecho "  - removed retired specialist $(basename "$f")"
   done
@@ -977,7 +1055,7 @@ else
   install_variant_tree
 fi
 
-# Skills bundling (PDO-08, 09): install massa-ai/persona-router into the
+# Skills bundling (PDO-08, 09): install massa-ai/profile/bootstrap into the
 # shared harness skills directory, unless scripts/install-skills.sh already
 # owns it for this platform.
 vecho ""

package/package.json

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

package/skills/agents/builder/SKILL.md

@@ -4,8 +4,7 @@ description: Write-permitted implementation agent. Implement approved plans by m
 license: MIT
 metadata:
   author: Luiz Massa
-  version: "1.0.0"
-  model_tier: standard
+  version: "1.1.0"
   permission: write
 ---
 
@@ -25,8 +24,7 @@ Implement an approved plan or task by modifying source code with a disjoint writ
 - Never perform reviews.
 - Never generate implementation plans.
 - Never write outside the assigned disjoint write set.
-- Never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
-- A `persona` supplied in the capability packet shapes emphasis only; these Restrictions win on any conflict.
+- Never load the `massa-ai` router skill; the dispatching workflow owns routing.
 
 ## Inputs
 - `scope`: exact files and modules to modify (disjoint write set).
@@ -51,7 +49,7 @@ Implement an approved plan or task by modifying source code with a disjoint writ
 ### Do not use when
 - No plan or task is approved.
 - The write set overlaps another active agent.
-- The task needs architectural decisions (route to architecture-specialist or planner first).
+- The task needs architectural decisions (route to `code-reviewer` in `guide` mode first).
 
 ## massa-ai Integration
 - Context Firewall: summarize diffs and command output; return evidence, not raw dumps.