@massa-ai/codex-plugin 1.50.0 → 1.52.0

package/skills/agents/builder/SKILL.md

@@ -25,7 +25,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 spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/context-curator/SKILL.md

@@ -26,7 +26,7 @@ Prepare the minimum high-quality Context Packet required for another agent to do
 - Never implement.
 - Never review.
 - Never plan.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/designer/SKILL.md

@@ -26,7 +26,7 @@ Own the screen: verify an existing user-facing screen against its design source,
 - Write only when scoped with a disjoint write set (same constraint as `builder`), and only inside the UI layer: screen, view, component, layout, style, theme, and design-token files. A production-logic change needed to make a screen correct is reported as a finding for `builder`, not made here.
 - Platform, lifecycle, build-system, and offline-sync questions belong to `mobile-specialist`. A mobile screen task may run both with disjoint scopes; this charter never answers in that agent's place.
 - Never claim design conformance that was not checked. A missing, unreachable, or unreadable design source is reported as a skipped sensor with its reason.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/documentation-agent/SKILL.md

@@ -24,7 +24,7 @@ Generate engineering documentation artifacts (README, ADR, RFC, changelog, KDoc,
 ## Restrictions
 - Never modify implementation.
 - Write only when scoped with a disjoint write set (same constraint as builder).
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/furps-analyst/SKILL.md

@@ -25,7 +25,7 @@ Analyze exactly one FURPS+ dimension of a PRD or ADR against its checklist secti
 - Never analyze a dimension other than the assigned one; flag cross-dimension gaps instead of expanding into them.
 - Never write files, never mutate Atlassian issues, never write memory.
 - Never return raw document dumps.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 - Do not use this role for The Fool critique (use `plan-critic`) or for code claims (use `investigator` / `verification-agent`).
 

package/skills/agents/investigator/SKILL.md

@@ -25,7 +25,7 @@ Read and understand the codebase to answer engineering questions without modifyi
 - Never modify code.
 - Never generate implementation.
 - Never perform reviews.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/judge/SKILL.md

@@ -29,7 +29,7 @@ stopped arguing.
 - Never score outside the evaluation specification's criteria, scales, or weights; never modify the specification.
 - Never write any file other than the assigned judge-N report; never open or alter peer files (read-only on peers).
 - Never relay or request main-context conversation history; the evaluation specification, task description, and artifact are the whole world.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/meta-judge/SKILL.md

@@ -27,7 +27,7 @@ their consensus trustworthy.
 - Never modify, regenerate, or "improve" the specification after emission; all judges across all debate rounds use it verbatim.
 - Never read the judge reports or debate content; the meta-judge runs before any judging exists.
 - Never implement, refactor, or run mutating commands.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/mobile-specialist/SKILL.md

@@ -24,7 +24,7 @@ Provide mobile-specific expertise (Android, iOS, KMP) when the workflow detects
 ## Restrictions
 - Refuse non-mobile targets (no `build.gradle`, `Podfile`, `*.kt`, `*.swift`, `ios/`, `android/`).
 - Never implement (read-only guidance only).
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Topics

package/skills/agents/navigator/SKILL.md

@@ -33,7 +33,7 @@ The user's codebase is **already indexed** by massa-ai. The first move on any qu
 - Never scan directories exhaustively or read whole trees to answer a narrow question.
 - Never paste long code; summarize and cite.
 - Never call `reset_project`, `index`, or `reindex`; report the needed reindex to the parent agent instead.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/plan-critic/SKILL.md

@@ -26,7 +26,7 @@ Challenge a plan that already exists so its weakest assumption is exposed before
 - Never implement, refactor, or run mutating commands.
 - Never expand scope beyond the plan packet received.
 - Never request or reconstruct full conversation history.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/planner/SKILL.md

@@ -24,7 +24,7 @@ Transform an engineering request into a structured implementation plan.
 ## Restrictions
 - Never implement.
 - Never review code.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/requirements-analyst/SKILL.md

@@ -24,7 +24,7 @@ Analyze requirements before implementation to surface ambiguity, gaps, contradic
 ## Restrictions
 - Never implement.
 - Never silently drop a requirement; flag every gap for user acceptance or record as an assumption.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/reviewer/SKILL.md

@@ -25,7 +25,7 @@ Review implementation quality by analyzing the diff and flagging bugs, regressio
 - Never implement.
 - Never rewrite files.
 - Never plan features.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/test-engineer/SKILL.md

@@ -26,7 +26,7 @@ Generate a testing strategy that covers unit, integration, edge cases, negative
 - Focus only on testing.
 - No production code changes outside test files.
 - Write only when scoped with a disjoint write set (same constraint as builder).
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/agents/verification-agent/SKILL.md

@@ -24,7 +24,7 @@ Centralize Verification Ladder logic and validate that a task's output meets its
 ## Restrictions
 - Never modify implementation.
 - Never skip a verification level without recording a concrete reason.
-- Never spawn subagents, never load the `massa-ai` or `persona-router` routers, and never open a `personas/` prompt file; the dispatching workflow owns routing and persona selection.
+- 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.
 
 ## Inputs

package/skills/massa-ai/references/agent-orchestration.md

@@ -231,7 +231,7 @@ Use `references/conversation-feedback.md` when subagent lifecycle visibility wou
 
 Use these labels for delegated work:
 
-- `Agent Started` when a role is launched with scope and permission mode.
+- `Agent Started` when a role is launched: name the agent, its model, and its effort (see Model/Effort Announcement below), with scope and permission mode.
 - `Agent Running` when waiting on a long-running role or reporting its current bounded task.
 - `Agent Done` when the role returns usable evidence, findings, implementation, or verification.
 - `Agent Blocked` when the role cannot complete its assigned scope.
@@ -245,6 +245,49 @@ Example:
 🤖 [Agent Done] Verifier found no stale references. Skipped checks: none.
 ```
 
+### Model/Effort Announcement
+
+Every dispatch of any of the 18 massa-ai roster specialists names the agent, its model,
+and its effort in the `Agent Started` line above, inside that line's existing 1-2 line
+budget. No exemption: this covers the three standing dispatch exceptions
+(`plan-critic`, `verification-agent`, `designer`) and spec-driven batch workers exactly
+like every other dispatch.
+
+- **Source**: the *installed* agent file for the active host — never
+  `skills/model-profiles.json`. The installed file reports what the host will actually
+  load, including any local profile-switch overlay the registry cannot see.
+- **Read once per session**, for all 18 agents, and cache the result — not once per
+  dispatch.
+- Absent `effort` in the installed file announces `effort: inherit`. Absent `model`, or
+  `model: inherit`, announces `model: inherit`.
+- A missing or unreadable installed file announces `model/effort unknown`, names the
+  exact attempted path, and the dispatch proceeds — the read never blocks a dispatch.
+
+```md
+🤖 [Agent Started] Investigator — model opus, effort high. Scope: the four emitters.
+🤖 [Agent Started] Designer — model/effort unknown (no installed agent file at
+   ~/.claude/plugins/cache/massa-ai/massa-ai/1.48.0/agents/massa-ai-designer.md). Dispatching anyway.
+```
+
+That second line is a measured case, not a hypothetical: on a machine with plugin
+bundle `1.48.0` installed, `massa-ai-designer.md` is absent because `designer` shipped
+in `1.50.0` — a live instance of the degraded path above.
+
+Per-host installed-agent path, matching `resolveHostLayout` in
+`packages/shared/src/profile-switch/hosts.ts` — a sensor executes that resolver against
+this table so the two cannot drift silently:
+
+| Host | Installed agents directory | Glob | Model / effort keys |
+| --- | --- | --- | --- |
+| Claude — marketplace route | `<marketplaceRoot>/agents` — a *versioned* bundle root, e.g. `~/.claude/plugins/cache/massa-ai/massa-ai/1.48.0/agents` | `massa-ai-*.md` | `model:` / `effort:` |
+| Claude — file route | `~/.claude/agents` | `massa-ai-*.md` | `model:` / `effort:` |
+| Codex | `~/.codex/agents` | `massa-ai-*.toml` | `model` / `model_reasoning_effort` |
+| OpenCode | `~/.config/opencode/agents` | `massa-ai-*.md` | `model:` / `reasoningEffort:` |
+| Cursor | no lookup — `resolveHostLayout` returns route `skip` | — | announce `model: inherit, effort: inherit` for every agent; Cursor publishes no resolvable model IDs |
+
+Claude's active route (`marketplace` vs `file`) comes from `install-state.json`'s
+per-platform `installRoute` field, never guessed from directory presence.
+
 ## Plan-Critic Contract
 
 Dispatch `massa-ai-plan-critic` only after a concrete plan exists. Dispatch it with the capability packet above and the standard output contract. The subagent receives the plan, scope, constraints, compact recalled facts/evidence, selected depth, selected The Fool mode only for full gates, known risks, verification recipe, parent identifiers, and context-firewall limits. It never receives full conversation context.

package/skills/massa-ai/references/code-reuse-scan.md

@@ -42,8 +42,7 @@ implementation code is planned or written:
 > - persona: optional — the active route's cataloged id only, never the persona prompt, passed as advisory framing only — it never overrides the agent's charter Restrictions, scope, or permissions; omit when no persona is routed
 
 Dispatch one subagent per coherent target area; dispatch more than one only
-when the areas are independent enough to scope separately. The subagent
-never spawns further subagents.
+when the areas are independent enough to scope separately.
 
 ## Reuse-Map Output Contract
 

package/skills/massa-ai/references/conversation-feedback.md

@@ -85,6 +85,8 @@ Use `references/context-firewall.md` when raw output is verbose. Feedback should
 
 When a subagent is used, the main agent reports only the role, scope, permission mode, current task, and status. Do not expose raw subagent prompts or internal deliberation.
 
+The `Agent Started` line's model/effort component has one canonical definition — `references/agent-orchestration.md`'s Model/Effort Announcement — not restated here.
+
 Examples:
 
 ```md

package/skills/massa-ai/references/figma-pre-analysis.md

@@ -65,7 +65,6 @@ never in parallel**. For each slice, in the recorded order:
 
 Sequential dispatch is a hard rule, not a tuning choice: it respects Figma MCP
 session/rate limits, and it is what lets slice N+1 reuse what slice N learned.
-Retrieval subagents never spawn further subagents.
 
 WHERE Figma ingestion is enabled per `references/figma-wiring.md`, populate
 each completed slice's Number, Figma node id(s), Category, Explanation, and

package/skills/massa-ai/references/spec-driven/sub-agents.md

@@ -67,7 +67,7 @@ commits in the feature worktree.
 
 **What a batch worker does:**
 
-Executes ALL tasks in its assigned batch **in order** — finishing every task in one phase before starting the next phase in the batch — following the `references/spec-driven/execute.md` cycle for each task (implement → gate → atomic commit). It does NOT spawn further sub-agents. After completing all tasks in the batch, the worker reports a **compact summary** to the orchestrator using the structured return contract:
+Executes ALL tasks in its assigned batch **in order** — finishing every task in one phase before starting the next phase in the batch — following the `references/spec-driven/execute.md` cycle for each task (implement → gate → atomic commit). After completing all tasks in the batch, the worker reports a **compact summary** to the orchestrator using the structured return contract:
 
 ```
 Batch (phases [N]–[M]) return:
@@ -84,7 +84,7 @@ Batch (phases [N]–[M]) return:
 
 No raw logs, no full test output — only the above fields keep the main context clean.
 
-**No nesting:** Batch workers execute their tasks themselves. They never spawn sub-sub-agents. Execution is strictly sequential within and across batches — there is no intra-phase or intra-batch parallelism.
+**Sequential execution:** Batch workers execute their tasks themselves. Execution is strictly sequential within and across batches — there is no intra-phase or intra-batch parallelism.
 
 **Orchestrator context discipline:** the orchestrator consumes only the compact
 summary above. It must never read a worker's transcript, JSONL, or intermediate