vibe-coding-master 0.3.22 → 0.3.24

package/dist/backend/services/translation-service.js

@@ -157,6 +157,8 @@ export function createTranslationService(deps) {
     }
     function startTranscriptTail(roleSession) {
         const state = getState(roleSession.id);
+        state.taskSlug = roleSession.taskSlug;
+        state.role = roleSession.role;
         if (state.unsubscribeTranscript) {
             return;
         }
@@ -183,7 +185,7 @@ export function createTranslationService(deps) {
         const config = await loadConfig();
         let displayed = false;
         if (event.kind === "text") {
-            const shouldTranslate = config.outputMode === "all" || event.stopReason === "end_turn";
+            const shouldTranslate = shouldTranslateTextTranscriptEvent(state, event, config);
             displayed = shouldTranslate
                 ? processClaudeOutputText(sessionId, event.text, config, event.id, {
                     flushImmediately: event.stopReason === "end_turn"
@@ -206,6 +208,18 @@ export function createTranslationService(deps) {
             state.seenTranscriptIds.add(event.id);
         }
     }
+    function shouldTranslateTextTranscriptEvent(state, event, config) {
+        if (config.outputMode === "all") {
+            return true;
+        }
+        if (event.stopReason !== "end_turn") {
+            return false;
+        }
+        if (config.outputMode === "pm-final-only") {
+            return state.role === "project-manager";
+        }
+        return true;
+    }
     function processClaudeOutputText(sessionId, rawText, config, entryId, options = {}) {
         return startClaudeOutputTranslation(sessionId, rawText, config, {
             entryId,
@@ -890,8 +904,6 @@ export function createTranslationService(deps) {
             });
         }
         return deps.codexTranslationService.createConversationJob(input.repoRoot, {
-            taskSlug: input.taskSlug,
-            role: input.role,
             direction: input.direction,
             sourceText: input.text,
             sourceLanguage: input.sourceLanguage,
@@ -921,7 +933,6 @@ export function createTranslationService(deps) {
             }
             try {
                 return await deps.codexTranslationService.validateConversationResult(repoRoot, {
-                    taskSlug: job.taskSlug,
                     resultPath: job.resultPath,
                     sourceHash: job.sourceHash,
                     targetLanguage: job.targetLanguage

package/dist/backend/templates/handoff.js

@@ -15,9 +15,9 @@ Task-specific context and coder guidance go here, not in source-code comments.
 Source-code comments should only describe durable behavior, contracts, invariants,
 error boundaries, or non-obvious logic that should remain useful after this task.
 
-| File | Action | Task Context | Durable Code Comment Needed | Coder Work | Allowed Freedom | VCM:CODE | Proof Point | Replan Trigger |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| TBD | TBD | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
+| ID | File | Action | Task Context | Durable Code Comment Needed | Coder Work | Allowed Freedom | VCM:CODE | Proof Point | Replan Trigger |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| SCF-001 | TBD | TBD | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
 
 ## Implementation Plan
 

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

@@ -27,7 +27,8 @@ export function renderArchitectHarnessRules() {
 
 - Define the expected implementation scope: affected modules, changed or created files, each file's responsibility, why it is in scope, and user-visible behavior changes.
 - Define every non-private callable surface intended for use outside its file: visibility, signature shape, responsibility, expected callers, behavior contract, side effects, and error boundaries.
-- Include a \`Scaffold Manifest\` for task-specific file context: file action, why the file is in scope, coder work, allowed implementation freedom, expected \`VCM:CODE\` placeholders, durable code comment needs, proof points, and Replan triggers.
+- Include a \`Scaffold Manifest\` for task-specific file context: stable row ID, file action, why the file is in scope, coder work, allowed implementation freedom, expected \`VCM:CODE\` placeholders, durable code comment needs, proof points, and Replan triggers.
+- Give each Scaffold Manifest row a stable ID such as \`SCF-001\`; use that ID in any related \`VCM:CODE\` marker so coder can report completion by ID.
 - Put task context, phase notes, handoff instructions, temporary rationale, and coder guidance in the \`Scaffold Manifest\`, not in source-code comments.
 - Cover architecture docs impact, known risks, and Replan triggers.
 - For docs impact, state whether changes belong in \`docs/ARCHITECTURE.md\`, affected \`<module>/ARCHITECTURE.md\`, \`.ai/generated/public-surface.json\`, or no durable architecture doc.
@@ -41,7 +42,7 @@ export function renderArchitectHarnessRules() {
 - Define every new or changed non-private callable surface directly in code with its signature shape and contract comment.
 - When changing an existing non-private callable surface, update its signature and contract comment in code before coder work starts; leave \`VCM:CODE\` only where implementation must change.
 - Non-private callable surface includes any function, method, type, trait, enum, constant, re-export, or similar symbol that another file can call or depend on.
-- Mark incomplete implementation bodies with \`VCM:CODE\`; coder must implement them and remove the markers before handoff.
+- Mark incomplete implementation bodies with \`VCM:CODE <Scaffold Manifest ID>\`; coder must implement them and remove the markers before handoff.
 - Architect scaffolding may include modules, files, signatures, type shapes, durable comments, and placeholder bodies, but not real business implementation beyond minimal scaffold code.
 - Coder may add private implementation helpers, but must not add or change cross-file callable surface without architect replan.
 

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

@@ -10,7 +10,7 @@ export function renderCoderHarnessRules() {
 ### Coder Implementation Discipline
 
 - Implement the architect-defined scaffold exactly; do not change file responsibilities, callable-surface signatures, or architect-defined contract intent unless the architecture plan explicitly allows it.
-- Implement every \`VCM:CODE\` placeholder and remove all \`VCM:CODE\` markers before handoff.
+- Implement every \`VCM:CODE\` placeholder, track completion by Scaffold Manifest ID when present, and remove all \`VCM:CODE\` markers before handoff.
 - Do not fake completion: no hardcoded success, disabled logic, swallowed errors, test-only shortcuts, or silent fallback that hides failure.
 - Keep the diff inside approved scope: no unrelated rewrites, drive-by refactors, renamed symbols, moved files, or formatting churn.
 - Preserve existing behavior unless the architecture plan explicitly changes it; keep existing call sites and shared code paths working.
@@ -40,6 +40,11 @@ export function renderCoderHarnessRules() {
 - Do not weaken, delete, or skip tests to make validation pass.
 - Record confirmed out-of-scope issues found during implementation in \`.ai/vcm/handoffs/known-issues.md\`.
 
+### Handoff
+
+- In the route message back to project-manager, include a \`Scaffold Completion\` section when the architecture plan contains a Scaffold Manifest.
+- The \`Scaffold Completion\` section must report completed Scaffold Manifest IDs or \`VCM:CODE\` IDs, remaining markers if any, private helpers added, manifest deviations, and whether Replan is needed.
+
 ### Generated Context
 
 - Regenerate \`.ai/generated/module-index.json\` with \`.ai/tools/generate-module-index\` after module, manifest, source-file, or test-file changes.

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

@@ -35,10 +35,19 @@ export function renderProjectManagerHarnessRules() {
 ### Dispatch
 
 - Use the \`vcm-route-message\` skill for every role dispatch, question, result, blocker, or finding.
-- Route messages contain PM-owned routing context only: target role, user request summary, known user constraints, source of truth, required next gate, skipped gates when applicable, required handoff inputs, expected artifact, stop conditions, and confirmed worktree information.
+- Formal route messages contain PM-owned routing context only: target role, user request summary, known user constraints, source of truth, required next gate, skipped gates when applicable, required handoff inputs, expected artifact, stop conditions, and confirmed worktree information.
 - Do not write technical design into route messages; ask architect to determine architecture, file scope, public contracts, behavior/contract proof points, docs impact, and Replan triggers.
 - For coder or reviewer messages, reference existing handoff artifacts instead of making new technical judgments.
 
+### Simple User Relay
+
+When forwarding a user's answer, clarification, or small preference update to an active role, use a lightweight relay message.
+
+PM may lightly rewrite the user's words to:
+- clarify pronouns or references from the current context
+- translate the user's intent into clear role-facing language
+- state whether this is confirmation, rejection, preference, or a small constraint
+
 ### Phased Tasks
 
 - When architect provides a phased plan, dispatch only one phase at a time.

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

@@ -33,6 +33,12 @@ If the same route file already contains a not-yet-delivered message, update that
 
 ## Message Format
 
+Use the smallest body that is complete. Include artifact refs instead of copying long documents.
+
+For simple user relay, use a lightweight body instead of the formal dispatch format.
+
+For formal dispatch, blocker, finding, review, or gate routing, use:
+
 \`\`\`md
 ---
 type: task
@@ -54,9 +60,9 @@ Expected next action:
 ...
 \`\`\`
 
-Use the smallest body that is complete. Include artifact refs instead of copying long documents.
+## Formal Body Content
 
-## Required Body Content
+Formal messages should include:
 
 - why this message exists
 - what the target role should do or what result is being reported

package/dist/shared/types/app-settings.js

@@ -12,8 +12,9 @@ export const TRANSLATION_TARGET_LANGUAGE_OPTIONS = [
     { value: "es", label: "Spanish" }
 ];
 export const TRANSLATION_OUTPUT_MODE_OPTIONS = [
-    { value: "final-only", label: "Final summary" },
-    { value: "all", label: "All output" }
+    { value: "pm-final-only", label: "PM final reply" },
+    { value: "final-only", label: "Each role final reply" },
+    { value: "all", label: "All replies" }
 ];
 export function createDefaultLaunchTemplate() {
     const roles = {};