vibe-coding-master 0.7.43 → 0.7.44

package/dist/backend/templates/harness/vcm-ask-user-skill.js

@@ -0,0 +1,82 @@
+export function renderVcmAskUserSkillRules() {
+    return `## Purpose
+
+Use this skill whenever Project Manager asks the user a question.
+
+## Ask And Wait
+
+Register the exact question before asking it:
+
+\`\`\`bash
+.ai/tools/vcm-ask-user --question "<exact question>"
+\`\`\`
+
+After the tool returns \`awaiting_user\`, ask that question and end the turn. Do not request Workflow Review, write a route message, run a Gate, or advance the workflow in the same turn.
+
+Every question pauses the workflow. PM may defer a question by not asking it; once PM asks, only a new direct user message resumes the workflow. The previous workflow approval is canceled, so request a fresh approval before the next dispatch.
+`;
+}
+export function renderAskUserTool() {
+    return `#!/usr/bin/env python3
+import argparse
+import json
+import os
+import sys
+import urllib.error
+import urllib.parse
+import urllib.request
+
+
+def emit(status, message=None, state=None):
+    payload = {"status": status}
+    if message:
+        payload["message"] = message
+    if state is not None:
+        payload["state"] = state
+    print(json.dumps(payload, ensure_ascii=False))
+
+
+def main():
+    parser = argparse.ArgumentParser(description="Pause VCM workflow for an exact user question.")
+    parser.add_argument("--question", required=True)
+    args = parser.parse_args()
+
+    if os.environ.get("VCM_ROLE") != "project-manager":
+        emit("failed", "Only project-manager may ask the user through VCM workflow control.")
+        return 2
+
+    question = args.question.strip()
+    if not question:
+        emit("failed", "A non-empty user question is required.")
+        return 2
+
+    api_url = os.environ.get("VCM_API_URL", "").rstrip("/")
+    task_slug = os.environ.get("VCM_TASK_SLUG", "").strip()
+    if not api_url or not task_slug:
+        emit("failed", "VCM_API_URL or VCM_TASK_SLUG is unavailable; the workflow was not paused.")
+        return 2
+
+    url = f"{api_url}/api/tasks/{urllib.parse.quote(task_slug, safe='')}/ask-user"
+    request = urllib.request.Request(
+        url,
+        data=json.dumps({"question": question}).encode("utf-8"),
+        headers={"content-type": "application/json"},
+        method="POST",
+    )
+    try:
+        with urllib.request.urlopen(request, timeout=5) as response:
+            state = json.loads(response.read().decode("utf-8"))
+        emit("awaiting_user", state=state)
+        return 0
+    except urllib.error.HTTPError as error:
+        detail = error.read().decode("utf-8", errors="replace")
+        emit("failed", f"VCM rejected the user question: HTTP {error.code} {detail}")
+    except (OSError, ValueError, urllib.error.URLError) as error:
+        emit("failed", f"VCM could not register the user question: {error}")
+    return 1
+
+
+if __name__ == "__main__":
+    sys.exit(main())
+`;
+}

package/dist/backend/templates/harness/vcm-code-navigation-skill.js

