@massa-ai/codex-plugin 1.56.0 → 1.57.0

package/skills/massa-ai/scripts/size_change.ts

@@ -0,0 +1,227 @@
+#!/usr/bin/env bun
+/**
+ * size_change.ts - deterministic change sizing for the Verification Ladder.
+ *
+ * `references/verification-ladder.md` sizes work by changed files and changed
+ * LOC. Counting those by eye over a `git diff` is exactly the kind of
+ * arithmetic a model gets subtly wrong, and the whole ladder hangs off the
+ * answer. This reads `git diff --numstat` and reports the counts plus the
+ * SIZE FLOOR of the tier. Bun builtins only, zero dependencies, agent-agnostic.
+ *
+ * FLOOR, not tier. Size is only half of the ladder's rule. The other half is
+ * qualitative and invisible to a diff: unclear acceptance criteria, a new
+ * dependency, a migration, an irreversible operation, security/privacy/auth, a
+ * public compatibility surface, a cross-service contract, or an unresolved
+ * architecture decision. Any one of those escalates regardless of how small the
+ * diff is, so this script's answer is a lower bound the agent may raise and must
+ * never lower.
+ *
+ * Boundary reading: the ladder states Standard as "<=10 files or <=500 changed
+ * LOC" and Spec-driven as ">10 files, >500 changed LOC" — read literally, the
+ * two clauses overlap. This resolves the overlap by escalating: anything over
+ * either bound is Spec-driven. That is the safe direction (it over-verifies
+ * rather than under-verifies), and it matches how the rest of the Spec-driven
+ * bullet reads — a list of independent triggers, not a conjunction.
+ *
+ * Changed LOC is added + deleted, which is what the ladder's "changed LOC"
+ * means: a 100-line rewrite is 200 changed LOC, not 0.
+ *
+ * Usage:
+ *   bun skills/massa-ai/scripts/size_change.ts                 # working tree vs HEAD
+ *   bun skills/massa-ai/scripts/size_change.ts --staged        # index vs HEAD
+ *   bun skills/massa-ai/scripts/size_change.ts --range main..HEAD
+ *   bun skills/massa-ai/scripts/size_change.ts --json
+ *
+ * Exit codes: 0 sized, 1 git failure, 2 usage error.
+ */
+
+const USAGE =
+  "usage: size_change.ts [-h] [--staged | --range REV_RANGE] [--json] [--root ROOT]";
+const HELP = `${USAGE}
+
+Size a change set against the Verification Ladder's file/LOC bounds.
+
+options:
+  -h, --help          show this help message and exit
+  --staged            size the index against HEAD (git diff --cached)
+  --range REV_RANGE   size a revision range, e.g. main..HEAD
+  --json              emit a JSON object instead of the text report
+  --root ROOT         run git in this directory (default: cwd)`;
+
+/** The ladder's numeric bounds. Changing one here changes the only place it is encoded. */
+const QUICK_MAX_FILES = 3;
+const QUICK_MAX_LOC = 200;
+const STANDARD_MAX_FILES = 10;
+const STANDARD_MAX_LOC = 500;
+
+type Tier = "quick" | "standard" | "spec-driven";
+
+interface Args {
+  staged: boolean;
+  range: string | null;
+  json: boolean;
+  root: string;
+}
+
+interface FileStat {
+  path: string;
+  added: number;
+  deleted: number;
+  binary: boolean;
+}
+
+interface Sizing {
+  mode: string;
+  files: number;
+  added: number;
+  deleted: number;
+  changedLoc: number;
+  binaryFiles: number;
+  tierFloor: Tier;
+  perFile: FileStat[];
+}
+
+function printUsageError(msg: string): void {
+  process.stderr.write(`${USAGE}\nsize_change.ts: error: ${msg}\n`);
+}
+
+function parseArgs(argv: string[]): Args | null {
+  const args: Args = { staged: false, range: null, json: false, root: "." };
+  for (let i = 0; i < argv.length; i++) {
+    const a = argv[i]!;
+    if (a === "-h" || a === "--help") {
+      console.log(HELP);
+      process.exit(0);
+    } else if (a === "--staged") {
+      args.staged = true;
+    } else if (a === "--json") {
+      args.json = true;
+    } else if (a === "--range" || a === "--root") {
+      if (i + 1 >= argv.length) {
+        printUsageError(`argument ${a}: expected one argument`);
+        return null;
+      }
+      const value = argv[++i]!;
+      if (a === "--range") args.range = value;
+      else args.root = value;
+    } else if (a.startsWith("--range=")) {
+      args.range = a.slice("--range=".length);
+    } else if (a.startsWith("--root=")) {
+      args.root = a.slice("--root=".length);
+    } else {
+      printUsageError(`unrecognized argument: ${a}`);
+      return null;
+    }
+  }
+  if (args.staged && args.range !== null) {
+    printUsageError("--staged and --range are mutually exclusive");
+    return null;
+  }
+  return args;
+}
+
+/** Runs git and returns stdout, or null when git itself failed. */
+function git(root: string, gitArgs: string[]): string | null {
+  const proc = Bun.spawnSync(["git", ...gitArgs], { cwd: root, stdout: "pipe", stderr: "pipe" });
+  if (proc.exitCode !== 0) {
+    process.stderr.write(new TextDecoder().decode(proc.stderr));
+    return null;
+  }
+  return new TextDecoder().decode(proc.stdout);
+}
+
+/**
+ * Parses `git diff --numstat` output.
+ *
+ * A binary file is reported as `-\t-\tpath`: it has no line counts, so it
+ * contributes to the file count and to nothing else. Counting `-` as 0 silently
+ * would make a 40 MB asset look like a no-op change, which is why binaries are
+ * reported separately instead.
+ */
+function parseNumstat(out: string): FileStat[] {
+  const stats: FileStat[] = [];
+  for (const line of out.split("\n")) {
+    if (!line.trim()) continue;
+    const parts = line.split("\t");
+    if (parts.length < 3) continue;
+    const [addedRaw, deletedRaw] = parts;
+    const binary = addedRaw === "-" || deletedRaw === "-";
+    stats.push({
+      // A rename is `old => new`; keep git's own rendering rather than guessing.
+      path: parts.slice(2).join("\t"),
+      added: binary ? 0 : Number(addedRaw),
+      deleted: binary ? 0 : Number(deletedRaw),
+      binary,
+    });
+  }
+  return stats;
+}
+
+/** The ladder's size floor. See the escalating boundary reading in the header. */
+export function tierFloor(files: number, changedLoc: number): Tier {
+  if (files <= QUICK_MAX_FILES && changedLoc <= QUICK_MAX_LOC) return "quick";
+  if (files > STANDARD_MAX_FILES || changedLoc > STANDARD_MAX_LOC) return "spec-driven";
+  return "standard";
+}
+
+function size(args: Args): Sizing | null {
+  const diffArgs = args.range !== null
+    ? ["diff", "--numstat", args.range]
+    : args.staged
+      ? ["diff", "--numstat", "--cached"]
+      : ["diff", "--numstat", "HEAD"];
+  const out = git(args.root, diffArgs);
+  if (out === null) return null;
+
+  const perFile = parseNumstat(out);
+  const added = perFile.reduce((n, f) => n + f.added, 0);
+  const deleted = perFile.reduce((n, f) => n + f.deleted, 0);
+  const changedLoc = added + deleted;
+  return {
+    mode: args.range !== null ? `range ${args.range}` : args.staged ? "staged (index vs HEAD)" : "working tree vs HEAD",
+    files: perFile.length,
+    added,
+    deleted,
+    changedLoc,
+    binaryFiles: perFile.filter((f) => f.binary).length,
+    tierFloor: tierFloor(perFile.length, changedLoc),
+    perFile,
+  };
+}
+
+function report(s: Sizing): void {
+  console.log(`scope:       ${s.mode}`);
+  console.log(`files:       ${s.files}${s.binaryFiles ? ` (${s.binaryFiles} binary, no line counts)` : ""}`);
+  console.log(`changed LOC: ${s.changedLoc} (+${s.added} / -${s.deleted})`);
+  console.log(`tier floor:  ${s.tierFloor}`);
+  console.log("");
+  for (const f of s.perFile) {
+    const counts = f.binary ? "binary" : `+${f.added}/-${f.deleted}`;
+    console.log(`  ${counts.padEnd(12)} ${f.path}`);
+  }
+  console.log("");
+  console.log(
+    "This is a FLOOR. Raise it for unclear acceptance criteria, a new dependency,",
+  );
+  console.log(
+    "a migration, an irreversible operation, security/privacy/auth, public",
+  );
+  console.log(
+    "compatibility, a cross-service contract, or an unresolved architecture",
+  );
+  console.log("decision. Never lower it. See references/verification-ladder.md.");
+}
+
+function main(argv: string[]): number {
+  const args = parseArgs(argv);
+  if (args === null) return 2;
+  const s = size(args);
+  if (s === null) return 1;
+  if (args.json) console.log(JSON.stringify(s, null, 2));
+  else report(s);
+  return 0;
+}
+
+if (import.meta.main) {
+  process.exit(main(process.argv.slice(2)));
+}

