vibe-coding-master 0.7.4 → 0.7.5

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

@@ -29,7 +29,7 @@ ${renderRoleMemoryRules("tester")}
 - If L0/L1 coverage is missing or weak, add or update tests when possible; otherwise report the exact missing coverage in \`.ai/vcm/handoffs/test-report.md\`.
 - Own L2/L3/L4 final-validation design, execution, and acceptance evidence.
 - Targeted diagnostic L2 checks run by Coder or Architect are implementation evidence only and do not replace Tester final validation.
-- Choose validation level by risk. Unit tests are not sufficient when the change crosses module boundaries, public contracts, UI flows, CLI/tooling flows, hooks, sessions, persistence, worktrees, or external process behavior; require integration or E2E coverage, or document why it is unnecessary or unavailable.
+- Choose validation level by risk. Unit tests are not sufficient when the change crosses module boundaries, public contracts, UI flows, CLI/tooling flows, hooks, sessions, persistence, worktrees, or external process behavior; require integration or E2E coverage, or document a concrete risk-based reason why it is unnecessary. Unavailable required coverage is a blocking validation gap.
 - For important new behavior, public workflows, cross-module behavior, UI/CLI/tooling flows, persistence/session/worktree behavior, hooks, or external process behavior, add a new integration/E2E case or extend an existing one with assertions that directly cover the new behavior.
 - Do not treat an existing integration/E2E command as sufficient unless it includes assertions for the new behavior or important regression path; otherwise add or modify the case, or record why coverage is not practical.
 - When tests were changed during the task, check whether assertions were weakened, removed, over-mocked, or rewritten to match the implementation instead of the approved behavior. Report this as a validation gap unless the approved contract changed.
@@ -67,13 +67,14 @@ ${renderRoleMemoryRules("tester")}
 
 ### Outputs
 
-- Write \`.ai/vcm/handoffs/test-report.md\` with \`Test Result: pass|fail\`, evidence reviewed, tests added or updated, commands run or checked, validation results, failed expectations, reproduction steps, skipped checks with reasons, coverage gaps, and blocking validation issues.
+- Write \`.ai/vcm/handoffs/test-report.md\` with \`Test Result: pass|fail\`, evidence reviewed, tests added or updated, coverage mapping, commands run or checked, validation results, failed expectations, reproduction steps, skipped checks with reasons, coverage gaps, and blocking validation issues.
 - \`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.
 - 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\` when tests fail, coverage is insufficient, important validation cannot complete, test quality is unacceptable, or validation risk needs project-manager routing.
 - When \`Test Result: pass\`, \`Blocking Validation Issues\` must be \`None\`.
 - When \`Test Result: fail\`, \`Blocking Validation Issues\` must list concrete blocking evidence.
-- For feature or cross-boundary changes, state which new or updated integration/E2E cases cover the important paths, or why such coverage is not needed or not available.
+- For feature or cross-boundary changes, state which new or updated integration/E2E cases cover the important paths, or give the concrete risk-based reason such coverage is unnecessary. If required coverage is unavailable, report it as a blocking issue.
 - For changed or newly added tests, state why the assertions prove real behavior rather than fixture-specific, implementation-specific, or mock-only behavior.
 - Report confirmed unresolved issues that should survive current-task cleanup in \`.ai/vcm/handoffs/test-report.md\`; do not write \`.ai/vcm/handoffs/known-issues.md\` (architect-owned).
 

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

@@ -2,7 +2,19 @@ const REQUIRED_HEADINGS = {
     "architecture-plan": [
         "Accepted Scope",
         "Current Code Reality",
+        "Planning Boundary",
+        "Code Reading Evidence",
+        "Existing Behavior Trace",
+        "Code / Docs Conflicts",
         "Architecture Decision",
+        "Changed Behavior Flow",
+        "Ownership",
+        "Data Flow",
+        "Lifecycle",
+        "Boundaries",
+        "Invariants",
+        "Failure Model",
+        "Decision Rationale",
         "Module/File Plan",
         "Public Surface Impact",
         "Scaffold Manifest",
@@ -18,6 +30,7 @@ const REQUIRED_HEADINGS = {
     "test-report": [
         "Evidence Reviewed",
         "Tests Added Or Updated",
+        "Coverage Mapping",
         "Commands Run Or Checked",
         "Validation Results",
         "Failed Expectations",
@@ -92,9 +105,16 @@ export function checkMarkdownArtifact(kind, artifactPath, content) {
 function validateArtifactFields(kind, content) {
     if (kind === "test-report") {
         const result = /^\s*Test Result\s*:\s*(\S+)\s*$/im.exec(content)?.[1]?.toLowerCase();
-        return result === "pass" || result === "fail"
+        const invalidFields = result === "pass" || result === "fail"
             ? []
             : ["Test Result must be pass or fail."];
+        if (result === "pass") {
+            const blockingIssues = readArtifactSectionValue(content, "Blocking Validation Issues");
+            if (!blockingIssues || !/^none\.?$/i.test(blockingIssues)) {
+                invalidFields.push("Blocking Validation Issues must be None when Test Result is pass.");
+            }
+        }
+        return invalidFields;
     }
     if (kind === "docs-sync-report") {
         return validateDecision(content, ["synced", "unchanged", "blocked"]);

package/package.json

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