@massa-ai/codex-plugin 1.25.0 → 1.27.0

package/install.sh

@@ -78,6 +78,12 @@ PLUGIN_DIR="$CODEX_DIR/plugins/massa-ai"
 HOOKS_JSON="$CODEX_DIR/hooks.json"
 AGENTS_DIR="$CODEX_DIR/agents"
 
+# Model-profile variant tree (T8, design Component 3 / MPS-04). Source is the
+# bundle's per-profile agent-profiles/<p>/ (sibling of agents/, A5); dest is
+# the engine's own host path table: $CODEX_DIR/massa-ai/agent-profiles/<p>/.
+VARIANTS_SRC="$SCRIPT_DIR/agent-profiles"
+VARIANTS_DEST="$CODEX_DIR/massa-ai/agent-profiles"
+
 # Array-append merge (F5 mitigation): for each of the 6 events, append the
 # massa-ai hook entry to the event's array if no entry with
 # _massaAiOwned: true already exists. Backup before first write. Uses node
@@ -299,10 +305,22 @@ 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"] };
-// The whole-record replace must not drop the plugin version record a previous
-// successful install wrote (R2) — re-attach it.
-if (prev && typeof prev === "object" && !Array.isArray(prev) && prev.plugin && typeof prev.plugin === "object") {
-  data.platforms[host].plugin = prev.plugin;
+// 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
+// a LATER step of this same install (record_plugin_version) — both must
+// survive this earlier whole-record replace or a switched profile / recorded
+// route silently vanishes on the next skills-bundling pass.
+if (prev && typeof prev === "object" && !Array.isArray(prev)) {
+  if (prev.plugin && typeof prev.plugin === "object") {
+    data.platforms[host].plugin = prev.plugin;
+  }
+  if (prev.modelProfile && typeof prev.modelProfile === "object") {
+    data.platforms[host].modelProfile = prev.modelProfile;
+  }
+  if (typeof prev.installRoute === "string") {
+    data.platforms[host].installRoute = prev.installRoute;
+  }
 }
 fs.mkdirSync(path.dirname(file), { recursive: true });
 fs.writeFileSync(file, JSON.stringify(data, null, 2) + "\n");
@@ -376,18 +394,27 @@ record_plugin_version() {
     return 0
   fi
 
-  local version installed_at
+  local version installed_at route
   version="$(sed -n 's/.*"version"[[:space:]]*:[[:space:]]*"\([^"]*\)".*/\1/p' "$SCRIPT_DIR/package.json" | head -n 1)"
   installed_at="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+  # installRoute (T8, design F1): installer-owned, engine-read-only. Unlike
+  # Claude, Codex's plugin/marketplace registration (register_codex_plugin) is
+  # ADDITIVE — it only affects /plugins visibility. The agent TOML files
+  # always land in $AGENTS_DIR regardless of whether that registration
+  # succeeds (see the unconditional copy loop below), so Codex has no
+  # "read in place, no local files" mode the way Claude's marketplace route
+  # does — installRoute is unconditionally "file" here, reflecting the one
+  # install shape Codex agents ever take. Written on EVERY install path.
+  route="file"
 
   # Tolerant of a corrupt/missing state file (rewrites a minimal valid one —
   # AC-8). A record-write failure warns but never fails the install: the next
   # run treats the host as unknown-version and reinstalls.
-  "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" "$CODEX_DIR" "$version" "$installed_at" <<'NODE' || \
+  "$runner" - "$HARNESS_STATE_FILE" "$HARNESS_HOST" "$CODEX_DIR" "$version" "$installed_at" "$route" <<'NODE' || \
     echo "  ⚠ could not record the plugin version — next run will reinstall (unknown version)" >&2
 const fs = require("fs");
 const path = require("path");
-const [, , file, host, root, version, installedAt] = process.argv;
+const [, , file, host, root, version, installedAt, installRoute] = process.argv;
 let data = { version: 2, platforms: {} };
 try {
   const existing = JSON.parse(fs.readFileSync(file, "utf8"));
@@ -404,12 +431,54 @@ const rec =
     ? data.platforms[host]
     : { root, skillsOwner: "plugin", skills: [] };
 rec.plugin = { version, installedAt };
+// installRoute is installer-owned (like plugin above); modelProfile is NEVER
+// written here — the switch engine (packages/shared/src/profile-switch/) is
+// its sole writer, and this installer only ever reads it (see
+// apply_recorded_profile below).
+rec.installRoute = installRoute;
 data.platforms[host] = rec;
 fs.mkdirSync(path.dirname(file), { recursive: true });
 fs.writeFileSync(file, JSON.stringify(data, null, 2) + "\n");
 NODE
 }
 
+# ── Model-profile variant tree + recorded-profile re-apply (T8, MPS-04) ─────
+# Read-side only: this installer never writes platforms[host].modelProfile —
+# see the comment above record_plugin_version's NODE block. It only (a)
+# refreshes the on-disk variant tree so an offline switch has files to copy
+# from, and (b) re-applies a previously recorded profile's active agent set on
+# install/upgrade, so a plugin upgrade never silently reverts a switched
+# profile back to the shipped default.
+install_variant_tree() {
+  [[ -d "$VARIANTS_SRC" ]] || return 0
+  rm -rf "$VARIANTS_DEST"
+  mkdir -p "$VARIANTS_DEST"
+  cp -R "$VARIANTS_SRC/." "$VARIANTS_DEST/"
+  vecho "  + model-profile variant tree refreshed at $VARIANTS_DEST"
+}
+
+# Prints the recorded profile name (platforms[codex].modelProfile.profile), or
+# an empty string when unset/unreadable. Never throws — a corrupt or missing
+# state file just means "no recorded profile", not an install failure.
+recorded_profile() {
+  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 profile =
+    rec && rec.modelProfile && typeof rec.modelProfile.profile === "string"
+      ? rec.modelProfile.profile
+      : "";
+  process.stdout.write(profile);
+} catch {
+  process.stdout.write("");
+}
+NODE
+}
+
 # ── Plugin-registry registration (delegated to the codex CLI) ───────────────
 # The CLI owns config.toml's [marketplaces.*] / [plugins."x@y"] tables and the
 # plugins/cache layout, so it is the only supported way to reach /plugins.
@@ -551,9 +620,33 @@ vecho "  + 6 massa-ai hook events wired (array-append, user hooks preserved)"
 # plugin dir — Codex custom agents load from the config-root agents/ dir, not
 # the plugin dir). Each file carries a "# massa-ai-owned" top comment for
 # scoped uninstall (R3: shared agents dir, user agents preserved).
+#
+# 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
+# ACTIVE set comes from agent-profiles/<profile>/ instead of the shipped
+# default — an upgrade must never silently revert a switched profile.
+# Recorded-but-missing-from-bundle is a loud fallback to the default, never a
+# silent one.
 mkdir -p "$AGENTS_DIR"
+ACTIVE_AGENTS_SRC="$SCRIPT_DIR/agents"
+json_runner=""
+if command -v node &>/dev/null; then json_runner="node"
+elif command -v bun &>/dev/null; then json_runner="bun"
+fi
+if [[ -n "$json_runner" ]]; then
+  RECORDED_PROFILE="$(recorded_profile "$json_runner")"
+  if [[ -n "$RECORDED_PROFILE" ]]; then
+    if [[ -d "$VARIANTS_SRC/$RECORDED_PROFILE" ]]; then
+      ACTIVE_AGENTS_SRC="$VARIANTS_SRC/$RECORDED_PROFILE"
+      echo "  ↷ re-applying recorded model profile '$RECORDED_PROFILE'"
+    else
+      echo "  ⚠ recorded model profile '$RECORDED_PROFILE' is not in this bundle — falling back to the default profile" >&2
+    fi
+  fi
+fi
+
 specialist_count=0
-for src in "$SCRIPT_DIR/agents/"massa-ai-*.toml; do
+for src in "$ACTIVE_AGENTS_SRC/"massa-ai-*.toml; do
   [[ -f "$src" ]] || continue
   name="$(basename "$src")"
   cp "$src" "$AGENTS_DIR/$name"
@@ -562,6 +655,8 @@ for src in "$SCRIPT_DIR/agents/"massa-ai-*.toml; do
 done
 vecho "  + ${specialist_count} subagent specialists (generated from skills/agents/*/SKILL.md)"
 
+install_variant_tree
+
 # 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.

package/package.json

@@ -1,9 +1,10 @@
 {
   "name": "@massa-ai/codex-plugin",
-  "version": "1.25.0",
+  "version": "1.27.0",
   "description": "massa-ai plugin for Codex — semantic code search, memory, and context compression",
   "files": [
     "agents",
+    "agent-profiles",
     "hooks",
     "skills",
     "install.sh",

package/skills/agents/judge/SKILL.md

@@ -4,7 +4,7 @@ description: Read-only debate-panel evaluator for judge-with-debate. Score an ar
 license: MIT
 metadata:
   author: S1LV4, luizgmassa
-  version: "1.0.0"
+  version: "1.1.0"
   model_tier: deep
   permission: read-only
 ---
@@ -83,12 +83,9 @@ next_step: <string>
 - References: `references/agent-orchestration.md`, `references/audit-report-io.md` (Judge With Debate Report Contracts).
 
 ## Model Hint
-This charter's `metadata.model_tier` (`deep`) is the fallback every host runs when dispatch-time
-model selection is unavailable. The `judge-with-debate` workflow additionally requests per-slot
-model diversity at dispatch time on hosts that support it — `workflows/judge-with-debate.md` is
-the single source for the current slot assignments, not this file. When dispatch-time selection
-is unavailable, every slot runs the charter default and the orchestrator records
-`DIVERSITY DEGRADED` per the workflow contract.
+See `references/agent-orchestration.md` (Model Diversity Fallback): `metadata.model_tier`
+(`deep`) is the per-slot fallback; `workflows/judge-with-debate.md` owns the live slot
+assignments.
 
 ## Validation Sensors
 - Every criterion score carries an exact quotation from the artifact.

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

@@ -4,7 +4,7 @@ description: Read-only evaluation-specification author for judge-with-debate. Ge
 license: MIT
 metadata:
   author: S1LV4, luizgmassa
-  version: "1.0.0"
+  version: "1.1.0"
   model_tier: deep
   permission: read-only
 ---
@@ -74,11 +74,8 @@ overall: weighted-mean
 - References: `references/agent-orchestration.md`, `references/audit-report-io.md` (Judge With Debate Report Contracts).
 
 ## Model Hint
-This charter's `metadata.model_tier` (`deep`) is the fallback every host runs when dispatch-time
-model selection is unavailable. The `judge-with-debate` workflow additionally requests a specific
-model for this slot at dispatch time on hosts that support it — `workflows/judge-with-debate.md`
-is the single source for the current assignment, not this file. When dispatch-time selection is
-unavailable, the orchestrator records a diversity warning per the workflow contract.
+See `references/agent-orchestration.md` (Model Diversity Fallback): `metadata.model_tier`
+(`deep`) is the fallback; `workflows/judge-with-debate.md` owns the live model assignment.
 
 ## Validation Sensors
 - Output parses as YAML; weights sum to 1.0 (±0.001); every criterion carries id, name, weight, scale (min 1, max 5), rubric anchors for 1/3/5, and a non-empty checklist.

package/skills/agents/navigator/SKILL.md

@@ -4,7 +4,7 @@ description: Code exploration specialist that leverages the massa-ai semantic in
 license: MIT
 metadata:
   author: S1LV4, luizgmassa
-  version: "1.0.0"
+  version: "1.1.0"
   model_tier: deep
   permission: read-only
   tools: mcp-index
@@ -16,7 +16,7 @@ metadata:
 Answer codebase questions through the massa-ai semantic index, reading files only once the index has narrowed the target to one to three of them.
 
 ## Core Principle
-The user's codebase is **already indexed** by massa-ai. The first move on any question is to query the index, not to read files blindly. File reads are expensive in context; massa-ai index queries are not.
+The user's codebase is **already indexed** by massa-ai. The first move on any question is to query the index, not read files blindly — file reads are expensive in context; massa-ai index queries are not.
 
 ## Responsibilities
 - Resolve the current project: run `pwd`, match the basename against `list_projects`.

package/skills/massa-ai/SKILL.md

@@ -312,22 +312,7 @@ Load only when a selected workflow asks for them:
 
 ## Graceful Degradation
 
-| Failure | Behavior |
-|---|---|
-| `recall` empty | Continue as cold start; do not invent memory. |
-| massa-ai server unavailable | Fall back to focused shell/file reads; keep session concept. |
-| Synapse unavailable | Continue with stateless search. |
-| Synapse prime/access mismatch | Use verified REST fallback or skip that optional step. |
-| index incomplete or stale | Use recall; skip search-dependent steps until ready. Graph tools (`trace_path`, `impact_analysis`, `get_architecture`) fall back to `search`/`get_references`; record reduced retrieval confidence. |
-| no meaningful memory | Say memory was intentionally skipped. |
-| memory write fails | Continue and report the unpersisted insight. |
-| `create_checkpoint` unavailable | Continue with `.specs/` artifact state as fallback. |
-| `handoff_begin` unavailable (`HANDOFFS_ENABLED=false`) | Fall back to `remember` + `.specs/` writes; record skipped handoff-table write. |
-| `bootstrap` unavailable | Proceed with manual `remember` calls. |
-| `compact_snapshot` unavailable | Continue with `compress` + `remember`; record skipped snapshot. |
-| code execution (`execute`/`execute_file`/`batch_execute`) unavailable | Load file into context instead; note the local-dev-only trust model still applies. |
-| `fetch_and_index` unavailable | Use native web fetch + manual indexing or skip external content. |
-| feedback reference unavailable | Continue without feedback lines; do not block the workflow. |
+On any tool/index/MCP failure (server unavailable, index incomplete, Synapse unavailable, `create_checkpoint`/`handoff_begin`/`bootstrap`/`compact_snapshot`/`execute`/`fetch_and_index` unavailable), load and follow `references/graceful-degradation.md` instead of blocking.
 
 ## Completion
 

package/skills/massa-ai/references/adr-authoring.md

@@ -1,6 +1,6 @@
 # ADR Authoring
 
-Use this reference from `workflows/adr.md`. It defines how massa-ai creates Architecture Decision Records without delegating orchestration to another ADR skill.
+Use from `workflows/adr.md`. Defines how massa-ai creates Architecture Decision Records without delegating orchestration to another ADR skill.
 
 ## Core Rule
 
@@ -15,9 +15,9 @@ Route matrix:
 | Direction is selected and implementation architecture/contracts/rollout need a blueprint | TDD |
 | Requirements, design, tasks, and execution all need staged approval | Spec-driven |
 
-Source relevance requires the source to name at least one target, constraint, risk, dependency, public contract, rejected option, decision owner, or rollout/rollback consequence for this ADR. Sources that provide only style or adjacent context are examples, not facts.
+Source relevance requires the source to name at least one target, constraint, risk, dependency, public contract, rejected option, decision owner, or rollout/rollback consequence for this ADR. Sources providing only style or adjacent context are examples, not facts.
 
-Do not guess. Missing source facts become questions, source gaps, or a workflow route change.
+Do not guess — missing source facts become questions, source gaps, or a workflow route change.
 
 ## Source Order
 

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

@@ -1,6 +1,6 @@
 # Agent Orchestration
 
-Use this reference when a workflow benefits from isolated context, parallel work, or independent verification.
+Use when a workflow benefits from isolated context, parallel work, or independent verification.
 
 Load `references/context-firewall.md` first when the delegated work may involve verbose logs, snapshots, generated reports, external research, or broad source inspection.
 
@@ -23,7 +23,7 @@ Subagents do bounded work only. Do not delegate everything.
 
 Tokens are spent once; context shapes every decision that follows. The orchestrator's
 working memory is the asset every rule below protects — delegation exists to keep
-disposable reasoning out of the main thread, not only to parallelize.
+disposable reasoning out of the main thread, not just to parallelize.
 
 - **Never poll a running subagent for status, and never ingest a subagent's raw
   transcript, JSONL, or intermediate reasoning — running or completed.** The
@@ -98,6 +98,21 @@ installed, spawning forbidden by platform policy, or the host returns an unknown
 delegated scope locally against the same output contract, and report the skipped
 delegation with its reason in the Evidence Gate.
 
+## Model Diversity Fallback
+
+Applies to any charter whose `metadata.model_tier` is a fallback and whose
+dispatching workflow additionally requests per-invocation model diversity at
+dispatch time (e.g. `judge` — 3 parallel slots; `meta-judge` — one slot).
+
+- The charter's `metadata.model_tier` is the fallback every host runs when
+  dispatch-time model selection is unavailable.
+- The dispatching workflow (e.g. `workflows/judge-with-debate.md`) is the
+  single source for the current slot/model assignment, not the charter file.
+- When dispatch-time selection is unavailable, every affected slot runs the
+  charter default, and the orchestrator records `DIVERSITY DEGRADED`
+  (multi-slot) or an equivalent diversity warning (single-slot) per the
+  dispatching workflow's own contract.
+
 ## Roles
 
 Use the role names in prompts and memory tags; use the host agent names to

package/skills/massa-ai/references/architecture-coupling-lens.md

@@ -1,6 +1,6 @@
 # Architecture Coupling Lens
 
-Use this detail reference when an architecture audit or execution task needs dependency health, dependency direction, integration cost, or coupling reduction.
+Use when an architecture audit or execution task needs dependency health, dependency direction, integration cost, or coupling reduction.
 
 ## Contents
 

package/skills/massa-ai/references/architecture-deepening-lens.md

@@ -1,6 +1,6 @@
 # Architecture Deepening Lens
 
-Use this detail reference when an architecture audit or execution task needs module depth, seams, adapters, testability, locality, or AI-navigability analysis.
+Use when an architecture audit or execution task needs module depth, seams, adapters, testability, locality, or AI-navigability analysis.
 
 ## Contents
 

package/skills/massa-ai/references/architecture-domain-lens.md

@@ -1,6 +1,6 @@
 # Architecture Domain Lens
 
-Use this detail reference when an architecture audit or execution task needs domain boundaries, bounded contexts, subdomain classification, ubiquitous language, or cohesion analysis.
+Use when an architecture audit or execution task needs domain boundaries, bounded contexts, subdomain classification, ubiquitous language, or cohesion analysis.
 
 ## Contents
 

package/skills/massa-ai/references/architecture-lenses.md

@@ -1,6 +1,6 @@
 # Architecture Lenses
 
-Use this reference for architecture audits, architecture-focused reviews, and refactor planning. It is the shared index and vocabulary guard; load the detail references only when a workflow needs that lens:
+Use for architecture audits, architecture-focused reviews, and refactor planning. Shared index and vocabulary guard; load the detail references only when a workflow needs that lens:
 
 - `references/architecture-domain-lens.md` for bounded contexts, ubiquitous language, subdomain classification, cohesion, and integration patterns.
 - `references/architecture-coupling-lens.md` for dependency graphs, strength/distance/volatility, dependency direction, and contract health.

package/skills/massa-ai/references/audit-report-io.md

@@ -1,6 +1,6 @@
 # Audit Report I/O
 
-Use this reference from audit workflows before writing reports and from execution workflows before report-driven changes.
+Use from audit workflows before writing reports and from execution workflows before report-driven changes.
 
 ## Report Paths
 
@@ -557,10 +557,40 @@ Before editing:
 
 - Verify workflow, project, target, target focus, scope, base/head, and resolved files match the current request.
 - Reinspect each finding's current location and evidence. Stop or re-audit when schema v2 drift rules invalidate any selected finding.
-- Verify every finding has common and workflow-specific fields plus the correct ID form.
+- Verify every finding has common and workflow-specific fields plus the correct ID form (deterministic backing below).
 - For implementation reports, require source-qualified IDs and child-lens fields.
 - For mobile Figma reports, re-read the Figma node and reject stale design/source/configuration evidence.
 - Ignore ruled-out candidates, skipped checks, no-finding summaries, `NOT EVALUATED` rows, constraint deviations, and low-confidence suspects unless the user explicitly changes scope after revalidation.
 - Build verification from report suggestions plus current project sensors.
 
 Do not execute from chat summaries, inline comments, screenshots alone, or remembered audit content. The saved markdown report is the source of truth.
+
+## Deterministic Validation
+
+`skills/massa-ai/scripts/validate_audit_report.ts` replaces the model-run
+metadata/ID checklist with a scripted check, run before any `*-fix` workflow
+edits code:
+
+```bash
+bun skills/massa-ai/scripts/validate_audit_report.ts <path-to-report.md> --family <family>
+```
+
+`--family` is one of `architecture`, `bugs`, `code-quality`, `security`,
+`requirements`, `tests`, `maestro`, `mobile-figma`, or `implementation`
+(auto-detected from the report's `Workflow:` field when omitted). It checks:
+
+- required freshness-header metadata fields for that family (common fields
+  plus family-specific extras — `Requirements Source` for single-lens and
+  implementation reports; `Scenario Source`/`Maestro CLI`/`Device/Emulator
+  Readiness` for Maestro; the mobile Figma identity fields for Mobile Figma)
+- finding-ID format (`PREFIX-N`, or `<Area>/<PREFIX>-N` for the
+  implementation composite family)
+- Area<->Prefix table membership for implementation reports (rejects an
+  unrecognized Area, a mismatched Area/Prefix pair, and any raw `SONAR-*`
+  executable ID)
+- finding-ID uniqueness and gap-free per-prefix/per-area sequencing
+
+A non-zero exit blocks editing. The script does **not** re-check drift
+against current source, table-structure presence (Target Surface Matrix,
+Maestro Run Matrix, etc.), or Figma-node freshness — those stay a manual
+step per the "Before editing" list above.

package/skills/massa-ai/references/audit-scope.md

@@ -1,6 +1,6 @@
 # Audit Scope
 
-Use this reference from audit workflows, implementation audit, bug finder, mobile Figma, and execution workflows before inspecting changed code or selecting an audit report.
+Use from audit workflows, implementation audit, bug finder, mobile Figma, and execution workflows before inspecting changed code or selecting an audit report.
 
 ## Scope Packets
 
@@ -64,6 +64,27 @@ Use the smallest scope type that matches the user's target:
 - Feature/flow: map entry points through main transformations and side effects; ask for a narrower flow when the feature spans too many unrelated surfaces.
 - Implementation parent scope: accept the exact packet supplied by `workflows/implementation/implementation-audit.md`, including PR diff when that is the selected scope type; child lenses must not broaden it without parent approval.
 
+## Lens Audit Scope Resolution Procedure
+
+Use this procedure in `bugs-audit`, `architecture-audit`, `code-quality-audit`, `requirements-audit`, `security-audit`, and `tests-audit` once each workflow's own step 4 has selected one of the 5 resolution branches below from its trigger list (modified files, commit range, codebase area, explicit-files/globs/branch-comparison/symbol/feature/whole-repo, or implementation-parent scope). This is the single home for the mechanical resolution steps; each lens workflow keeps only its branch-name trigger list and a pointer here.
+
+- **Modified files**: include staged and unstaged tracked files from the working tree, plus untracked non-generated source/test/fixture/schema/config/docs files only when they can affect the lens's evidence (see Per-Lens Scope Deltas for the exact affect-scope and deleted-file-breakage wording per lens). Exclude generated, dependency, build, log, cache, temporary, and secret paths per repo rules. Inspect diffs first, then only the surrounding evidence the lens needs.
+- **Commit range**: use the user-supplied explicit commits/range when given. For "commits made by me", resolve author identity from `git config user.email`, falling back to `git config user.name` when empty, and review only branch-unique commits by that identity. For branch-relative commit scopes, resolve the base with `Branch, Commit, And PR Diff Resolution` below. Ask the user for any missing range/identity/base before proceeding. Inspect the changed files and diffs from those commits, then the lens-specific evidence named in Per-Lens Scope Deltas.
+- **Codebase area**: require a concrete path, module, package, feature area, or glob; ask when missing. Follow `references/codebase-investigation.md`'s retrieval order to find the lens-specific targets in Per-Lens Scope Deltas. Map only top-level modules first and recommend a narrower pass when scope is broad.
+- **Explicit files/globs, branch comparison, symbol/class/function, feature/flow, or explicitly requested whole-repo scope**: resolve the target here and record the resolution method, base/head when relevant, resolved files, exclusions, requirements source when applicable, and freshness timestamp. For symbol/class/function targets, inspect definitions, references, callers, tests, and config plus the lens's extra targets, only as needed to verify a candidate finding. For feature/flow targets, map entry points through the lens-specific transformations named in Per-Lens Scope Deltas. For whole-repo scope, map the lens's first-pass surface (Per-Lens Scope Deltas) and report skipped-depth checks rather than implying exhaustive coverage.
+- **Implementation parent scope**: accept the exact scope packet from `implementation-audit`; do not broaden beyond resolved files, surrounding code, and the lens-specific evidence in Per-Lens Scope Deltas needed to verify the lens's claim. Return compact lens findings to the parent implementation audit; do not write broad project memories unless explicitly assigned.
+
+### Per-Lens Scope Deltas
+
+| Lens (workflow) | Commit-range trigger phrase | Modified-files affect-scope + deleted-file breakage extras | Codebase-area retrieval targets | Symbol/class/function extra targets | Feature/flow mapping focus | Whole-repo first pass | Implementation-parent extra evidence |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| Architecture (`architecture-audit`) | architecture issues introduced by branch commits | architecture contracts or module boundaries; deletion also breaks architecture contracts | target modules, entry points, exported surfaces, references, semantic hotspots, tests, adjacent config | exported surfaces, references, dependency direction, callers, tests, ADRs | entry points through main transformations, contracts, side effects | top-level modules | exported surfaces, references, config, tests, ADRs |
+| Bugs (`bugs-audit`) | bugs introduced by branch commits | runtime or validation behavior; deletion breaks imports, exports, routing, migrations, config, tests, or packaging | entry points, public API, tests, adjacent config | callers, callees, tests, contracts, config | input -> transformation -> output through the named flow | high-risk entry points | callers, callees, tests, config, migrations, schemas, public contracts |
+| Code Quality (`code-quality-audit`) | quality issues introduced by branch commits | maintainability, validation behavior, or public contracts; deletion breaks imports, exports, routing, migrations, config, tests, or packaging | target modules, semantic hotspots, public API, tests, adjacent config | references, call sites, tests, current usage evidence | main code path only as far as needed for maintainability/overengineering | sampled/top-level coverage | public API, tests, config, project patterns |
+| Requirements (`requirements-audit`) | requirement drift introduced by branch commits | required behavior; deletion also breaks required behavior or documentation contracts | entry points, public API, tests, config, docs, acceptance criteria | call paths, public contracts, tests, config, docs, requirement links | expected behavior from the requirements source to implementation, tests, docs, contracts | top-level requirement areas | public contracts, tests, config, docs, requirements |
+| Security (`security-audit`) | security issues introduced by branch commits | runtime or validation behavior; deletion also breaks secrets handling or policy enforcement | entry points, trust boundaries, policy checks, validators, tests, adjacent config | call paths, trust boundaries, validators, policies, tests, config, schemas | untrusted input, identity, authorization, validation, persistence, side effects, logs | major trust boundaries | called auth/validation helpers, config, schemas, tests |
+| Tests (`tests-audit`) | test gaps introduced by branch commits | runtime, validation, or test behavior; deletion also breaks test coverage | production entry points, tests, fixtures, mocks, test commands, coverage-sensitive config | call paths, behavior contracts, tests, fixtures, mocks, test commands | changed or targeted behavior mapped to existing tests and deterministic harnesses | major test surfaces | nearby tests, fixtures, config, callers |
+
 ## Branch, Commit, And PR Diff Resolution
 
 Use this order:

package/skills/massa-ai/references/code-annotation.md

@@ -1,7 +1,7 @@
 # Code Annotation And Test Coverage
 
-Use this reference in every implementation workflow, before writing or editing
-source. It defines the three things every created or updated unit of code owes
+Use in every implementation workflow, before writing or editing
+source. Defines the three things every created or updated unit of code owes
 the next reader: an API doc block, a rationale comment, and a test.
 
 ## Principle
@@ -46,7 +46,7 @@ Rules:
 
 ## 2. Rationale Comment
 
-Doc blocks describe the contract. They do not explain why the code changed. Add
+Doc blocks describe the contract, not why the code changed. Add
 a rationale block once at the changed unit — the class, the method, or the
 enclosing block — not on every line.
 
@@ -108,8 +108,8 @@ Rules:
 
 Data models and anemic domain models carry state, not behavior. A unit test
 that constructs them and asserts their own getters, setters, fields, or
-constructor defaults mirrors the implementation and cannot detect that the
-model is wrong — it is the "test that mirrors the code" anti-pattern from the
+constructor defaults mirrors the implementation and cannot detect the
+model is wrong — the "test that mirrors the code" anti-pattern from the
 rule above. **Do not write unit tests for these kinds:**
 
 - **Data models** — persistence-layer entities: ORM-mapped classes, database

package/skills/massa-ai/references/codebase-investigation.md

@@ -1,6 +1,6 @@
 # Codebase Investigation
 
-Use this reference when understanding unfamiliar code before planning, fixing, reviewing, or refactoring.
+Use when understanding unfamiliar code before planning, fixing, reviewing, or refactoring.
 
 ## Golden Rules
 

package/skills/massa-ai/references/context-firewall.md

@@ -1,6 +1,6 @@
 # Context Firewall
 
-Use this reference before loading raw artifacts >200 lines, >20 KB, >50 search hits, generated reports, logs, screenshots, browser snapshots, CSVs, external research, or any source batch likely to exceed the next decision's needs.
+Use before loading raw artifacts >200 lines, >20 KB, >50 search hits, generated reports, logs, screenshots, browser snapshots, CSVs, external research, or any source batch likely to exceed the next decision's needs.
 
 ## Principle
 
@@ -56,6 +56,7 @@ The main agent receives only:
 
 Subagents should not return raw dumps. Never poll a running subagent for status and never read a subagent transcript — the returned output contract is the only channel back into the main context (canonical rules: `references/agent-orchestration.md`, Orchestrator Working Memory). The main agent still owns memory recall, persistence, synthesis, and the final Evidence Gate.
 
+
 ## Persistence Boundary
 
 `massa-ai` remains the canonical memory layer for massa-ai workflows. Do not introduce `.notebook/`, SQLite, generated state files, or new persistence systems unless a separate workflow explicitly requires them.

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

@@ -1,6 +1,6 @@
 # Conversation Feedback
 
-Use this reference when a massa-ai workflow needs chat-visible status updates for routing, loading, memory, NotebookLM, subagents, divergences, errors, verification, or completion.
+Use when a massa-ai workflow needs chat-visible status updates for routing, loading, memory, NotebookLM, subagents, divergences, errors, verification, or completion.
 
 ## Principle
 

package/skills/massa-ai/references/debug-diagnosis-loop.md

@@ -1,6 +1,6 @@
 # Debug Diagnosis Loop
 
-Use this reference when `workflows/debug.md` asks for an evidence-first diagnosis loop.
+Use when `workflows/debug.md` asks for an evidence-first diagnosis loop.
 
 ## Principle
 

package/skills/massa-ai/references/decision-engine.md

@@ -1,6 +1,6 @@
 # Decision Engine Reference
 
-Load this when scoring memories, making a trade-off decision, or debugging with
+Load when scoring memories, making a trade-off decision, or debugging with
 prior attempts. Do not load for simple edits where no memory write or design
 decision is needed.
 

package/skills/massa-ai/references/evidence-gate.md

@@ -18,7 +18,7 @@ A completion report must include:
 
 Completion reports must also state that tests, specs, fixtures, snapshots,
 schemas, public contracts, and validator checks were not weakened unless the
-user explicitly requested a validation-asset change.
+user explicitly requested it.
 
 ## Acceptable Evidence
 

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

@@ -1,6 +1,6 @@
 # Figma Pre-Analysis And Sequential Retrieval
 
-Load this reference whenever a workflow receives one or more Figma links, node
+Load whenever a workflow receives one or more Figma links, node
 IDs, or a readable desktop selection as a design source — the Figma audit/fix
 family (`mobile-figma-audit`, `mobile-figma-fix`), `design`, and the
 design-source gates of implementation workflows (`feature`, `spec-driven`).
@@ -14,14 +14,14 @@ restate it.
 
 Full Figma extraction on unscoped links overloads one context with mixed
 screens, buries feature boundaries, and makes evidence non-attributable. A
-cheap pre-analysis pass first maps what the links contain, so each retrieval
+cheap pre-analysis pass maps what the links contain first, so each retrieval
 pass reads one coherent slice.
 
 ## Stage 1 — Pre-Analysis (always first, exactly one subagent)
 
 Dispatch one read-only subagent (investigator-class; Figma MCP — Model Context
 Protocol — access, no repository mutation) over the user-provided Figma links.
-Its job is understanding, **not** extraction:
+Its job: understanding, **not** extraction:
 
 - Summarize composition: pages, screens, frames, component sets, shared tokens.
 - Summarize product context: what the screens are for, the features they serve,

package/skills/massa-ai/references/furps/analyst-role.md

@@ -2,7 +2,7 @@
 
 Reusable sub-agent role for `workflows/refinement/furps-refinement.md`. Charter follows `references/subagent-design.md`. Registered in `references/agent-orchestration.md`.
 
-Purpose: analyze exactly one FURPS+ dimension (F, U, R, P, S, or X) of a PRD/ADR against its checklist section and return structured refinement findings.
+Purpose: analyze exactly one FURPS+ dimension (F, U, R, P, S, or X) of a PRD/ADR against its checklist section, returning structured refinement findings.
 
 Trigger description:
 - Use when the `furps-refinement` workflow fans out per-dimension analysis and needs isolated context plus independent verification per dimension.

package/skills/massa-ai/references/furps/checklist.md

@@ -1,6 +1,6 @@
 # FURPS+ Refinement Checklist
 
-Use this reference from `workflows/refinement/furps-refinement.md` when analyzing a PRD and/or ADR against the FURPS+ quality model. One `furps-analyst` sub-agent loads only its assigned dimension section; the main agent loads the full file only when synthesizing or when no dimension split is used.
+Use from `workflows/refinement/furps-refinement.md` when analyzing a PRD and/or ADR against the FURPS+ quality model. One `furps-analyst` sub-agent loads only its assigned dimension section; the main agent loads the full file only when synthesizing or when no dimension split is used.
 
 ## Source
 

package/skills/massa-ai/references/furps/intake.md

@@ -1,6 +1,6 @@
 # FURPS+ Refinement Intake & Sub-agent Packet Contract
 
-Use this reference from `workflows/refinement/furps-refinement.md` during intake and before dispatching sub-agents. It defines source detection, DoR sourcing, the context-firewall, the bounded document packet, and the sub-agent packet contracts.
+Use from `workflows/refinement/furps-refinement.md` during intake and before dispatching sub-agents. Defines source detection, DoR sourcing, the context-firewall, the bounded document packet, and the sub-agent packet contracts.
 
 ## Source-type detection
 

package/skills/massa-ai/references/furps/report-contract.md

@@ -1,6 +1,6 @@
 # FURPS+ Refinement Report Contract
 
-Use this reference from `workflows/refinement/furps-refinement.md` before writing the final report. It extends the shared `references/audit-report-io.md` single-lens contract with FURPS-specific sections and the required refinement outputs (open questions, suggestions, insights, risks, DoR coverage gaps).
+Use from `workflows/refinement/furps-refinement.md` before writing the final report. Extends the shared `references/audit-report-io.md` single-lens contract with FURPS-specific sections and the required refinement outputs (open questions, suggestions, insights, risks, DoR coverage gaps).
 
 ## Report path