package/skills/massa-ai/workflows/architecture/architecture-audit.md

@@ -30,18 +30,7 @@ Findings-only: do not edit code unless the user separately asks for fixes.
    - `references/agent-orchestration.md` only for large scopes, explicit parallel/subagent requests, PR subagent invocation, isolated audit slices, or independent verification of high-impact findings
 3. `recall` -> load ADRs, architecture decisions, known boundaries, coupling patterns, accepted exceptions, project constraints, and prior rejected refactors for the target area.
    - Apply the Memory Freshness Gate from `references/audit-scope.md`; recalled exceptions are leads, not proof.
-4. Establish the investigation scope before proceeding:
-   - Modified files scope: use when the user says modified files, changed files, current changes, uncommitted changes, staged changes, or unstaged changes.
-   - Explicit files/globs scope: use when the user names files, directories, or globs.
-   - Commit range scope: use when the user provides commits/ranges or asks for commits made by me, my branch commits, or architecture issues introduced by branch commits.
-   - Branch comparison scope: use when the user names base/head branches, refs, or a branch diff.
-   - Codebase area scope: use when the user names a path, module, package, bounded context, feature area, architecture question, or glob.
-   - Symbol/class/function scope: use when the user names exported surfaces, classes, functions, adapters, interfaces, or dependency edges.
-   - Feature/flow scope: use when the user names a runtime flow or cross-module feature.
-   - Whole-repo scope: use only when the user explicitly asks for a whole-repo architecture audit.
-   - Implementation parent scope: use only when `workflows/implementation/implementation-audit.md` invokes this workflow with a concrete implementation scope packet.
-   - If the target focus is missing, vague, or too broad, ask for a concrete target from the supported scope types in `references/audit-scope.md`.
-   - Build the shared scope packet from `references/audit-scope.md` and carry it into the report.
+4. Establish the investigation scope: select the scope type and build the shared scope packet per `references/audit-scope.md`, which owns the supported scope types, the ask-when-vague rule, and the packet fields. Carry the packet into the report.
 5. Resolve the selected branch's mechanics (modified files, commit range, codebase area, explicit-files/branch/symbol/feature/whole-repo, or implementation parent scope) per `references/audit-scope.md` (Lens Audit Scope Resolution Procedure, Architecture row of Per-Lens Scope Deltas).
 6. Investigation pass:
    - Call `get_architecture` with `id` (projectId) for the architecture-specific deep map: packages, entry points, routes, hotspots, communities, layers, and opt-in cycles (pass `aspects:["cycles"]` for Tarjan SCC over CALL edges). `get_architecture` differs from `project_map` (general overview: PageRank backbone + symbol counts) — use `get_architecture` for architecture-specific structure, `project_map` for the general overview. Both count as evidence only when the index is fresh for the current repository path and commit/worktree state; otherwise fall back to `search`/`get_references` and record reduced retrieval confidence.
