vibe-coding-master 0.6.19 → 0.6.21

package/dist/backend/templates/harness/vcm-route-message-skill.js

@@ -1,13 +1,24 @@
 export function renderVcmRouteMessageSkillRules() {
     return `## Purpose
 
-Use this skill when a VCM role needs to hand work, ask a question, report a result, report a blocker, or raise a finding to another VCM role.
+Use this skill when project-manager dispatches a VCM role or when a VCM role reports a question, result, blocker, or finding back to project-manager.
 
 This skill writes a route file. It does not deliver the message. VCM backend delivery is triggered later by Claude Code hooks.
 
 ## Route Policy
 
-Use only routes allowed by the current VCM role rules and task approval.
+VCM uses project-manager as the routing hub.
+
+Allowed routes:
+
+- \`project-manager -> architect\`
+- \`project-manager -> coder\`
+- \`project-manager -> tester\`
+- \`architect -> project-manager\`
+- \`coder -> project-manager\`
+- \`tester -> project-manager\`
+
+Non-PM roles must not route directly to each other. Report questions, blockers, results, findings, or validation evidence back to project-manager. PM decides the next role route.
 
 Allowed message types:
 
@@ -27,7 +38,7 @@ Write or update exactly one file:
 .ai/vcm/handoffs/messages/<from-role>-<to-role>.md
 \`\`\`
 
-The file name is authoritative. Do not put from/to in frontmatter and do not create alternate message paths.
+Use one allowed route above. The file name is authoritative. Do not put from/to in frontmatter and do not create alternate message paths.
 
 If the same route file already contains a not-yet-delivered message, update that file instead of creating a fragmented follow-up.
 
@@ -37,7 +48,7 @@ Use the smallest body that is complete. Include artifact refs instead of copying
 
 For simple user relay, use a lightweight body instead of the formal dispatch format.
 
-For formal dispatch, blocker, finding, review, or gate routing, use:
+For PM dispatch, use:
 
 \`\`\`md
 ---
@@ -56,19 +67,46 @@ Request or result:
 Evidence:
 ...
 
-Expected next action:
+Next gate:
+...
+
+Stop conditions:
 ...
 \`\`\`
 
+For non-PM reports, use:
+
+\`\`\`md
+---
+type: result
+artifact_refs:
+  - .ai/vcm/handoffs/example.md
+---
+
+Summary:
+...
+
+Result, blocker, or finding:
+...
+
+Evidence:
+...
+
+Requested PM decision:
+...
+\`\`\`
+
+For non-PM role reports, \`Requested PM decision\` is a request for PM classification, not an instruction to route, skip gates, continue, pause, or close the task.
+
 ## Formal Body Content
 
 Formal messages should include:
 
 - why this message exists
-- what the target role should do or what result is being reported
+- what the target role should do for PM dispatch, or what result/status is being reported for non-PM reports
 - source of truth or artifact references
 - validation or documentation state when relevant
-- blocker, decision needed, or next step when relevant
+- blocker, finding, status, or PM decision needed when relevant
 
 ## Turn Rule
 
@@ -81,7 +119,9 @@ Do not:
 - start a shell loop
 - wait for another role's answer
 - paste directly into another role terminal
-- use Claude Code Task/Subagent for VCM role delegation
+- use Claude Code Task/Subagent to replace VCM role routing. Coder worker
+  subagents are governed by Coder's \`vcm-coder-worker\` rules and are not
+  route-message delivery.
 
 VCM scans pending route files after the Stop hook and delivers later replies in a new turn.
 

package/dist/backend/templates/message-envelope.js

@@ -2,9 +2,6 @@ export function renderMessageEnvelope(message) {
     const artifactRefs = message.artifactRefs.length > 0
         ? message.artifactRefs.map((artifact) => `- ${artifact}`).join("\n")
         : "- none";
-    const routeFileExample = message.toRole === "project-manager"
-        ? ".ai/vcm/handoffs/messages/project-manager-<target-role>.md"
-        : `.ai/vcm/handoffs/messages/${message.toRole}-project-manager.md`;
     return `
 [VCM MESSAGE]
 id: ${message.id}
@@ -21,8 +18,8 @@ ${artifactRefs}
 Instructions:
 - Read the message and execute only within this VCM task.
 - If you write or update a VCM route file, use the vcm-route-message skill.
-- If you need to send a VCM message after handling this, write or update .ai/vcm/handoffs/messages/<your-role>-<target-role>.md.
-- Non-PM roles reply only to project-manager, for example ${routeFileExample}.
+- If PM sends a VCM message after handling this, write or update .ai/vcm/handoffs/messages/project-manager-<target-role>.md.
+- If a non-PM role sends a VCM message after handling this, reply only to project-manager with .ai/vcm/handoffs/messages/<your-role>-project-manager.md.
 - After writing a route file, end this Claude Code turn immediately.
 - Do not poll, loop, or wait for another role in this turn. VCM scans route files after your Stop hook and delivers later replies in a new turn.
 [/VCM MESSAGE]

package/dist/shared/constants.js

@@ -20,9 +20,9 @@ export const CORE_VCM_ROLE_DEFINITIONS = [
         dispatchable: true
     },
     {
-        name: "reviewer",
-        label: "Reviewer",
-        commandAgent: "reviewer",
+        name: "tester",
+        label: "Tester",
+        commandAgent: "tester",
         dispatchable: true
     }
 ];

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

