vibe-coding-master 0.6.9 → 0.6.11

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

@@ -68,8 +68,10 @@ export function renderArchitectHarnessRules() {
 - Remove temporary diagnostics before completion.
 - If the fix exceeds those limits, return a normal architecture plan with root cause, evidence, affected scope, and Replan triggers.
 - Architect-run validation in Debug Mode is diagnostic evidence, not final acceptance.
+- Before handing off an architect-completed Debug Mode fix, run the smallest relevant L0 fast checks for the touched files or changed modules: format, lint, typecheck, boundary, dependency, or project-defined equivalents. If a check cannot run, report the exact reason.
+- If the Debug Mode fix changes module structure, source/test file lists, public APIs, routes, exports, re-exports, or other externally consumed surface, run \`.ai/tools/generate-module-index\` / \`.ai/tools/generate-public-surface\` or their \`--check\` mode as applicable.
 - After an architect-completed debug fix, route to reviewer for independent final validation before project-manager final acceptance.
-- Report root cause, changed files, production-code changed line count, validation run, and final disposition.
+- Report root cause, changed files, production-code changed line count, L0 checks run or skipped with reason, generated-context regeneration or freshness check when applicable, diagnostic validation run, and final disposition.
 
 ### Replan And Drift
 

package/dist/backend/templates/harness/project-manager-agent.js

@@ -17,6 +17,17 @@ export function renderProjectManagerHarnessRules() {
 - Do not overload the user with file names, function names, logs, or implementation details unless they are necessary for the user's decision.
 - Do not oversimplify findings. Preserve the cause, impact, risk, and required next step so the user can understand why the flow is blocked or why approval is needed.
 
+### PM Managed Mode
+
+PM Managed Mode applies only when the user explicitly asks to complete the current task in this mode.
+
+- PM must drive the task to completion according to the user's request.
+- PM must not delay, narrow, reinterpret, skip, or deviate from the requested task without explicit user approval.
+- Questions about how to complete the task are managed inside the VCM flow. This includes workload, phasing, implementation approach, module boundaries, dependencies, internal services, permissions, validation, debugging, replanning, and review fixes.
+- Simple or technical execution questions should be routed to Architect or the responsible role for decision.
+- Ask the user only when the task cannot proceed without user intent or real-world authorization: unclear or conflicting requirements, required external accounts/secrets/test environments/data access, real cost, production permission, sensitive data access, durable-doc conflict, or a proven need to change the requested outcome.
+- When PM asks the user, the flow must stop and wait for the user's explicit instruction before continuing.
+
 ### Routing
 
 - Use the routes defined in \`CLAUDE.md\`.