@@ -73,18 +62,15 @@ Findings-only: do not edit code unless the user separately asks for fixes.
 > - output: findings with lens-specific evidence, provisional severity, tradeoff, and what would disprove it
 > - firewall: raw dependency graphs, generated reports, and broad search output summarized, not returned raw
 > - memory: suggest-only; main agent persists accepted constraints/rejected refactors
-> - 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: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
 > - trigger: independent verification of a high-impact architecture finding
 > - scope: the specific finding's claimed evidence and affected boundary/module
-> - permissions: read-only
 > - inputs: the candidate finding, its source evidence, ADRs, accepted exceptions, and the verification suggestion
 > - sensors: deterministic command or artifact check that would falsify the finding
 > - output: confirmed/disproven verdict with evidence; skipped-check reason if the sensor cannot run
 > - firewall: raw logs/snapshots summarized
 > - memory: suggest-only; main agent persists reusable verification recipes
-> - 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
 9. Severity rules (apply the countable threshold first, then the qualitative clause):
    - `critical`: architecture issue likely causes data loss, auth/privacy break, production outage, irreversible corruption, OR affects >10 files; otherwise use the qualitative clause below.
    - `high`: strong coupling with high volatility, boundary violation, dependency inversion break, or shallow module design likely to cause major change friction or regression.

package/skills/massa-ai/workflows/architecture/architecture-fix.md

@@ -82,7 +82,6 @@ Not for findings-only architecture review — route to `workflows/architecture/a
 > - output: implementation summary, commands run, test counts, deviations
 > - firewall: raw diffs/logs summarized
 > - memory: suggest-only; main agent persists reusable architecture patterns
-> - 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: `massa-ai-reviewer`** (role: `reviewer`) — charter `skills/agents/reviewer/SKILL.md`
 > - trigger: implementation of the architecture finding complete, before the verification gate — never optional
@@ -93,20 +92,16 @@ Not for findings-only architecture review — route to `workflows/architecture/a
 > - output: ranked findings, blocking vs advisory; blocking findings become architecture fix items before verification runs
 > - firewall: summarized findings only, never raw diff dumps
 > - memory: suggest-only; main agent persists review outcomes for the architecture fix
-> - fallback: if the subagent is unavailable, run a standalone fresh-eyes review against this output contract and record the skipped-delegation reason
-> - 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: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
 > - trigger: mandatory at Standard+/Spec-driven-sized findings or high/critical severity, per the Independent Verification Mandate in `references/verification-ladder.md`'s Mandatory Verification Fix Gate; Quick-tier findings take the fallback below instead
 > - scope: the fixed finding's dependency direction, seam/adapter shape, tests, imports, and report claim closure
-> - permissions: read-only
 > - inputs: the finding, the applied fix, the verification suggestion, dependency-direction/import-cycle evidence, and validation assets
 > - sensors: deterministic command (targeted tests, import-cycle check, dependency-direction check), report claim closure check; discrimination sensor per `references/discrimination-sensor.md` (mutate the fixed dependency direction, seam, or boundary contract in a scratch worktree)
 > - output: confirmed/disproven closure verdict with evidence, feeding the Fix Closure Report's Independent Verifier column
 > - firewall: raw test output/logs summarized
 > - memory: suggest-only; main agent persists architecture verification outcomes
 > - fallback: if the subagent is unavailable, run a standalone fresh-eyes re-check of the architecture closure evidence against this output contract and record the skipped-delegation reason
-> - 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
 
 11. Verify each completed finding:
    - If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