@@ -1,5 +1,9 @@
 export const GATE_REVIEW_GATES = [
     "architecture-plan",
     "validation-adequacy",
-    "final-diff"
+    "code-diff"
+];
+export const CODE_DIFF_SOURCES = [
+    "coder",
+    "architect-debug"
 ];

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

@@ -1,21 +1,30 @@
 const REQUIRED_HEADINGS = {
     "architecture-plan": [
-        "Context",
+        "Accepted Scope",
+        "Current Code Reality",
         "Architecture Decision",
+        "Module/File Plan",
+        "Public Surface Impact",
         "Scaffold Manifest",
-        "Implementation Plan",
-        "Risks",
-        "Stop Conditions"
+        "Tester Coverage Hints",
+        "Docs Impact",
+        "Known Risks",
+        "Coder Handoff Notes"
     ],
     "known-issues": [
         "Task Issues",
         "Escalation To Docs"
     ],
-    "review-report": [
-        "Summary",
-        "Findings",
-        "Validation",
-        "Decision"
+    "test-report": [
+        "Evidence Reviewed",
+        "Tests Added Or Updated",
+        "Commands Run Or Checked",
+        "Validation Results",
+        "Failed Expectations",
+        "Reproduction Steps",
+        "Skipped Checks With Reasons",
+        "Coverage Gaps",
+        "Blocking Validation Issues"
     ],
     "docs-sync-report": [
         "Summary",
@@ -34,6 +43,7 @@ const REQUIRED_HEADINGS = {
         "Validation Summary",
         "Review And Docs Sync",
         "Known Issues Disposition",
+        "Gate Review Gates",
         "Cleanup Readiness",
         "Final User Summary"
     ]
@@ -48,6 +58,7 @@ export function checkMarkdownArtifact(kind, artifactPath, content) {
             isEmpty: true,
             hasPlaceholder: false,
             missingHeadings: [...REQUIRED_HEADINGS[kind]],
+            invalidFields: [],
             status: "missing"
         };
     }
@@ -60,11 +71,13 @@ export function checkMarkdownArtifact(kind, artifactPath, content) {
             isEmpty: true,
             hasPlaceholder: false,
             missingHeadings: [...REQUIRED_HEADINGS[kind]],
+            invalidFields: [],
             status: "empty"
         };
     }
     const missingHeadings = REQUIRED_HEADINGS[kind].filter((heading) => !hasHeading(trimmed, heading));
     const hasPlaceholder = PLACEHOLDER_PATTERN.test(trimmed);
+    const invalidFields = validateArtifactFields(kind, trimmed);
     return {
         kind,
         path: artifactPath,
@@ -72,9 +85,50 @@ export function checkMarkdownArtifact(kind, artifactPath, content) {
         isEmpty: false,
         hasPlaceholder,
         missingHeadings,
-        status: missingHeadings.length === 0 && !hasPlaceholder ? "ok" : "incomplete"
+        invalidFields,
+        status: missingHeadings.length === 0 && !hasPlaceholder && invalidFields.length === 0 ? "ok" : "incomplete"
     };
 }
+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"
+            ? []
+            : ["Test Result must be pass or fail."];
+    }
+    if (kind === "docs-sync-report") {
+        return validateDecision(content, ["synced", "unchanged", "blocked"]);
+    }
+    if (kind === "final-acceptance") {
+        return validateDecision(content, [
+            "accepted",
+            "accepted-with-known-risks",
+            "needs-coder-follow-up",
+            "needs-architect-follow-up",
+            "needs-docs-sync",
+            "blocked-by-user-decision"
+        ]);
+    }
+    return [];
+}
+function validateDecision(content, allowed) {
+    const decision = readArtifactSectionValue(content, "Decision")?.toLowerCase();
+    return decision && allowed.includes(decision)
+        ? []
+        : [`Decision must be one of: ${allowed.join(", ")}.`];
+}
+export function readArtifactSectionValue(content, heading) {
+    const match = new RegExp(`^#{1,6}\\s+${escapeRegExp(heading)}\\s*$`, "im").exec(content);
+    if (!match || match.index === undefined) {
+        return undefined;
+    }
+    const afterHeading = content.slice(match.index + match[0].length);
+    const nextHeading = /\n#{1,6}\s+\S/.exec(afterHeading);
+    const section = nextHeading?.index === undefined
+        ? afterHeading
+        : afterHeading.slice(0, nextHeading.index);
+    return section.split(/\r?\n/).map((line) => line.trim()).find(Boolean);
+}
 function hasHeading(content, heading) {
     const pattern = new RegExp(`^#{1,6}\\s+${escapeRegExp(heading)}\\s*$`, "im");
     return pattern.test(content);