vibe-coding-master 0.8.12 → 0.8.13

package/dist/backend/services/auto-memory-service.js

@@ -1470,7 +1470,8 @@ function buildRoleDraftPrompt(taskRepoRoot, state, draft, planningCandidatePath)
                 "Review that candidate against final task evidence. Carry forward only facts that remain verified after implementation and testing."
             ]
             : []),
-        `Assigned proposal path: ${resolveRepoPath(taskRepoRoot, draft.path)}`
+        `Assigned proposal path: ${draft.path}`,
+        "Pass the assigned repository-relative path to vcm-artifact --path."
     ];
     return [
         ...prompt,

package/dist/backend/services/pm-user-question.js

@@ -6,7 +6,8 @@ const markdown = unified().use(remarkParse).use(remarkGfm).freeze();
 const DIRECT_REQUESTS = [
     /^(?:can|could|do|did|are|have|should|will|would)\s+you\b/i,
     /^(?:should|shall|may|can|could)\s+(?:i|we)\b/i,
-    /^(?:which|what|how|where|when|who)\b[^.!?]*\b(?:you|your|(?:should|shall|can|may)\s+(?:i|we))\b/i,
+    /^(?:which|what|how|where|when|who)\s+(?:is|are|was|were|do|did|have|has|can|could|will|would|should|shall|may)\s+(?:you|your|i|we)\b/i,
+    /^(?:which|what|how|where|when|who)\b[^.!?:,;]*\b(?:do|did|can|could|will|would|should|shall|may)\s+(?:you|i|we)\b/i,
     /^(?:which|what)\s+(?:option|approach|behavior|behaviour|choice)\b[^.!?]*\bshould\s+be\b/i,
     /^(?:please\s+)?(?:answer|reply|respond|choose|confirm|decide|provide|select|tell\s+me|let\s+me\s+know|give\s+(?:me|your))\b/i,
     /^i\s+need\s+your\s+(?:decision|choice|confirmation|answer|approval)\b/i,

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

@@ -42,7 +42,8 @@ ${renderRoleMemoryRules("architect")}
 
 - Architect may invoke only \`vcm-architect-evidence-worker\`, \`vcm-architect-scaffold-worker\`, and \`vcm-architect-validation-worker\`.
 - Every worker must run in the foreground and return before the current Architect turn continues. Do not run workers in the background or end the turn while a worker is active.
-- Give each worker an exact bounded assignment, repo-relative paths, and one report path. Pass paths instead of copying full source, documents, or plans into the worker prompt.
+- Give each worker an exact bounded assignment, repo-relative paths, and one report path under \`.ai/vcm/architect-workers/<worker-type>/worker-<worker-id>.md\`. Pass paths instead of copying full source, documents, or plans into the worker prompt.
+- Read the assigned report file before accepting a worker result or continuing its unfinished work; a text-only return is not a completed worker report.
 - Worker output is evidence or execution output, never an architecture decision. Architect owns every conclusion, plan, change boundary, validation interpretation, and final claim.
 - Use \`vcm-architect-evidence-worker\` for bounded bulk reading when relevant evidence spans multiple files or modules. Evidence workers may run in parallel only when their read scopes are disjoint.
 - Give evidence workers only repo-relative paths, symbols, documents, and questions. They have no shell access.

package/dist/backend/templates/harness/architect-evidence-worker-agent.js

@@ -17,7 +17,8 @@ You are \`vcm-architect-evidence-worker\`, a foreground evidence-collection suba
 
 ### Evidence Output
 
-- Write only the assigned report under \`.ai/vcm/architect-workers/evidence/\`.
+- Write the assigned report under \`.ai/vcm/architect-workers/evidence/worker-<worker-id>.md\` before returning. Only that report and its candidate or staging files may be written.
+- For candidate or staging Markdown, use \`worker-<worker-id>-candidate.md\`; never start its basename with \`report\`, \`summary\`, \`findings\`, or \`analysis\` (case-insensitive). If Write rejects a candidate or staging basename, rename it and retry; still deliver the assigned final report file, not just response text.
 - Keep the report concise and factual. Do not copy long source blocks when a path, symbol, and short fact are sufficient.
 - Use this structure:
 

package/dist/backend/templates/harness/architect-scaffold-worker-agent.js

@@ -17,8 +17,14 @@ You are \`vcm-architect-scaffold-worker\`, a foreground subagent invoked by Arch
 
 - Run \`.ai/tools/check-scaffold-ledger --mode scaffold\` and the plan's scaffold L0 compile/typecheck checks.
 - Commit only the scaffold changes after the ledger reconciles and required checks pass.
-- Return the commit hash, changed files, ledger result, and exact check results to Architect.
-- If the assigned scaffold cannot be completed, return the concrete failure evidence without changing the plan.
+- If the assigned scaffold cannot be completed, record the concrete failure evidence without changing the plan.
+
+### Scaffold Output
+
+- Write the assigned report under \`.ai/vcm/architect-workers/scaffold/worker-<worker-id>.md\` before returning, including when scaffold work remains incomplete.
+- For candidate or staging Markdown, use \`worker-<worker-id>-candidate.md\`; never start its basename with \`report\`, \`summary\`, \`findings\`, or \`analysis\` (case-insensitive). If Write rejects a candidate or staging basename, rename it and retry; still deliver the assigned final report file, not just response text.
+- Record completed and remaining Scaffold Manifest IDs, changed files, commit hash (or no commit with the reason), ledger result, exact L0 check commands and results, and concrete failure evidence.
+- Return the report path and a concise completion summary to Architect.
 
 Architect reviews the worker's commit and remains responsible for the final scaffold, plan, and evidence.
 Do not invoke another subagent.`;

package/dist/backend/templates/harness/architect-validation-worker-agent.js

@@ -13,7 +13,8 @@ You are \`vcm-architect-validation-worker\`, a foreground command-execution suba
 
 ### Validation Output
 
-- Write only the assigned report under \`.ai/vcm/architect-workers/validation/\`.
+- Write the assigned report under \`.ai/vcm/architect-workers/validation/worker-<worker-id>.md\` before returning. Only that report and its candidate or staging files may be written.
+- For candidate or staging Markdown, use \`worker-<worker-id>-candidate.md\`; never start its basename with \`report\`, \`summary\`, \`findings\`, or \`analysis\` (case-insensitive). If Write rejects a candidate or staging basename, rename it and retry; still deliver the assigned final report file, not just response text.
 - Use this structure:
 
 \`\`\`md

package/dist/backend/templates/harness/coder-worker-agent.js

@@ -26,6 +26,7 @@ You are \`vcm-coder-worker\`, a bounded implementation worker invoked by Coder.
 \`\`\`
 
 - After the sweep of assigned items and their assigned checks, commit the assigned files. After the commit succeeds, write the assigned report to a candidate outside \`.ai/vcm\`, submit it with \`.ai/tools/vcm-artifact coder-worker-report --file <candidate> --path <assigned-report-path> --mode final\`, then update only the assigned worker state to \`completed\` with the same \`commitHash\` as the final step.
+- For candidate or staging Markdown, use \`worker-<worker-id>-candidate.md\`; never start its basename with \`report\`, \`summary\`, \`findings\`, or \`analysis\` (case-insensitive). If Write rejects a candidate or staging basename, rename it and retry; still submit the assigned final report through \`vcm-artifact\`, not just response text.
 - The completed state must retain \`workerId\`, \`reportPath\`, and \`handled: false\`, set \`status\` to \`completed\`, and add \`"commitHash": "<exact-report-commit-hash>"\`.
 - Use \`completed\` only after every assigned item reached a terminal state. A successful item has green assigned proof and its marker removed. A failed item has a genuine attempt committed with objective failure evidence and its marker retained. Use \`success\` only when every item succeeded; otherwise use \`has_failed_items\`.
 - If execution is interrupted before the sweep, commit, or report completes, leave the worker state as \`running\`. Coder must resume the worker or take over the remaining work.

package/dist/backend/templates/harness/vcm-propose-memory-skill.js

@@ -10,6 +10,10 @@ planning-session memory candidate and provides an exact path.
   under \`.ai/vcm/memory-review/runs/<run-id>/drafts/\` or a planning candidate
   under \`.ai/vcm/memory-review/candidates/\` in the active task worktree.
 - If VCM did not provide a path, do not create a proposal.
+- Pass the assigned repository-relative destination unchanged to \`--path\`;
+  do not prefix it with the task worktree or base repository root. \`--file\`
+  names the candidate file, not the destination. VCM writes the accepted proposal
+  inside the active task worktree.
 - Propose only verified, durable, reusable project knowledge supported by task
   evidence.
 - Before proposing an add or update, check current durable documents, Harness

package/dist/backend/templates/harness/vcm-report-harness-issue-skill.js

@@ -5,16 +5,20 @@ This skill records feedback only. It must not call Harness Engineer directly and
 
 ## Write Location
 
-Submit one markdown file under:
+Submit one markdown file with this repository-relative \`--path\`:
 
 \`\`\`
-\${VCM_BASE_REPO_ROOT}/.ai/vcm/harness-feedback/pending/
+.ai/vcm/harness-feedback/pending/<UTC timestamp>-<reporter-role>-<short-slug>.md
 \`\`\`
 
 If \`VCM_BASE_REPO_ROOT\` is not set, do not guess a fallback path. Report the
 environment problem to project-manager so VCM can retry with the correct base
 repository root.
 
+VCM resolves this destination inside the base repository root, not the task
+worktree. Do not prefix \`--path\` with \`VCM_BASE_REPO_ROOT\` or an absolute
+directory. \`--file\` names the candidate file, not the destination.
+
 Use a filename like:
 
 \`\`\`

package/package.json

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

package/scripts/harness-tools/vcm-artifact

@@ -19,7 +19,7 @@ def parse_args() -> argparse.Namespace:
     parser.add_argument("--mode", choices=("draft", "final"), default="final")
     parser.add_argument(
         "--path",
-        help="VCM-assigned destination for dynamic artifacts or a durable-document assignment report.",
+        help="Repository-relative VCM-assigned destination; never an absolute path. VCM selects the artifact's repository root.",
     )
     parser.add_argument(
         "--keep-candidate",