@@ -114,7 +109,7 @@ Not for findings-only architecture review — route to `workflows/architecture/a
    - Apply the Mandatory Verification Fix Gate from `references/verification-ladder.md`: run the report's Verification Suggestion or an equivalent deterministic command/artifact check for each selected finding or coherent group.
    - Run the sensors at the mandate's own tier gate: dispatch the verification-agent block above at Standard+/Spec-driven size or high/critical severity; a Quick-tier finding runs its fallback fresh-eyes self-check instead — the hop is skippable, the check never is.
    - A surviving mutant on the discrimination sensor marks the finding's Closure Matrix row `blocked` and records a `surviving_mutant` signal via `references/lessons.md`.
-   - The fix→re-verify loop is capped per `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; exhausting it also marks the row `blocked`. That cap counts re-verify cycles across the whole finding and is a different counter from the two-consecutive-failed-fixes breaker in this file's preamble, which fires inside a single edit iteration.
+   - The fix→re-verify loop is capped per `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; exhausting it also marks the row `blocked`.
    - A finding cannot be marked `fixed` when a target-relevant command or artifact check exists but was not attempted; if verification cannot run, mark it `blocked`, `deferred`, or `skipped` with an allowed skipped-check reason.
    - Run the report's verification suggestion when available.
    - Add static checks for dependency direction/import cycles when feasible.
@@ -144,5 +139,3 @@ User asks: "Fix finding ARCH-2 from audits/architecture/2026-06-06 architecture-
 1. Read the specified report and only execute `ARCH-2`.
 2. Preserve unaffected architecture findings for later.
 3. Report evidence for `ARCH-2` closure and residual risks.
-
-<!-- validator anchors: Stage 3 delivery-authorization scope | Independent Verification Exception | surviving_mutant | Bounded Fix→Re-verify Loop | Fix Closure Report Contract | CONCERNS.md is satisfied by citation | graceful degradation preserved -->

package/skills/massa-ai/workflows/bugs/bugs-audit.md

@@ -26,18 +26,7 @@ Findings-only: do not edit code unless the user separately asks for fixes.
    - `references/agent-orchestration.md` only for large scopes, explicit parallel/subagent requests, PR subagent invocation, or independent verification of high-impact findings
 3. `recall` -> load prior bug patterns, known regressions, project constraints, ADRs, fragile flows, and accepted exceptions for the target area.
    - Apply the Memory Freshness Gate from `references/audit-scope.md`; recalled exceptions are leads, not proof.
-4. Establish the investigation scope before proceeding:
-   - Modified files scope: use when the user says modified files, changed files, current changes, uncommitted changes, staged changes, or unstaged changes.
-   - Explicit files/globs scope: use when the user names files, directories, or globs.
-   - Commit range scope: use when the user provides commits/ranges or asks for commits made by me, my branch commits, or bugs introduced by branch commits.
-   - Branch comparison scope: use when the user names base/head branches, refs, or a branch diff.
-   - Codebase area scope: use when the user names a path, module, package, feature area, service, or glob.
-   - Symbol/class/function scope: use when the user names public classes, functions, APIs, handlers, or exported surfaces.
-   - Feature/flow scope: use when the user names a runtime flow, user journey, or feature area.
-   - Whole-repo scope: use only when the user explicitly asks for a whole-repo bug audit.
-   - Implementation parent scope: use only when `workflows/implementation/implementation-audit.md` invokes this workflow with a concrete implementation scope packet.
-   - If the target focus is missing, vague, or too broad, ask for a concrete target from the supported scope types in `references/audit-scope.md`.
-   - Build or accept the shared scope packet from `references/audit-scope.md` and carry it into the report.
+4. Establish the investigation scope: select the scope type and build or accept the shared scope packet per `references/audit-scope.md`, which owns the supported scope types, the ask-when-vague rule, and the packet fields. Carry the packet into the report.
 5. Resolve the selected branch's mechanics (modified files, commit range, codebase area, explicit-files/branch/symbol/feature/whole-repo, or implementation parent scope) per `references/audit-scope.md` (Lens Audit Scope Resolution Procedure, Bugs row of Per-Lens Scope Deltas).
 6. Investigation pass. Dispatch `audit-specialist` per `references/agent-orchestration.md` when the scope justifies an isolated read-only subagent:
 
@@ -50,7 +39,6 @@ Findings-only: do not edit code unless the user separately asks for fixes.
 > - output: findings with bug category, location, evidence, trigger, severity, confidence, simplest fix direction, verification suggestion
 > - firewall: raw diffs/logs/search output summarized, not returned raw
 > - memory: suggest-only; main agent persists reusable bug patterns
-> - 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
 
     - Trace input -> transformation -> output for each suspicious path.
    - Check diffs, surrounding code, callers and callees, tests, config, migrations, schemas, and recalled project patterns.

package/skills/massa-ai/workflows/bugs/bugs-fix.md

@@ -71,7 +71,6 @@ Not for findings-only bug discovery — route to `workflows/bugs/bugs-audit.md`.
 > - output: implementation summary, commands run, test counts, deviations
 > - firewall: raw diffs/logs summarized
 > - memory: suggest-only; main agent persists reusable bug patterns
-> - 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: `massa-ai-reviewer`** (role: `reviewer`) — charter `skills/agents/reviewer/SKILL.md`
 > - trigger: implementation complete, before the verification gate — never optional
@@ -82,20 +81,16 @@ Not for findings-only bug discovery — route to `workflows/bugs/bugs-audit.md`.
 > - output: ranked findings, blocking vs advisory; blocking findings become fix items before verification runs
 > - firewall: summarized findings only, never raw diff dumps
 > - memory: suggest-only; main agent persists
-> - fallback: if the subagent is unavailable, run a standalone fresh-eyes review against this output contract and record the skipped-delegation reason
-> - 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: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
 > - trigger: mandatory at Standard+/Spec-driven bug-fix size or high/critical bug severity, per the Independent Verification Mandate tier gate in `references/verification-ladder.md`
 > - scope: the fixed bug finding's repro path, regression tests, and report claim closure
-> - permissions: read-only
 > - inputs: the bug finding, the applied root-cause fix, the verification suggestion, and validation assets
 > - sensors: deterministic command (repro path, focused regression tests, inspection) and report claim closure; discrimination sensor per `references/discrimination-sensor.md` (the divergence-point fix just applied)
 > - output: confirmed/disproven bug-closure verdict with evidence
 > - firewall: raw repro transcripts and test/log output summarized
 > - memory: suggest-only; main agent persists bug-closure verification outcomes
 > - fallback: if the subagent is unavailable, run a standalone fresh-eyes re-check of the bug-fix closure evidence against this output contract and record the skipped-delegation reason
-> - 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
    - Main agent owns report parsing, prioritization, memory writes, final synthesis, and Evidence Gate.
 
 10. Verify each completed finding:
@@ -106,7 +101,7 @@ Not for findings-only bug discovery — route to `workflows/bugs/bugs-audit.md`.
    - Run the report's verification suggestion when available.
    - The red→green reproduction proves the regression test catches this bug; the discrimination sensor proves that same assertion would also discriminate against a future wrong implementation — complementary, and both required at Standard+.
    - At the tiers named in the verification-agent dispatch's trigger above, run the discrimination sensor per `references/discrimination-sensor.md` against the divergence-point fix; a surviving mutant marks the finding's closure row `blocked` and records the `surviving_mutant` lessons signal even when the reproduction test is green.
-   - The fix→re-verify cycle is capped per `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; this is a separate counter from the two-consecutive-failed-fixes breaker into `references/root-cause-scripts.md` above, which fires inside one iteration and neither consumes nor resets the loop count.
+   - The fix→re-verify cycle is capped per `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop.
    - Run focused regression tests first, then relevant lint/type/build/test commands when feasible.
    - Confirm validation assets were not weakened.
    - Record command/artifact, result, skipped reason or `none`, highest Verification Ladder level reached, validation assets protected, and residual risk.
@@ -131,6 +126,3 @@ User asks: "Fix BUG-2 from audits/bugs/2026-06-07 bugs-audit.md."
 1. Read the specified report and only execute `BUG-2`.
 2. Preserve other bug findings for later.
 3. Report evidence for `BUG-2` closure and residual risks.
-
-<!-- validator anchors: "Independent Verification Exception", "the divergence-point fix just applied", "audits/bugs/<YYYY-MM-DD bugs-fix-closure>.md", "check_fix_closure.ts <closure.md> --family bugs", "The red→green reproduction proves the regression test catches this bug", "Bounded Fix→Re-verify Loop" -->
-

package/skills/massa-ai/workflows/code-quality/code-quality-audit.md

@@ -28,18 +28,7 @@ Findings-only: do not edit code unless the user separately asks for fixes.
    - `references/agent-orchestration.md` only for large scopes, explicit parallel/subagent requests, PR subagent invocation, or independent verification of high-impact findings
 3. `recall` -> load project style rules, ADRs, prior quality decisions, accepted extension points, repeated anti-patterns, and accepted exceptions for the target area.
    - Apply the Memory Freshness Gate from `references/audit-scope.md`; recalled exceptions are leads, not proof.
-4. Establish the investigation scope before proceeding:
-   - Modified files scope: use when the user says modified files, changed files, current changes, uncommitted changes, staged changes, or unstaged changes.
-   - Explicit files/globs scope: use when the user names files, directories, or globs.
-   - Commit range scope: use when the user provides commits/ranges or asks for commits made by me, my branch commits, or quality issues introduced by branch commits.
-   - Branch comparison scope: use when the user names base/head branches, refs, or a branch diff.
-   - Codebase area scope: use when the user names a path, module, package, feature area, service layer, or glob.
-   - Symbol/class/function scope: use when the user names public classes, functions, interfaces, helpers, or exported surfaces.
-   - Feature/flow scope: use when the user names a runtime flow or feature area.
-   - Whole-repo scope: use only when the user explicitly asks for a whole-repo code quality audit.
-   - Implementation parent scope: use only when `workflows/implementation/implementation-audit.md` invokes this workflow with a concrete implementation scope packet.
-   - If the target focus is missing, vague, or too broad, ask for a concrete target from the supported scope types in `references/audit-scope.md`.
-   - Build the shared scope packet from `references/audit-scope.md` and carry it into the report.
+4. Establish the investigation scope: select the scope type and build the shared scope packet per `references/audit-scope.md`, which owns the supported scope types, the ask-when-vague rule, and the packet fields. Carry the packet into the report.
 5. Resolve the selected branch's mechanics (modified files, commit range, codebase area, explicit-files/branch/symbol/feature/whole-repo, or implementation parent scope) per `references/audit-scope.md` (Lens Audit Scope Resolution Procedure, Code Quality row of Per-Lens Scope Deltas).
 6. Input rules:
    - SOLID inputs: non-test source files only.
@@ -64,7 +53,6 @@ Findings-only: do not edit code unless the user separately asks for fixes.
 > - output: findings with smell category, location, evidence, severity, confidence, and simplest fix direction
 > - firewall: raw diffs/logs/search output summarized, not returned raw
 > - memory: suggest-only; main agent persists reusable code-quality patterns
-> - 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
 
     - Do not delegate every check by default; avoid duplicate source reading when one main-agent pass is cheaper.
     - Subagents may suggest memory content, but the main agent decides what durable knowledge to persist.
@@ -76,7 +64,7 @@ Findings-only: do not edit code unless the user separately asks for fixes.
    - Magic values: repeated strings, event names, timeouts, numeric thresholds, status codes.
    - Generic names: `data`, `info`, `result`, `value`, `temp`, `manager`, `handler`, `helper` without useful qualification, using `references/naming-standards.md` to filter conventional short-scope or framework-required names.
    - Long parameter lists: more than 3-4 positional parameters.
-   - File shape: flag multi-subject files (unrelated exported surfaces bundled together) and any file over ~600 lines, regardless of subject count — it crowds out working context for the rest of the task (see `references/coding-guidelines.md` "File shape for agent readers"). Do NOT flag a single-subject file for line count alone below that bound.
+   - File shape: apply the File Shape rule in `references/code-quality-lens.md`.
    - Needlessly indirect code: pass-through wrappers, one-use abstractions, helper layers with no behavior, factories/builders that only hide one constructor call.
    - Speculative surfaces: unused options, future-oriented hooks, extension points with one implementation, exported APIs with no evidence of use.
    - Complexity without payoff: deep nesting, miniature state machines, or polymorphism where a direct branch or data map would preserve clarity.
@@ -84,26 +72,7 @@ Findings-only: do not edit code unless the user separately asks for fixes.
    - Android/KMP Compose recomposition leads: `@Composable`, `remember`, `rememberSaveable`, `derivedStateOf`, `LaunchedEffect`, `DisposableEffect`, `SideEffect`, `produceState`, `snapshotFlow`, `mutableStateOf`, `SnapshotStateList`, stability annotations/config, Compose compiler reports, Compose UI tests, and screenshot tests.
 9. Investigation pass:
    - Use summary/enriched search, symbol tools, and targeted file reads to inspect target modules, semantic hotspots, public classes, interfaces, functions, and exported API surface.
-   - Apply SOLID checks to non-test source only:
-     - Single Responsibility: flag classes/modules bundling distinct concern groups, such as validation plus persistence or formatting plus dispatch, only when separating them yields an externally-findable named unit (locatable by search or grep from outside the file) or measurably reduces change risk — never on concern-count or size alone.
-     - Open/Closed: flag caller-side switches or if/else chains on type tags where adding a variant requires modifying existing files.
-     - Liskov: flag subtypes that throw where the base does not, ignore required methods, or narrow the base contract.
-     - Interface Segregation: flag interfaces that force implementors to define unused methods.
-     - Dependency Inversion: flag hardcoded `new ConcreteType()` inside class bodies where abstraction or injection would be natural.
-   - Apply Clean Code checks to test and non-test source:
-     - Magic values: meaningful bare literals should be named constants, especially repeated strings, timeouts, thresholds, and event names.
-     - Function does more than one thing: split only when the result yields an externally-findable named unit (locatable by search or grep from outside the file) or measurably reduces change risk; never split on size or "more than one thing" alone.
-     - Unqualified generic names: flag vague names without domain or role qualification.
-     - What-comments: flag comments that restate code; keep only why comments for constraints, workarounds, or non-obvious invariants.
-     - Half-finished surfaces: flag exported TODOs, stubs, placeholder returns, and "implement later" code.
-     - Long parameter lists: flag more than 3-4 positional parameters; suggest an options object.
-   - Apply KISS/YAGNI/DRY checks:
-     - KISS: flag abstractions, layers, indirection, or control flow that raise cognitive load without clearly improving readability, correctness, or constraint handling. Call out premature generalization, deep call chains, excessive configuration, and clever patterns that obscure intent. Prefer straightforward, explicit code a new reader can follow end-to-end: inline trivial abstractions, collapse unnecessary layers, choose boring solutions unless complexity is justified (real variability, hard constraints, or measured bottlenecks). When weighing whether to split instead of inline, apply the same discoverability-or-change-risk criterion used for the split lead above.
-     - YAGNI: flag speculative features, extension points, and generic infrastructure with no concrete caller, requirement, or near-term use. Call out "just in case" hooks, over-parameterization, unused toggles, and frameworks introduced ahead of need. Prefer implementing only what current use cases demand, structured to evolve when real requirements appear. Defer generalization until duplication or constraints force it, and remove dead or unused paths aggressively.
-     - DRY: flag duplicated logic, data transformations, or domain rules repeated without a strong reason (e.g., performance isolation or explicit decoupling). Highlight copy-paste patterns, parallel conditionals, and repeated constants that raise maintenance cost or inconsistency risk. Recommend consolidation into a single source of truth when it improves clarity and reduces bugs, but avoid over-abstraction that harms readability or adds indirection for trivial reuse.
-     - Prefer delete, inline, or merge recommendations over replacement abstractions when simpler code preserves behavior.
-     - Require usage evidence before calling a surface unnecessary; if evidence is incomplete, mark the item `suspect`.
-     - Do not recommend ports, adapters, bounded contexts, new service/module boundaries, or VSA migration from this workflow; hand those to architecture-audit.
+   - Apply the SOLID, Clean Code, KISS/YAGNI/DRY and Standing Rules sections of `references/code-quality-lens.md`. Use their Flag-when column here; the Fix-direction column belongs to `workflows/code-quality/code-quality-fix.md` and is not an audit output. Report only what the lens's Split Criterion supports.
    - For Android Jetpack Compose and KMP Compose Multiplatform code, apply recomposition quality checks from `references/mobile-context.md`:
      - Excessive recomposition risk: unstable parameters, mutable collections or mutable models crossing composable boundaries, expensive work in composition, unremembered lambdas/objects, inappropriate `derivedStateOf`, broad state reads, and backwards writes after state reads.
      - Missing recomposition or stale UI risk: non-observable mutation, missing or wrong `remember`/effect keys, stale captured lambdas that need `rememberUpdatedState`, incorrect stability annotations, and risky stability configuration entries that can make UX updates fail to happen.

package/skills/massa-ai/workflows/code-quality/code-quality-fix.md

@@ -54,14 +54,8 @@ Not for findings-only SOLID, Clean Code, KISS, YAGNI, DRY, maintainability, or o
    - Quick: rename, inline, delete unused speculation, extract constant, collapse trivial wrapper, or local parameter-object change.
    - Standard: multi-file consolidation, shared behavior cleanup, public helper contract change, or meaningful test impact; define characterization checks first.
    - Spec-driven: broad redesign, unclear behavior, cross-boundary migration, or user-visible behavior change; pause and route to `workflows/spec-driven.md` or ask for approval.
-8. Apply code quality fixing methods:
-   - SOLID: separate mixed responsibilities only when the split yields an externally-findable named unit (locatable by search or grep from outside the file) or reduces change risk; replace caller-side type switches with polymorphism or data maps only when new variants are real; preserve base contracts; narrow fat interfaces; inject dependencies when hardcoded concretes block testing or substitution.
-   - Clean Code: name domain concepts precisely using `references/naming-standards.md`, replace repeated magic values with named constants, split functions only when the result yields an externally-findable named unit (locatable by search or grep from outside the file) or measurably reduces change risk — never split on size or "more than one thing" alone — remove code-restating comments, finish or delete stubs, and convert long positional parameter lists to options objects when it improves call-site clarity.
-   - KISS: inline shallow helpers, collapse needless layers, choose direct control flow over clever indirection, and remove configuration that hides rather than expresses behavior. When choosing whether to split instead of inline, apply the same discoverability-or-change-risk criterion used for the Clean Code split direction above.
-   - YAGNI: delete unused extension points, future hooks, unused options, one-implementation factories, and speculative public APIs when usage evidence is absent.
-   - DRY: consolidate duplicated domain rules or transformations into one clear source of truth, but avoid abstractions that make trivial duplication harder to read.
-   - AI-slop cleanup: remove generic wrappers, fabricated-looking abstractions, one-call factories, code-restating comments, and unused configurability when current usage evidence does not justify them.
-   - Do not introduce ports, adapters, bounded contexts, new service/module boundaries, or VSA-style folder migration to satisfy a code-quality finding.
+8. Apply the Fix-direction column of `references/code-quality-lens.md` (SOLID, Clean Code, KISS/YAGNI/DRY) plus its Standing Rules, which include the architecture boundary this workflow must not cross. Every extraction decision — and every decision to inline instead — goes through that file's Split Criterion.
+   - Fix only what the audit report confirmed. A lens rule the report did not raise is not an invitation to widen the diff.
 9. Preserve behavior:
    - Run or identify characterization tests before changing behavior-adjacent code.
    - Do not weaken tests, fixtures, snapshots, types, or public contracts to make cleanup pass.
@@ -77,7 +71,6 @@ Not for findings-only SOLID, Clean Code, KISS, YAGNI, DRY, maintainability, or o
 > - output: implementation summary, commands run, test counts, deviations
 > - firewall: raw diffs/logs summarized
 > - memory: suggest-only; main agent persists reusable code-quality patterns
-> - 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: `massa-ai-reviewer`** (role: `reviewer`) — charter `skills/agents/reviewer/SKILL.md`
 > - trigger: implementation of the CQ finding complete, before the verification gate — never optional
@@ -88,20 +81,16 @@ Not for findings-only SOLID, Clean Code, KISS, YAGNI, DRY, maintainability, or o
 > - output: ranked findings, blocking vs advisory; blocking findings become CQ fix items before verification runs
 > - firewall: summarized findings only, never raw diff dumps
 > - memory: suggest-only; main agent persists review outcomes for the code-quality fix
-> - fallback: if the subagent is unavailable, run a standalone fresh-eyes review against this output contract and record the skipped-delegation reason
-> - 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: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
 > - trigger: mandatory per the verification-ladder's Independent Verification Mandate at Standard+/Spec-driven finding size or high/critical severity; at Quick size the subagent hop is skipped and the standalone fresh-eyes check below runs instead
 > - scope: the fixed finding's behavior-preservation claim over the moved/transformed code, its call sites/imports, and report claim closure
-> - permissions: read-only
 > - inputs: the finding, the applied fix, the verification suggestion, and validation assets
 > - sensors: deterministic command (behavior-preservation check, import graph, characterization tests); discrimination sensor per `references/discrimination-sensor.md` (mutate the pre-fix moved/transformed code the behavior-preservation claim protects, never newly introduced code)
 > - output: confirmed/disproven closure verdict with evidence
 > - firewall: raw test output/logs summarized
 > - memory: suggest-only; main agent persists code-quality verification outcomes
 > - fallback: if the subagent is unavailable, run a standalone fresh-eyes re-check of the code-quality closure evidence against this output contract and record the skipped-delegation reason
-> - 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
    - Main agent owns report parsing, prioritization, memory writes, final synthesis, and Evidence Gate.
 
 11. Verify each completed finding:
@@ -116,7 +105,7 @@ Not for findings-only SOLID, Clean Code, KISS, YAGNI, DRY, maintainability, or o
    - Record command/artifact, result, skipped reason or `none`, highest Verification Ladder level reached, validation assets protected, and residual risk.
    - At the same Standard+/Spec-driven-or-high/critical tiers as the Independent Verification Mandate, run the discrimination sensor from `references/discrimination-sensor.md` against the pre-fix moved/transformed code the behavior-preservation claim protects; Quick mechanical transforms (rename, inline, delete) are exempt. A surviving mutant is an unproven preservation claim: strengthen the characterization test or close the row `blocked` and emit the `surviving_mutant` lessons signal — do not mark it `fixed`.
    - When a survivor traces to cross-boundary coupling rather than a weak assertion, route it through this workflow's step 5 reclassification gate (bounded-context/dependency-direction/seam/module-depth invalidity check) to `workflows/architecture/architecture-fix.md` instead of forcing a local fix.
-   - The fix→re-verify cycle is capped per `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; exceeding the cap stops the finding at `Blocked` with evidence preserved. That cap is a separate counter from the two-consecutive-failed-fixes breaker in the preamble above — the breaker fires inside a single iteration and neither consumes nor resets the cap.
+   - The fix→re-verify cycle is capped per `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; exceeding the cap stops the finding at `Blocked` with evidence preserved.
 12. Close out with the Fix Closure Report:
    - Write the Fix Closure Report per `references/audit-report-io.md` (Fix Closure Report Contract) to `audits/code-quality/<YYYY-MM-DD code-quality-fix-closure>.md`, one Closure Matrix row per selected finding.
    - Run `bun skills/massa-ai/scripts/check_fix_closure.ts <closure.md> --family code-quality` before Propose/Evidence Gate; a non-zero exit blocks Propose. If no code-execution tool is available, run the same checks by reading the artifact (graceful degradation preserved).
@@ -134,6 +123,3 @@ User asks: "Use code-quality-fix to fix latest findings for billing services."
 3. Execute confirmed non-suspect findings by severity and behavior risk.
 4. Prefer delete/inline/rename/extract before introducing new abstractions.
 5. Verify behavior and validation assets after each finding group.
-
-<!-- validator anchors: references/discrimination-sensor.md; references/knowledge-verification-chain.md; references/brownfield-mapping.md; Independent Verification Exception; Fix Closure Report Contract; check_fix_closure.ts --family code-quality; Bounded Fix→Re-verify Loop; Stage 3 delivery-authorization scope -->
-

package/skills/massa-ai/workflows/commit.md

@@ -35,15 +35,15 @@ Not for Jira ticket creation, release notes, changelogs, PR descriptions, or his
    - any Markdown basename matching `*-audit.md`
    - If any excluded file is already staged, stop before committing and report the exact paths. Do not unstage user-selected files unless the user explicitly asks.
 7. Never stage everything through a shortcut, never commit all tracked modifications automatically, and never reset, checkout, amend, squash, rebase, or rewrite history unless the user separately requests that exact operation.
-8. Draft the commit message using caveman-commit rules:
-   - Conventional Commits format: `<type>(<scope>): <imperative summary>`, with scope optional.
-   - Type precedence when multiple apply: `fix`, `feat`, `perf`, `refactor`, `test`, `docs`, `build`, `ci`, `style`, `chore`, `revert`. Use `revert` only when the commit's primary purpose is reverting an earlier change.
-   - Subject is imperative, has no trailing period, targets 50 characters when practical, and has hard cap 72 characters including any Jira prefix.
+8. Draft the commit message in Conventional Commits format — `<type>(<scope>): <imperative summary>`, scope optional — then validate it deterministically:
+   - Shape, allowed type, description casing, trailing period, the optional `[<KEY>] ` Jira prefix, and the `!`/`BREAKING CHANGE:` pairing are all checked by `bun skills/massa-ai/scripts/check_commit.ts --message "<msg>"`. Run it on every drafted message. A non-zero exit blocks the commit; fix the message and re-run rather than committing past it.
+   - The script cannot choose between two defensible types, so type precedence stays a judgment call: `fix`, `feat`, `perf`, `refactor`, `test`, `docs`, `build`, `ci`, `style`, `chore`, `revert`. Use `revert` only when the commit's primary purpose is reverting an earlier change.
+   - The script's 72-character check is a warning; treat it as a hard cap including any Jira prefix, and target 50 characters when practical.
    - With a Jira key, prefix the subject exactly as `[<KEY>] `, for example `[SA-142] fix(auth): reject expired tokens`.
-   - Match existing project capitalization after the colon when current history or nearby commits make it clear.
+   - The description after the colon is lowercase — the script errors on an uppercase first letter, so this overrides any surrounding history that capitalizes.
    - Body is required for breaking changes, migrations, security fixes, reverts, linked issues, or rationale not inferable from the diff. Wrap body lines at 72 characters.
    - Do not include AI attribution unless the repository explicitly requires an attribution trailer.
-9. If committing, run the commit with the exact drafted message only after the final staged-path audit report exclusion check passes. If the commit fails, report the exact failure and leave staging untouched.
+9. If committing, run the commit with the exact drafted message only after `check_commit.ts` exits zero and the final staged-path audit report exclusion check passes. If the commit fails, report the exact failure and leave staging untouched.
 10. Complete `references/evidence-gate.md`, including branch key detection result, staged path policy, excluded audit Markdown paths, command outcome, skipped checks, memory outcome, and residual risk.
 
 ## Failure Handling

package/skills/massa-ai/workflows/debug.md

@@ -25,7 +25,7 @@ Before the first repository mutation, load `references/implementation-delivery.m
    - `references/debug-diagnosis-loop.md`
    - `references/mobile-diagnosis.md` when the bug target involves KMP, iOS, Android, native bridges, devices, simulators/emulators, or mobile lifecycle
    - `references/verification-ladder.md` before Quick/Standard/Spec-driven sizing or applying fixes
