vibe-coding-master 0.0.16 → 0.2.0

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

@@ -0,0 +1,86 @@
+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.
+
+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.
+
+Allowed message types:
+
+- task
+- question
+- revise
+- cancel
+- result
+- blocked
+- finding
+
+## Route File
+
+Write or update exactly one file:
+
+\`\`\`text
+.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.
+
+If the same route file already contains a not-yet-delivered message, update that file instead of creating a fragmented follow-up.
+
+## Message Format
+
+\`\`\`md
+---
+type: task
+artifact_refs:
+  - .ai/vcm/handoffs/architecture-plan.md
+  - docs/plans/example.md
+---
+
+Summary:
+...
+
+Request or result:
+...
+
+Evidence:
+...
+
+Expected next action:
+...
+\`\`\`
+
+Use the smallest body that is complete. Include artifact refs instead of copying long documents.
+
+## Required Body Content
+
+- why this message exists
+- what the target role should do or what result is being reported
+- source of truth or artifact references
+- validation or documentation state when relevant
+- blocker, decision needed, or next step when relevant
+
+## Turn Rule
+
+After writing or updating the route file, end the current Claude Code turn immediately.
+
+Do not:
+
+- send another message to the same target role in the same turn
+- poll route files
+- 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
+
+VCM scans pending route files after the Stop hook and delivers later replies in a new turn.
+
+## Recovery
+
+If delivery is manual, blocked, or the target role is busy, leave the route file non-empty. Do not clear it yourself unless the user or VCM controller has explicitly confirmed manual handling.
+`;
+}

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

@@ -20,6 +20,7 @@ ${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}.
 - After writing a route file, end this Claude Code turn immediately.

package/dist/backend/templates/role-command.js

@@ -1,6 +1,12 @@
-export function renderRoleCommandTemplate(taskSlug, role) {
+export function renderRoleCommandTemplate(taskSlug, role, taskRepoRoot = "$VCM_TASK_REPO_ROOT", branch = "TBD") {
     return `# ${role} command for ${taskSlug}
 
+## Worktree
+
+Task repo root: ${taskRepoRoot}
+Branch: ${branch}
+Rule: only edit files under Task repo root.
+
 ## Objective
 
 TBD

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

@@ -6,15 +6,9 @@ const REQUIRED_HEADINGS = {
         "Risks",
         "Stop Conditions"
     ],
-    "implementation-log": [
-        "Summary",
-        "Files Changed",
-        "Validation",
-        "Deviations From Architecture Plan",
-        "Follow-ups"
-    ],
-    "validation-log": [
-        "Validation"
+    "known-issues": [
+        "Task Issues",
+        "Escalation To Docs"
     ],
     "review-report": [
         "Summary",
@@ -29,7 +23,18 @@ const REQUIRED_HEADINGS = {
         "Docs Reviewed And Left Unchanged",
         "Public Contract / Module Boundary Notes",
         "Remaining Documentation Risks",
+        "Known Issues Disposition",
         "Decision"
+    ],
+    "final-acceptance": [
+        "Decision",
+        "Evidence Reviewed",
+        "Scope Traceability",
+        "Validation Summary",
+        "Review And Docs Sync",
+        "Known Issues Disposition",
+        "Cleanup Readiness",
+        "Final User Summary"
     ]
 };
 const PLACEHOLDER_PATTERN = /(^|\n)\s*(TBD|Not run yet\.?|status:\s*draft)\s*(\n|$)/i;