@@ -7,14 +7,16 @@ Use this skill when Architect must establish symbol definitions, implementations
 
 1. Define the affected feature or module boundary and locate entry symbols with \`.ai/generated/module-index.json\` and \`.ai/generated/public-surface.json\` when available.
 2. Use LSP workspace or file symbols, definitions, implementations, references, and incoming or outgoing call hierarchy to resolve project-owned relationships. If \`LSP\` is unavailable, report a VCM LSP configuration failure instead of substituting text search.
-3. If an initial workspace-symbol request is empty or reports indexing, wait and retry; startup or indexing time does not permit replacing a required semantic query with text matching. Retry the same bounded workspace query at most two more times. If it still cannot resolve, record the operation and result as unresolved.
-4. Read the complete project-owned callable unit at every resolved location.
-5. Expand one project-owned dependency hop at a time until the required behavior path has no unresolved symbol.
-6. Use Glob, generated context, architecture documents, and runtime evidence to locate dynamic registrations, configuration or string edges, macros, documentation, and external boundaries that LSP does not model.
+3. Treat LSP results as symbol-specific. An accessor, backing field, trait declaration, implementation method, wrapper, and alias are separate symbols. Query every relevant symbol separately. When starting from an accessor or wrapper, read its implementation, resolve the backing field, delegate, or trait item with LSP, then query those symbols too. Never use one symbol's references as proof of a complete semantic class.
+4. If an initial workspace-symbol request is empty or reports indexing, wait and retry; startup or indexing time does not permit replacing a required semantic query with text matching. Retry the same bounded workspace query at most two more times. If it still cannot resolve, record the operation and result as unresolved.
+5. Read the complete project-owned callable unit at every resolved location.
+6. Expand one project-owned dependency hop at a time until the required behavior path has no unresolved symbol.
+7. If the correct LSP operation against the actual symbol is demonstrably partial for a relationship LSP does not model or expose, record the operation, result, and missing relationship. Then use an exact text search only within the already identified owning file or module to locate candidates. Read every candidate and verify its semantics against code and LSP. Text matches are candidate locations, not relationship evidence, and must not expand the search boundary or replace the initial LSP query.
+8. Use Glob, generated context, architecture documents, and runtime evidence to locate dynamic registrations, configuration or string edges, macros, documentation, and external boundaries that LSP does not model.
 
 ## Evidence
 
-- Record each resolved relationship and whether it came from LSP, runtime evidence, an external boundary, or a generated boundary.
+- Record each resolved relationship and whether it came from LSP, runtime evidence, verified bounded source fallback, an external boundary, or a generated boundary.
 - When an empty LSP result contradicts a direct call in the code, another LSP result, or runtime evidence, treat the relationship as unresolved. Record the contradiction and use exact fallback evidence.
 - If LSP is unavailable or cannot resolve a required project-owned relationship, record that limitation and leave the relationship unresolved.
 - Generated indexes and architecture docs locate likely code; reading current-worktree implementation establishes behavior.

package/dist/backend/templates/harness/vcm-task-state-skill.js

@@ -10,12 +10,12 @@ The declaration is recoverable context, not a workflow controller. It does not a
 Record a recoverable checkpoint with:
 
 \`\`\`bash
-.ai/tools/update-task-state --flow code-change --step awaiting-user --status awaiting-user
+.ai/tools/update-task-state --flow code-change --step architect-planning --status active
 \`\`\`
 
 Supply only fields that changed. Use \`none\` to clear branch or resume point. Repeat \`--evidence\` for evidence paths.
 
-Declare the selected flow before its first dispatch, update the step before later PM dispatches, and update no-route checkpoints such as waiting for the user, waiting for Gate Review, or completion. Do not put task-state or workflow-approval fields in route-message frontmatter.
+Declare the selected flow before its first dispatch, update the step before later PM dispatches, and update no-route checkpoints such as waiting for Gate Review or completion. Use \`vcm-ask-user\`, not this advisory declaration, whenever PM asks the user a question. Do not put task-state or workflow-approval fields in route-message frontmatter.
 
 If declaration fails, report the warning when relevant and continue the existing workflow. Never delay routing, Gate Review, final acceptance, or task close because task state is unavailable.
 `;

package/dist/backend/templates/harness/vcm-workflow-review-skill.js

@@ -44,7 +44,7 @@ If VCM rejects the transition, remain in the current PM turn and choose a legal
 
 ## User Authorization
 
