vibe-coding-master 0.7.30 → 0.7.31

package/dist/backend/services/gate-review-service.js

@@ -1,6 +1,6 @@
 import { createHash, randomUUID } from "node:crypto";
 import path from "node:path";
-import { CODE_DIFF_SOURCES, GATE_REVIEW_GATES } from "../../shared/types/gate-review.js";
+import { CODE_DIFF_FINDING_SCOPES, CODE_DIFF_SOURCES, GATE_REVIEW_GATES } from "../../shared/types/gate-review.js";
 import { checkMarkdownArtifact } from "../../shared/validation/artifact-check.js";
 import { VcmError } from "../errors.js";
 import { resolveRepoPath } from "../adapters/filesystem.js";
@@ -38,6 +38,7 @@ const VALIDATION_ANALYSIS_FIELDS = [
     "Boundary And Failure Coverage",
     "Public Contract Coverage",
     "Test Integrity",
+    "Test Infrastructure",
     "Skips And Gaps",
     "User Approval And Gap Disposition",
     "Validation Readiness"
@@ -91,6 +92,7 @@ const CORE_INPUT_ARTIFACTS = {
     "validation-adequacy": ".ai/vcm/handoffs/test-report.md"
 };
 const VALID_SEVERITIES = new Set(["critical", "high", "medium", "low"]);
+const VALID_CODE_DIFF_FINDING_SCOPES = new Set(CODE_DIFF_FINDING_SCOPES);
 export function createGateReviewService(deps) {
     const now = deps.now ?? (() => new Date().toISOString());
     const reportPollIntervalMs = deps.reportPollIntervalMs ?? DEFAULT_REPORT_POLL_INTERVAL_MS;
@@ -1067,11 +1069,18 @@ async function readValidationReportError(fs, taskRepoRoot) {
     const absolutePath = resolveRepoPath(taskRepoRoot, relativePath);
     const content = await fs.pathExists(absolutePath) ? await fs.readText(absolutePath) : null;
     const check = checkMarkdownArtifact("test-report", relativePath, content);
-    if (check.status === "ok") {
-        return undefined;
+    if (check.status !== "ok") {
+        return `${relativePath} is incomplete and cannot start validation-adequacy review. `
+            + formatValidationArtifactFailure(check, content);
+    }
+    const infrastructureStatus = matchField(extractMarkdownSection(content ?? "", "Test Infrastructure") ?? "", "Status");
+    if (infrastructureStatus === "repair-required") {
+        return `${relativePath} cannot start validation-adequacy review while Test Infrastructure Status is repair-required. Route Tester repair first.`;
+    }
+    if (infrastructureStatus === "production-change-required") {
+        return `${relativePath} cannot start validation-adequacy review while Test Infrastructure Status is production-change-required. Route the active flow's implementation-failure branch first.`;
     }
-    return `${relativePath} is incomplete and cannot start validation-adequacy review. `
-        + formatValidationArtifactFailure(check, content);
+    return undefined;
 }
 async function readCodeDiffPrerequisiteError(deps, context, index) {
     const reportError = await readValidationReportError(deps.fs, context.taskRepoRoot);
@@ -1367,11 +1376,13 @@ function validateRequestChangeFindings(findings) {
     }
 }
 function validateCodeDiffFindings(findings) {
-    const incomplete = findings.find((finding) => !finding.file?.trim() || !finding.location?.trim());
+    const incomplete = findings.find((finding) => (!finding.file?.trim()
+        || !finding.location?.trim()
+        || !finding.scope));
     if (incomplete) {
         throw new VcmError({
             code: "GATE_REVIEW_CODE_DIFF_FINDING_LOCATION_MISSING",
-            message: `Code-diff finding ${incomplete.title} must contain File and Line Or Symbol.`,
+            message: `Code-diff finding ${incomplete.title} must contain File, Line Or Symbol, and Finding Scope.`,
             statusCode: 500
         });
     }
@@ -1465,6 +1476,7 @@ function extractFindings(content) {
             file: matchField(block, "file"),
             line: parsePositiveInteger(matchField(block, "line")),
             location: matchField(block, "line or symbol"),
+            scope: normalizeCodeDiffFindingScope(matchField(block, "finding scope")),
             evidence: matchField(block, "evidence") ?? "",
             expected: matchField(block, "expected") ?? "",
             gap: matchField(block, "gap") ?? "",
@@ -1527,6 +1539,12 @@ function normalizeSeverity(value) {
         ? normalized
         : undefined;
 }
+function normalizeCodeDiffFindingScope(value) {
+    const normalized = typeof value === "string" ? value.toLowerCase() : "";
+    return VALID_CODE_DIFF_FINDING_SCOPES.has(normalized)
+        ? normalized
+        : undefined;
+}
 function normalizeCallbackStatus(value) {
     return value === "not_sent" || value === "sent" || value === "skipped" || value === "failed"
         ? value

package/dist/backend/templates/handoff.js

@@ -1,4 +1,4 @@
-import { ARCHITECTURE_BRIEF_STATUSES, ARCHITECTURE_PLAN_RESULTS, DOCS_SYNC_DECISIONS, FINAL_ACCEPTANCE_DECISIONS, L3_ACTIONS, L3_REQUIRED_VALUES, STRICT_NONE_VALUE, TEST_RESULTS, renderArtifactOptions } from "../../shared/validation/artifact-contract.js";
+import { ARCHITECTURE_BRIEF_STATUSES, ARCHITECTURE_PLAN_RESULTS, DOCS_SYNC_DECISIONS, FINAL_ACCEPTANCE_DECISIONS, L3_ACTIONS, L3_REQUIRED_VALUES, STRICT_NONE_VALUE, TEST_INFRASTRUCTURE_STATUSES, TEST_RESULTS, renderArtifactOptions } from "../../shared/validation/artifact-contract.js";
 export function renderArchitectureBriefTemplate(taskSlug) {
     return `# Architecture Brief: ${taskSlug}
 
@@ -201,6 +201,26 @@ TBD
 
 TBD
 
+## Test Infrastructure
+
+Status: ${renderArtifactOptions(TEST_INFRASTRUCTURE_STATUSES)}
+
+### Affected Files
+
+${STRICT_NONE_VALUE}
+
+### Boundary Evidence
+
+${STRICT_NONE_VALUE}
+
+### Defect-Class Sweep
+
+${STRICT_NONE_VALUE}
+
+### Repair Commit
+
+${STRICT_NONE_VALUE}
+
 ## Failed Expectations
 
 ${STRICT_NONE_VALUE}

package/dist/backend/templates/harness/gate-review.js

@@ -185,6 +185,14 @@ when they are relevant to the changed behavior. Check that tests were not
 weakened, over-mocked, tied only to fixture values or implementation details,
 or made green by bypassing the real behavior path.
 
+Inspect the \`Test Infrastructure\` section of \`test-report.md\`. A report with
+\`repair-required\` or \`production-change-required\` is not gate-ready. When
+status is \`repaired\`, verify the affected files remain Tester-owned, the
+boundary evidence excludes production or shared changes, the defect-class sweep
+covers the affected test-infrastructure family, the repair commit exists in the
+current range, and required clean-state validation was rerun. Request changes
+for missing, contradictory, incomplete, weakened, or unverified repair evidence.
+
 Do not approve only because \`Test Result: pass\` or all recorded commands are
 green. Request changes when the report is incomplete or inconsistent with the
 actual tests, validation level does not match risk, an important behavior has
@@ -239,6 +247,13 @@ scaffold, and coder completion evidence. Verify that the complete planned
 behavior is implemented without changing architect-owned boundaries or
 contracts.
 
+When the range contains Tester-authored changes recorded in \`test-report.md\`,
+review those tests, fixtures, test-only helpers, and \`docs/TESTING.md\` against
+the Tester role, the repair or coverage evidence, and
+\`docs/CODING_STANDARDS.md\`. Do not reject a valid Tester-owned change merely
+because it is not a Coder scaffold item. Verify that Tester changes remain
+test-only, preserve real behavior paths, and are committed and validated.
+
 For \`architect-debug\`, compare the commits with the current Architect route
 command and \`.ai/vcm/handoffs/architect-debug.md\`. Verify that the confirmed
 root cause is supported by the code, the implementation fixes that cause rather
@@ -319,6 +334,7 @@ Use this findings structure:
 - Boundary And Failure Coverage:
 - Public Contract Coverage:
 - Test Integrity:
+- Test Infrastructure:
 - Skips And Gaps:
 - User Approval And Gap Disposition:
 - Validation Readiness:
@@ -344,6 +360,8 @@ Use this findings structure:
 <!-- File and Line Or Symbol are required for code-diff findings. -->
 - File:
 - Line Or Symbol:
+<!-- Finding Scope is required for code-diff findings. Use test-only only when correction needs no production, runtime, public-contract, dependency, generated-context, architecture, or shared-production change. -->
+- Finding Scope: test-only|implementation
 - Evidence:
 - Expected:
 - Gap:
@@ -382,6 +400,7 @@ If there are no findings, write:
 - Boundary And Failure Coverage:
 - Public Contract Coverage:
 - Test Integrity:
+- Test Infrastructure:
 - Skips And Gaps:
 - User Approval And Gap Disposition:
 - Validation Readiness:

package/dist/backend/templates/harness/project-manager-agent.js

@@ -93,9 +93,11 @@ PM may leave this path only through the allowed branches below.
 - **Coder Continuation:** If Coder returns \`Decision: incomplete\`, lacks the required completion artifact, or has not completed implementation and L0/L1 validation, route Coder again — this is the only route for an in-progress sweep. Problems recorded inside an incomplete report are sweep state, not routable failures; PM routes problems onward only from a post-sweep \`failed\` report carrying the consolidated per-item disposition.
 - **Coder Failure Debug:** If Coder returns \`Decision: failed\` with compile, typecheck, or L0/L1 failure evidence after implementation, suspend the main flow and enter Architect Debug Branch.
 - **Tester Continuation:** If Tester returns \`Test Result: incomplete\`, route Tester again to continue the recorded remaining validation. Do not enter Debug, Diagnosis, or validation-adequacy Gate Review.
-- **Tester Failure:** If Tester returns \`Test Result: fail\` for the original Coder implementation, enter Architect Debug Branch.
-- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the report to Tester, then rerun the validation-adequacy Gate after Tester updates the tests or test report.
-- **Code-Diff Correction:** If the code-diff Gate returns \`request_changes\`, suspend the main flow and enter Architect Debug Branch with the Gate report.
+- **Tester Test-Infrastructure Repair:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: repair-required\`, route Tester to repair and commit the confined test-infrastructure defect, rerun required validation, and replace \`test-report.md\`. Do not enter Architect Debug while this Tester-owned repair remains available.
+- **Tester Failure:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: none\`, \`repaired\`, or \`production-change-required\`, suspend the main flow and enter Architect Debug Branch.
+- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the complete report to Tester. Tester must correct the tests or evidence, rerun required validation, commit tracked Tester-owned changes, and replace \`test-report.md\` before PM reruns the Gate. If corrected validation returns \`fail\`, apply Tester Test-Infrastructure Repair or Tester Failure from that result.
+- **Tester Code-Diff Correction:** If every code-diff finding has \`Finding Scope: test-only\`, route the complete report to Tester. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source coder\`.
+- **Code-Diff Correction:** If any code-diff finding has \`Finding Scope: implementation\`, suspend the main flow and enter Architect Debug Branch with the complete Gate report.
 - **Docs Sync Correction:** \`Decision: synced\` or \`unchanged\` continues to Final Acceptance. \`Decision: blocked\` remains at docs sync unless the report identifies an allowed Debug, Diagnosis, or user-decision branch.
 - **Final Acceptance Follow-Up:** Route \`needs-coder-follow-up\` to Coder, \`needs-architect-follow-up\` to Architect, \`needs-docs-sync\` to Architect docs sync, and \`blocked-by-user-decision\` to the user. After follow-up work, resume from the earliest affected Code-Change Flow step and repeat every downstream Gate.
 - **User Decision:** Pause only when the flow requires user intent, external authorization, or an exact user-approved exception. Resume from the suspended step after the user's decision is recorded.
@@ -116,7 +118,7 @@ The flow completes only when Final Acceptance returns:
 - Route user-originated or flow-required architecture, scope, contract, dependency, public surface, durable docs, and implementation-plan questions to Architect.
 - Do not treat Coder architecture doubts, design concerns, scaffold objections, or validation predictions as architecture questions.
 - Route validation strategy, test coverage, test-report, and validation adequacy questions to Tester.
-- Route bugs, build/runtime errors, and failing validation from a code-delivery flow to Architect Debug Mode according to the active flow. Do not route a Validation-Only Flow \`Test Result: fail\` to Debug unless the accepted outcome requires implementation repair.
+- Route bugs, build/runtime errors, and production-implementation validation failures from a code-delivery flow to Architect Debug Mode according to the active flow. Route a confined \`repair-required\` test-infrastructure failure back to Tester. Do not route a Validation-Only Flow \`Test Result: fail\` to Debug unless the accepted outcome requires implementation repair.
 - Ask the user only when user intent, priority, approval, external authorization, secrets, real cost, production permission, sensitive data access, or durable-doc conflict requires user decision.
 - Non-PM role results, blockers, findings, and requests must come back to PM. PM decides the next route.
 - Only PM decides the next VCM route, gate, pause, retry, final acceptance, or PR-Preparation Flow step. Non-PM role messages are evidence and status only; any requested next action from a non-PM role is advisory and must be reclassified by PM against the active flow, required artifacts, gate state, and PM routing rules.
@@ -134,6 +136,7 @@ Every branch must end in exactly one of these outcomes:
 
 - return to the recorded main-flow resume point
 - repeat the current responsible role
+- route to Tester for an explicitly allowed test-only repair or correction
 - route to Architect Debug Mode
 - route to Architecture Diagnosis Mode
 - pause for user decision
@@ -152,9 +155,11 @@ The shared path is:
 
 - **Normal Plan Required:** If Architect returns \`normal architecture plan required\`, enter Code-Change Flow at Architect planning. When Debug is a branch of Code-Change Flow, resume that parent flow at Architect planning.
 - **Tester Continuation:** If Tester returns \`Test Result: incomplete\`, route Tester again to continue the recorded remaining validation.
-- **Architecture Diagnosis:** If Tester returns \`Test Result: fail\`, enter Architecture Diagnosis Branch.
-- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the report to Tester, then rerun the validation-adequacy Gate after Tester updates the tests or test report.
-- **Code-Diff Revision:** If the code-diff Gate returns \`request_changes\`, route the report to Architect Debug Mode. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source architect-debug\`.
+- **Tester Test-Infrastructure Repair:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: repair-required\`, route Tester to repair and commit the confined test-infrastructure defect, rerun required validation, and replace \`test-report.md\`.
+- **Architecture Diagnosis:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: none\`, \`repaired\`, or \`production-change-required\`, enter Architecture Diagnosis Branch.
+- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the complete report to Tester. After Tester corrects tests or evidence, reruns validation, commits tracked Tester-owned changes, and replaces \`test-report.md\`, rerun the Gate.
+- **Tester Code-Diff Correction:** If every code-diff finding has \`Finding Scope: test-only\`, route the complete report to Tester. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source architect-debug\`.
+- **Code-Diff Revision:** If any code-diff finding has \`Finding Scope: implementation\`, route the complete report to Architect Debug Mode. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source architect-debug\`.
 
 #### Successful Exit
 
@@ -183,9 +188,11 @@ Architecture Diagnosis Mode must run before another Debug Mode fix or Coder disp
 #### Allowed Branches
 
 - **Tester Continuation:** If Tester returns \`Test Result: incomplete\`, route Tester again to continue the recorded remaining validation.
-- **Tester Failure:** If Tester returns \`Test Result: fail\` for the Diagnosis implementation, pause and report to the user. If required validation remains unavailable, ask whether the user explicitly approves retaining that exact Coverage Gap.
-- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the report to Tester, then rerun the validation-adequacy Gate after Tester updates the tests or test report.
-- **Code-Diff Revision:** If the code-diff Gate returns \`request_changes\`, route the report to Architecture Diagnosis Mode. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source architect-diagnosis\`.
+- **Tester Test-Infrastructure Repair:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: repair-required\`, route Tester to repair and commit the confined test-infrastructure defect, rerun required validation, and replace \`test-report.md\`.
+- **Tester Failure:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: none\`, \`repaired\`, or \`production-change-required\`, pause and report to the user. If required validation remains unavailable, ask whether the user explicitly approves retaining that exact Coverage Gap.
+- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the complete report to Tester. After Tester corrects tests or evidence, reruns validation, commits tracked Tester-owned changes, and replaces \`test-report.md\`, rerun the Gate.
+- **Tester Code-Diff Correction:** If every code-diff finding has \`Finding Scope: test-only\`, route the complete report to Tester. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source architect-diagnosis\`.
+- **Code-Diff Revision:** If any code-diff finding has \`Finding Scope: implementation\`, route the complete report to Architecture Diagnosis Mode. After correction, repeat Tester validation, validation-adequacy Gate, and \`code-diff --source architect-diagnosis\`.
 
 #### Successful Exit
 
@@ -258,7 +265,8 @@ PM may leave this path only through the allowed branches below.
 #### Allowed Branches
 
 - **Tester Continuation:** If Tester returns \`Test Result: incomplete\`, route Tester again to continue the recorded remaining validation.
-- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the report to Tester and rerun the Gate after correction.
+- **Tester Test-Infrastructure Repair:** If Tester returns \`Test Result: fail\` with \`Test Infrastructure Status: repair-required\`, route Tester to repair and commit the confined defect, rerun required validation, and replace \`test-report.md\`.
+- **Validation Revision:** If the validation-adequacy Gate returns \`request_changes\`, route the complete report to Tester and rerun the Gate after Tester corrects tests or evidence, reruns validation, commits tracked Tester-owned changes, and replaces \`test-report.md\`.
 - **Code Change Required:** If the accepted outcome requires production-code, runtime-behavior, public-contract, dependency, or system-architecture changes, enter Code-Change Flow at Architect planning.
 - **User Decision:** If validation requires missing user intent, credentials, environment access, sensitive data, real cost, or external authorization, pause and ask the user.
 
@@ -335,11 +343,11 @@ PM may lightly rewrite the user's words to:
 
 - Gate Review requests are mandatory and unconditional. At every trigger point, use the \`vcm-gate-review\` skill to run \`.ai/tools/request-gate-review\` with the matching gate and code source arguments without first judging whether Gate Review is enabled. The tool (via VCM) is the single source of truth for enable state; never skip the run because you assume Gate Review is off or because the worktree has no gate-review index yet.
 - The tool's first output line decides the next step: \`disabled\`, \`not_required\`, or \`already_approved\` continue the normal VCM flow; \`started\` or \`running\` stop the turn and wait for the VCM callback; \`failed_to_start\` is a hard stop — report it to the user and do not silently proceed past the gate.
-- Trigger points (run each unconditionally): after the architecture brief is confirmed and Architect completes planning, before coder dispatch run \`architecture-plan\`; after Tester returns a terminal \`Test Result: pass|fail\` that the active flow permits to reach the gate, run \`validation-adequacy\`; after that validation-adequacy Gate completes successfully, run \`code-diff --source coder\` for Coder implementation, \`code-diff --source architect-debug\` for an Architect Debug fix, or \`code-diff --source architect-diagnosis\` for an Architecture Diagnosis fix. Validation-Only Flow stops after validation-adequacy and does not run code-diff. Never run either post-implementation Gate for \`Test Result: incomplete\`.
+- Trigger points (run each unconditionally): after the architecture brief is confirmed and Architect completes planning, before coder dispatch run \`architecture-plan\`; after Tester returns a terminal \`Test Result: pass|fail\` that the active flow permits to reach the gate, run \`validation-adequacy\`; after that validation-adequacy Gate completes successfully, run \`code-diff --source coder\` for Coder implementation, \`code-diff --source architect-debug\` for an Architect Debug fix, or \`code-diff --source architect-diagnosis\` for an Architecture Diagnosis fix. A test report with \`Test Infrastructure Status: repair-required\` or \`production-change-required\` does not reach a Gate; route the matching allowed branch first. Validation-Only Flow stops after validation-adequacy and does not run code-diff. Never run either post-implementation Gate for \`Test Result: incomplete\`.
 - PM does not inspect commits or decide whether code changes exist. At a \`code-diff\` trigger point, run the tool; the tool decides \`disabled\`, \`not_required\`, \`already_approved\`, or starts review.
 - Do not run \`code-diff\` before Tester completes, while validation-adequacy is unresolved, or for incomplete, unresolved failed, planning-only, Docs-Only Flow, Validation-Only Flow, PR-Preparation Flow, or Communication-Only Flow. A terminal \`fail\` with the exact required user-approved testing gap may proceed only through the recorded validation-adequacy disposition.
 - Gate Review trigger points apply only when the active delivery flow reaches that milestone. Do not run Gate Review for Communication-Only Flow.
-- On a callback, accept only \`approve\` or \`request_changes\`. Apply \`request_changes\` through the allowed branch defined by the active flow; in Code-Change Flow use Architecture Plan Revision, Code-Diff Correction, or Validation Revision according to the gate.
+- On a callback, accept only \`approve\` or \`request_changes\`. Apply \`request_changes\` through the allowed branch defined by the active flow; for code-diff, use Tester Code-Diff Correction only when every finding is \`test-only\`, otherwise use the flow's Architect correction branch.
 - Do not ask Reviewer to choose owners, fixes, Replan, or user-intervention needs.
 - Record gate decision, report path, and any skip or override reason.
 

package/dist/backend/templates/harness/tester-agent.js

@@ -9,7 +9,7 @@ ${renderRoleMemoryRules("tester")}
 
 - Own independent validation, tester-owned test design, test implementation, test adequacy, \`docs/TESTING.md\`, and final validation confidence.
 - Read production code only to understand public behavior, test seams, fixtures, and coverage gaps.
-- Do not edit production code, decide architecture, or diagnose fixes beyond validation evidence.
+- Do not edit production code or decide architecture. Diagnose and repair only PM-routed defects confined to Tester-owned tests, fixtures, test-only helpers, and \`docs/TESTING.md\`; otherwise report validation evidence without proposing a fix.
 
 ### Inputs
 
@@ -40,7 +40,7 @@ ${renderRoleMemoryRules("tester")}
 - If project-manager asks for clarification, clarify only the validation evidence, expected behavior, affected path, or coverage gap.
 - If validation fails or expected behavior is unclear, report the evidence to project-manager; architect owns diagnosis, and project-manager decides the next route.
 - After Architect Debug or Architecture Diagnosis changes, rerun the required validation independently. Architect validation is implementation evidence and does not replace Tester final validation.
-- Add or modify tests, test fixtures, or test-only helpers needed for validation confidence.
+- Add or modify tests, test fixtures, or test-only helpers needed for correct, reliable validation and approved behavior coverage.
 - Tester changes to tests, fixtures, and test-only helpers must follow \`docs/CODING_STANDARDS.md\` and prove the approved behavior contract.
 - Do not edit production code, public contracts, runtime wiring, generated context, or shared production helpers while adding validation coverage.
 - Do not weaken assertions, reshape fixtures to match the current implementation, bypass real behavior paths, skip tests, or add test-only shortcuts.
@@ -57,6 +57,16 @@ ${renderRoleMemoryRules("tester")}
 - A required check that fails, is skipped, or cannot be completed by Tester continuation is a blocking validation issue and requires \`Test Result: fail\`.
 - Update \`docs/TESTING.md\` when validation strategy, commands, level mapping, integration/E2E case definitions, selection rules, final-validation cleanup, test gaps, or test expectations change.
 
+### Test-Infrastructure Repair
+
+- Use this repair path only when project-manager routes a reported test-infrastructure defect back to Tester.
+- The repair must remain confined to tests, fixtures, test-only helpers, or \`docs/TESTING.md\`. It must not change production code, runtime behavior, public contracts, dependencies, generated context, system architecture, or shared production helpers.
+- Confirm the defect mechanism from current files and reproducible evidence. In the affected test-infrastructure family, inspect every occurrence of the same mechanism and repair every confirmed instance.
+- Do not replace a repair with a workaround that bypasses the defective path, weakens assertions, skips validation, or hides the failure.
+- After repair, perform the required clean-state validation again and replace \`test-report.md\` with current results.
+- If the repair requires any prohibited production or shared scope, do not make that change. Record \`Test Infrastructure Status: production-change-required\` and the concrete boundary evidence for project-manager.
+- A current validation path with an unresolved test-infrastructure defect cannot return \`Test Result: pass\`.
+
 ### Mandatory L3 End-To-End Coverage
 
 L3 validates a complete externally observable flow from a project-defined
@@ -126,7 +136,27 @@ Coverage Gap.
 
 ### Outputs
 
-- Write \`.ai/vcm/handoffs/test-report.md\` with \`Test Result: pass|fail|incomplete\`, evidence reviewed, tests added or updated, coverage mapping, validation progress, commands run or checked, validation results, failed expectations, reproduction steps, skipped checks with reasons, coverage gaps, blocking validation issues, and user approval evidence.
+- Write \`.ai/vcm/handoffs/test-report.md\` with \`Test Result: pass|fail|incomplete\`, evidence reviewed, tests added or updated, coverage mapping, validation progress, commands run or checked, validation results, test-infrastructure status and evidence, failed expectations, reproduction steps, skipped checks with reasons, coverage gaps, blocking validation issues, and user approval evidence.
+- \`test-report.md\` must include this test-infrastructure section:
+
+\`\`\`md
+## Test Infrastructure
+
+Status: none|repair-required|repaired|production-change-required
+
+### Affected Files
+
+### Boundary Evidence
+
+### Defect-Class Sweep
+
+### Repair Commit
+\`\`\`
+
+- Use \`none\` when no test-infrastructure defect was found. Every subsection must then be exactly \`None.\`.
+- Use \`repair-required\` only for a confirmed defect confined to Tester-owned scope that project-manager must route back to Tester. Record affected files, boundary evidence, and the completed defect-class sweep; set Repair Commit to exactly \`None.\` and return \`Test Result: fail\`.
+- Use \`repaired\` after the PM-routed repair is committed and required validation is rerun. Record affected files, boundary evidence, defect-class sweep, and the repair commit.
+- Use \`production-change-required\` when repair requires production or shared scope. Record affected files, boundary evidence, and the completed defect-class sweep; set Repair Commit to exactly \`None.\` and return \`Test Result: fail\`.
 - \`test-report.md\` must include this L3 section:
 
 \`\`\`md
@@ -148,13 +178,14 @@ L3 Required: yes|no
 
 - When \`L3 Required: yes\`, include at least one complete flow-to-case mapping. \`Action\` must be \`run-existing\`, \`updated\`, or \`added\`.
 - When \`L3 Required: no\`, use \`Not-Required Evidence\` to prove every condition in the L3 not-required rule.
-- In Validation-Only Flow, if tests, fixtures, test-only helpers, or \`docs/TESTING.md\` changed, commit those changes before reporting and record the changed files and commit in \`test-report.md\`. If no tracked files changed, record that no commit was required.
+- In every flow, if tests, fixtures, test-only helpers, or \`docs/TESTING.md\` changed, commit those changes before reporting a terminal result and record the changed files and commit in \`test-report.md\`. If no tracked files changed, record that no commit was required.
 - \`test-report.md\` is the current validation evidence, not a log; when rewriting it, carry forward still-unresolved findings or explicitly mark them resolved instead of dropping them.
 - In \`Coverage Mapping\`, map each accepted changed behavior or relevant risk to its validation level, actual test file and case or external evidence, exercised entry path and key assertions, result, and any remaining gap.
 - In \`Validation Progress\`, record \`Completed Validation\` and \`Remaining Validation\`. A final \`pass\` report must set remaining validation to \`None\`.
 - Use \`pass\` only when required validation completed and no blocking test failure, missing required coverage, unacceptable test weakness, or unresolved validation risk remains.
 - Use \`fail\` only when tests fail, coverage is insufficient and Tester continuation cannot resolve it, required validation is blocked from completion, test quality is unacceptable, or validation risk needs project-manager routing.
 - Use \`incomplete\` only when required validation remains, no blocking issue has been found, and another Tester turn can continue the recorded remaining work.
+- \`Test Infrastructure Status: repair-required\` or \`production-change-required\` requires \`Test Result: fail\`; neither status may appear in a \`pass\` or \`incomplete\` report.
 - When \`Test Result: pass\`, the entire body of \`Remaining Validation\`, \`Failed Expectations\`, \`Coverage Gaps\`, \`Blocking Validation Issues\`, and \`User Approval Evidence\` must be exactly \`None.\` with no additional text.
 - When \`Test Result: incomplete\`, \`Completed Validation\` and \`Remaining Validation\` must both contain concrete progress, while the entire body of \`Failed Expectations\`, \`Coverage Gaps\`, \`Blocking Validation Issues\`, and \`User Approval Evidence\` must be exactly \`None.\` with no additional text.
 - When \`Test Result: fail\`, \`Blocking Validation Issues\` must list concrete blocking evidence.

package/dist/shared/types/gate-review.js

@@ -3,6 +3,10 @@ export const GATE_REVIEW_GATES = [
     "validation-adequacy",
     "code-diff"
 ];
+export const CODE_DIFF_FINDING_SCOPES = [
+    "test-only",
+    "implementation"
+];
 export const CODE_DIFF_SOURCES = [
     "coder",
     "architect-debug",

package/dist/shared/validation/artifact-check.js

@@ -1,4 +1,4 @@
-import { ARCHITECTURE_BRIEF_STATUSES, ARCHITECTURE_PLAN_RESULTS, DOCS_SYNC_DECISIONS, FINAL_ACCEPTANCE_DECISIONS, L3_ACTIONS, L3_REQUIRED_VALUES, STRICT_NONE_VALUE, TEST_RESULTS } from "./artifact-contract.js";
+import { ARCHITECTURE_BRIEF_STATUSES, ARCHITECTURE_PLAN_RESULTS, DOCS_SYNC_DECISIONS, FINAL_ACCEPTANCE_DECISIONS, L3_ACTIONS, L3_REQUIRED_VALUES, STRICT_NONE_VALUE, TEST_INFRASTRUCTURE_STATUSES, TEST_RESULTS } from "./artifact-contract.js";
 const REQUIRED_HEADINGS = {
     "architecture-brief": [
         "Accepted Outcome",
@@ -50,6 +50,11 @@ const REQUIRED_HEADINGS = {
         "Not-Required Evidence",
         "Commands Run Or Checked",
         "Validation Results",
+        "Test Infrastructure",
+        "Affected Files",
+        "Boundary Evidence",
+        "Defect-Class Sweep",
+        "Repair Commit",
         "Failed Expectations",
         "Reproduction Steps",
         "Skipped Checks With Reasons",
@@ -152,6 +157,55 @@ function validateArtifactFields(kind, content) {
         const invalidFields = isAllowedValue(result, TEST_RESULTS)
             ? []
             : [renderExactFieldError("Test Result", TEST_RESULTS, result)];
+        const infrastructureStatus = readInlineField(readArtifactSectionContent(content, "Test Infrastructure") ?? "", "Status");
+        if (!isAllowedValue(infrastructureStatus, TEST_INFRASTRUCTURE_STATUSES)) {
+            invalidFields.push(renderExactFieldError("Test Infrastructure Status", TEST_INFRASTRUCTURE_STATUSES, infrastructureStatus));
+        }
+        const infrastructureFiles = readArtifactSectionContent(content, "Affected Files");
+        const infrastructureBoundary = readArtifactSectionContent(content, "Boundary Evidence");
+        const infrastructureSweep = readArtifactSectionContent(content, "Defect-Class Sweep");
+        const infrastructureCommit = readArtifactSectionContent(content, "Repair Commit");
+        if (infrastructureStatus === "none") {
+            for (const [heading, value] of [
+                ["Affected Files", infrastructureFiles],
+                ["Boundary Evidence", infrastructureBoundary],
+                ["Defect-Class Sweep", infrastructureSweep],
+                ["Repair Commit", infrastructureCommit]
+            ]) {
+                if (!isExactNone(value)) {
+                    invalidFields.push(renderExactSectionError(heading, STRICT_NONE_VALUE, value, "when Test Infrastructure Status is none"));
+                }
+            }
+        }
+        if (infrastructureStatus === "repair-required" || infrastructureStatus === "production-change-required") {
+            for (const [heading, value] of [
+                ["Affected Files", infrastructureFiles],
+                ["Boundary Evidence", infrastructureBoundary],
+                ["Defect-Class Sweep", infrastructureSweep]
+            ]) {
+                if (!hasSubstantiveSectionValue(value)) {
+                    invalidFields.push(`${heading} is required when Test Infrastructure Status is ${infrastructureStatus}.`);
+                }
+            }
+            if (!isExactNone(infrastructureCommit)) {
+                invalidFields.push(renderExactSectionError("Repair Commit", STRICT_NONE_VALUE, infrastructureCommit, `when Test Infrastructure Status is ${infrastructureStatus}`));
+            }
+            if (result !== "fail") {
+                invalidFields.push(`Test Result must be fail when Test Infrastructure Status is ${infrastructureStatus}.`);
+            }
+        }
+        if (infrastructureStatus === "repaired") {
+            for (const [heading, value] of [
+                ["Affected Files", infrastructureFiles],
+                ["Boundary Evidence", infrastructureBoundary],
+                ["Defect-Class Sweep", infrastructureSweep],
+                ["Repair Commit", infrastructureCommit]
+            ]) {
+                if (!hasSubstantiveSectionValue(value)) {
+                    invalidFields.push(`${heading} is required when Test Infrastructure Status is repaired.`);
+                }
+            }
+        }
         const l3Required = readInlineField(content, "L3 Required");
         if (!isAllowedValue(l3Required, L3_REQUIRED_VALUES)) {
             invalidFields.push(renderExactFieldError("L3 Required", L3_REQUIRED_VALUES, l3Required));

package/dist/shared/validation/artifact-contract.js

@@ -6,6 +6,12 @@ export const ARCHITECTURE_PLAN_RESULTS = [
     "user clarification required"
 ];
 export const TEST_RESULTS = ["pass", "fail", "incomplete"];
+export const TEST_INFRASTRUCTURE_STATUSES = [
+    "none",
+    "repair-required",
+    "repaired",
+    "production-change-required"
+];
 export const L3_REQUIRED_VALUES = ["yes", "no"];
 export const L3_ACTIONS = ["run-existing", "updated", "added"];
 export const DOCS_SYNC_DECISIONS = ["synced", "unchanged", "blocked"];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vibe-coding-master",
-  "version": "0.7.30",
+  "version": "0.7.31",
   "description": "Local GUI session cockpit for Claude Code role sessions.",
   "type": "module",
   "files": [