-   - `references/context-firewall.md` before inspecting logs, traces, snapshots, or generated output that meet its threshold table (a single source/log/doc block >200 lines, >20 KB, or >50 search hits)
+   - `references/context-firewall.md` before inspecting logs, traces, snapshots, or generated output that meet its threshold table
    - `references/lessons.md` when `.specs/lessons.json` exists, to load confirmed project lessons before diagnosis
 3. `recall` → load prior debugging attempts for this entity
 4. IF prior attempts exist:
@@ -76,24 +76,20 @@ Before the first repository mutation, load `references/implementation-delivery.m
 > - output: ranked findings, blocking vs advisory; blocking findings become fix items before verification runs
 > - firewall: summarized findings only, never raw diff dumps
 > - memory: suggest-only; main agent persists
-> - fallback: if the subagent is unavailable, run a standalone fresh-eyes review against this output contract and record the skipped-delegation reason
-> - 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: `massa-ai-verification-agent`** (role: `verification-agent`) — charter `skills/agents/verification-agent/SKILL.md`
 > - trigger: mandatory at Standard+/Spec-driven fix size, per the Independent Verification Mandate tier gate in `references/verification-ladder.md`; a Quick-tier fix takes the fallback below instead
 > - scope: the fixed divergence point from step 13, its reproduction path, and the regression test added in step 14
-> - permissions: read-only
 > - inputs: the root cause, the reproduction evidence, the regression test, and the changed files — not spec acceptance criteria
 > - sensors: re-run of the reproduction/feedback loop confirming the original failure signal no longer reproduces; discrimination sensor per `references/discrimination-sensor.md` (mutate the fixed code; the regression test must kill it)
 > - output: confirmed/disproven root-cause-closure verdict with evidence
 > - firewall: raw reproduction transcripts and logs summarized, never raw dumps
 > - memory: suggest-only; main agent persists debug verification outcomes
 > - fallback: if the subagent is unavailable, run a standalone fresh-eyes re-check of root cause, reproduction, and regression coverage, and record the skipped-delegation reason
-> - 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
 
 15. If verification found a reusable signal (`ac_gap`, `surviving_mutant`, `spec_precision_gap`, `spec_deviation`, `gate_fail`), record it via `references/lessons.md`:
      `bun skills/massa-ai/scripts/lessons.ts --root . add --feature "<slug>" --signal "<signal>" --source "<ref>" --text "<one terse lesson>"`
-     Rerun the original feedback loop, run the verification recipe, and remove temporary instrumentation unless intentionally retained as observability. The fix → re-verify cycle is capped by `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; a reached cap stops the session `Blocked` with the evidence preserved. That cap counts re-verify cycles across the whole symptom and is a separate counter from the two-consecutive-failed-fixes breaker into `references/root-cause-scripts.md` named in this file's preamble — that breaker fires inside a single edit iteration and neither consumes nor resets the re-verify count.
+     Rerun the original feedback loop, run the verification recipe, and remove temporary instrumentation unless intentionally retained as observability. The fix → re-verify cycle is capped by `references/verification-ladder.md`'s Bounded Fix→Re-verify Loop; a reached cap stops the session `Blocked` with the evidence preserved.
 16. Use `references/agent-orchestration.md` for isolated investigation branches; the Standard+ verifier dispatch above is mandated by that reference's Independent Verification Exception, not merely loaded when it improves signal.
 17. IF fix found:
    - Persist the root cause via `remember` as a scored `decision` memory with `memory:semantic`
@@ -134,6 +130,3 @@ User asks: "The login route returns 500 after deploy."
 6. Define the verification recipe: rerun the original route check, add or update regression coverage at the failing seam, and confirm validation assets were not weakened.
 7. If root cause is a missing `DATABASE_URL`, persist via `remember`: a semantic decision memory for the root cause and a procedural pattern memory for the deploy-env verification command.
 8. At Standard+ size, dispatch `massa-ai-verification-agent` to independently re-run the reproduction against the `DATABASE_URL` fix and confirm the regression test kills a mutant on the restored connection check before closing.
-
-<!-- validator anchors: brownfield Minimum Bar gate | references/knowledge-verification-chain.md | prove the coverage discriminates | Dispatch: `massa-ai-verification-agent` | Independent Verification Exception | Bounded Fix→Re-verify Loop | .specs/debug/<slug>/REPORT.md | check_specs_delivered.ts <slug> --kind debug | graceful degradation preserved | references/artifact-persistence.md | ## Failure Handling -->
-