-Only the user's explicit instruction may authorize a rejected transition. Ask the user directly and wait. After the user authorizes the exact exception, resubmit the unchanged transition with:
+Only the user's explicit instruction may authorize a rejected transition. Use \`vcm-ask-user\` with the exact authorization question, ask it, and wait. After the user authorizes the exact exception, resubmit the unchanged transition with:
 
 \`\`\`text
 Authorization Text: <user's exact authorization>

package/dist/shared/types/workflow.js

@@ -11,6 +11,7 @@ export const WORKFLOW_EVIDENCE_ARTIFACTS = [
     "test-report.md",
     "architect-debug.md",
     "architecture-diagnosis.md",
+    "docs-update-report.md",
     "docs-sync-report.md",
     "final-acceptance.md"
 ];

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

@@ -1,4 +1,4 @@
-import { ARCHITECT_DEBUG_STATUSES, ARCHITECTURE_BRIEF_STATUSES, ARCHITECTURE_DIAGNOSIS_DISPOSITIONS, ARCHITECTURE_EVIDENCE_STATUSES, ARCHITECTURE_PLAN_RESULTS, CODER_COMPLETION_DECISIONS, DOCS_SYNC_DECISIONS, FINAL_ACCEPTANCE_DECISIONS, L3_ACTIONS, L3_REQUIRED_VALUES, PLANNING_PROGRESS_STATUSES, STRICT_NONE_VALUE, TEST_INFRASTRUCTURE_STATUSES, TEST_RESULTS } from "./artifact-contract.js";
+import { ARCHITECT_DEBUG_STATUSES, ARCHITECTURE_BRIEF_STATUSES, ARCHITECTURE_DIAGNOSIS_DISPOSITIONS, ARCHITECTURE_EVIDENCE_STATUSES, ARCHITECTURE_PLAN_RESULTS, CODER_COMPLETION_DECISIONS, DOCS_REPORT_DECISIONS, FINAL_ACCEPTANCE_DECISIONS, L3_ACTIONS, L3_REQUIRED_VALUES, PLANNING_PROGRESS_STATUSES, STRICT_NONE_VALUE, TEST_INFRASTRUCTURE_STATUSES, TEST_RESULTS } from "./artifact-contract.js";
 import { getArtifactDefinition } from "./artifact-registry.js";
 const PLACEHOLDER_PATTERN = /(^|\n)\s*(TBD|Not run yet\.?|status:\s*draft)\s*(\n|$)/i;
 export function checkMarkdownArtifact(kind, artifactPath, content, options = {}) {
@@ -244,8 +244,8 @@ function validateArtifactFields(kind, content, mode) {
         }
         return invalidFields;
     }
-    if (kind === "docs-sync-report") {
-        return validateDecision(content, DOCS_SYNC_DECISIONS);
+    if (kind === "docs-update-report" || kind === "docs-sync-report") {
+        return validateDecision(content, DOCS_REPORT_DECISIONS);
     }
     if (kind === "final-acceptance") {
         return validateDecision(content, FINAL_ACCEPTANCE_DECISIONS);

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

@@ -23,7 +23,7 @@ export const TEST_INFRASTRUCTURE_STATUSES = [
 ];
 export const L3_REQUIRED_VALUES = ["yes", "no"];
 export const L3_ACTIONS = ["run-existing", "updated", "added"];
-export const DOCS_SYNC_DECISIONS = ["synced", "unchanged", "blocked"];
+export const DOCS_REPORT_DECISIONS = ["synced", "unchanged", "blocked"];
 export const FINAL_ACCEPTANCE_DECISIONS = [
     "accepted",
     "accepted-with-known-risks",

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

@@ -156,6 +156,22 @@ export const ARTIFACT_DEFINITIONS = [
             "User Approval Evidence"
         ]
     },
+    {
+        kind: "docs-update-report",
+        fileName: "docs-update-report.md",
+        owner: ["architect", "coder", "tester"],
+        requiredHeadings: [
+            "Summary",
+            "Assignment ID",
+            "Documents Updated",
+            "Documents Reviewed And Left Unchanged",
+            "Evidence Reviewed",
+            "Checks Performed",
+            "Commit",
+            "Remaining Documentation Issues",
+            "Decision"
+        ]
+    },
     {
         kind: "docs-sync-report",
         fileName: "docs-sync-report.md",