@mindstudio-ai/remy 0.1.229 → 0.1.231

package/dist/headless.js

@@ -682,11 +682,17 @@ function parseFrontmatter(filePath) {
     return { name: "", description: "", type: "" };
   }
 }
-function loadPlanStatus() {
+function loadPlanStatus(onboardingState) {
   try {
     const content = fs4.readFileSync(".remy-plan.md", "utf-8");
     const match = content.match(/^---\n([\s\S]*?)\n---/);
     const status = match?.[1]?.match(/^status:\s*(.+)$/m)?.[1]?.trim();
+    if (status === "pending" && onboardingState === "intake") {
+      return `
+<pending_initial_plan>
+This is your initial plan, proposed via writePlan and awaiting the user's decision. The user approves it by pressing "Start Building" \u2014 you'll get an approveInitialPlan message when they do, and it will tell you to begin. Until then, stay in intake: keep discussing, and revise with writePlan if the user asks. Don't start building on your own, even if the user says "looks good" in chat.
+</pending_initial_plan>`;
+    }
     if (status === "pending") {
       return `
 <pending_plan>
@@ -868,7 +874,7 @@ The user is currently in ${viewContext?.mode ?? "code"} mode.
 ${viewContext?.activeFile ? `Active file: ${viewContext.activeFile}` : ""}
 </view_context>
 
-${loadPlanStatus()}
+${loadPlanStatus(onboardingState)}
 `;
   return resolveIncludes(template);
 }
@@ -1379,8 +1385,11 @@ var updatePlanStatusTool = {
       required: ["status"]
     }
   },
-  async execute(input) {
+  async execute(input, context) {
     const status = input.status;
+    if (context?.onboardingState === "intake") {
+      return `The initial plan isn't approved or rejected through this tool \u2014 the user decides via "Start Building". Keep discussing, and revise the plan with writePlan if they want changes.`;
+    }
     let content;
     try {
       content = await fs10.readFile(PLAN_FILE2, "utf-8");
@@ -5113,6 +5122,50 @@ ${summaryText}
 var DESCRIPTION = `
 Visual design expert. Describe the situation and what you need \u2014 the agent decides what to deliver. It reads the spec files automatically. Include relevant user requirements and context it can't get from the spec, but do not list specific deliverables or tell it how to do its job. Do not suggest implementation details or ideas - only relay what is needed.
 `.trim();
+var RENDER_WRITE_TOOL_NAMES = /* @__PURE__ */ new Set(["writeFile", "editFile"]);
+var DESIGN_EXPERT_RENDER_TOOLS = [
+  ...DESIGN_EXPERT_TOOLS,
+  writeFileTool.definition,
+  editFileTool.definition
+];
+async function runDesignExpert(opts, context) {
+  const history = context.conversationMessages ? getSubAgentHistory(context.conversationMessages, "visualDesignExpert") : [];
+  return runSubAgent({
+    system: getDesignExpertPrompt(context.onboardingState),
+    task: opts.task,
+    history: history.length > 0 ? history : void 0,
+    tools: opts.enableWrite ? DESIGN_EXPERT_RENDER_TOOLS : DESIGN_EXPERT_TOOLS,
+    externalTools: /* @__PURE__ */ new Set(),
+    executeTool: (name, input, toolCallId, onLog, sams) => {
+      const childCtx = toolCallId ? { ...deriveContext(context, toolCallId), subAgentMessages: sams } : { ...context, subAgentMessages: sams };
+      if (COMMON_READ_TOOL_NAMES.has(name)) {
+        return executeTool(name, input, childCtx);
+      }
+      if (opts.enableWrite && RENDER_WRITE_TOOL_NAMES.has(name)) {
+        return executeTool(name, input, childCtx);
+      }
+      return executeDesignExpertTool(name, input, childCtx, toolCallId, onLog);
+    },
+    apiConfig: context.apiConfig,
+    model: resolveModel("visualDesignExpert", context.models, context.model),
+    subAgentId: "visualDesignExpert",
+    signal: context.signal,
+    parentToolId: context.toolCallId,
+    requestId: context.requestId,
+    onEvent: context.onEvent,
+    resolveExternalTool: context.resolveExternalTool,
+    toolRegistry: context.toolRegistry,
+    background: opts.background,
+    onBackgroundComplete: opts.background ? (bgResult) => {
+      context.onBackgroundComplete?.(
+        context.toolCallId,
+        opts.reportingName ?? "visualDesignExpert",
+        bgResult.text,
+        bgResult.messages
+      );
+    } : void 0
+  });
+}
 var designExpertTool = {
   clearable: false,
   definition: {
@@ -5137,49 +5190,20 @@ var designExpertTool = {
     if (!context) {
       return "Error: visual design expert requires execution context";
     }
-    const history = context.conversationMessages ? getSubAgentHistory(context.conversationMessages, "visualDesignExpert") : [];
-    const result = await runSubAgent({
-      system: getDesignExpertPrompt(context.onboardingState),
-      task: input.task,
-      history: history.length > 0 ? history : void 0,
-      tools: DESIGN_EXPERT_TOOLS,
-      externalTools: /* @__PURE__ */ new Set(),
-      executeTool: (name, input2, toolCallId, onLog, sams) => {
-        const childCtx = toolCallId ? { ...deriveContext(context, toolCallId), subAgentMessages: sams } : { ...context, subAgentMessages: sams };
-        if (COMMON_READ_TOOL_NAMES.has(name)) {
-          return executeTool(name, input2, childCtx);
-        }
-        return executeDesignExpertTool(
-          name,
-          input2,
-          childCtx,
-          toolCallId,
-          onLog
-        );
+    const result = await runDesignExpert(
+      {
+        task: input.task,
+        background: input.background
       },
-      apiConfig: context.apiConfig,
-      model: resolveModel("visualDesignExpert", context.models, context.model),
-      subAgentId: "visualDesignExpert",
-      signal: context.signal,
-      parentToolId: context.toolCallId,
-      requestId: context.requestId,
-      onEvent: context.onEvent,
-      resolveExternalTool: context.resolveExternalTool,
-      toolRegistry: context.toolRegistry,
-      background: input.background,
-      onBackgroundComplete: input.background ? (bgResult) => {
-        context.onBackgroundComplete?.(
-          context.toolCallId,
-          "visualDesignExpert",
-          bgResult.text,
-          bgResult.messages
-        );
-      } : void 0
-    });
+      context
+    );
     context.subAgentMessages?.set(context.toolCallId, result.messages);
     return result.text;
   }
 };
+async function runDesignExpertRender(opts, context) {
+  return runDesignExpert({ ...opts, enableWrite: true }, context);
+}
 
 // src/subagents/productVision/tools.ts
 var VISION_TOOLS = [
@@ -5284,16 +5308,25 @@ ${unifiedDiff(filePath, oldContent, "")}`;
       const filePath = resolve("pitch.html");
       try {
         fs19.mkdirSync(ROADMAP_DIR, { recursive: true });
-        const existing = fs19.existsSync(filePath) ? fs19.readFileSync(filePath, "utf-8").trim() : "";
-        const currentDeck = existing || PITCH_DECK_SHELL;
+        const exists = fs19.existsSync(filePath);
+        const before = exists ? fs19.statSync(filePath).mtimeMs : null;
+        const delivery = exists ? `### Your deliverable
+The pitch deck already exists at \`${filePath}\`. Read it, then update it for the new <pitch_content>, keeping the presentation scaffolding intact \u2014 change only what needs to change.
+
+Reply with a one-line summary of what you changed \u2014 not the HTML.` : `### Your deliverable
+Write the complete pitch deck to \`${filePath}\`. It does not exist yet \u2014 start from this scaffold, keeping its progress bar, chevron navigation, keyboard navigation, and transition mechanics intact:
+
+<pitch_deck_shell>
+${PITCH_DECK_SHELL}
+</pitch_deck_shell>
+
+Reply with a one-line summary of what you wrote \u2014 not the HTML.`;
         const task = `
 <pitch_content>${input.task}</pitch_content>
 
-<current_deck>${currentDeck}</current_deck>
-
 We are building the pitch deck for the app. Using the provided <pitch_content>, as well as the app's spec data, think about what would make a compelling, interactive, self-contained horizontally-scrolling HTML slide deck for this product. Keep it simple, clean, powerful. Giant text, large logo, big, bold stats and claims. Edit the content as necessary to create the most impactful, bold, and beautiful slides. This should not feel like an essay, and it should not feel like a landing page \u2014 it should feel like a modern interactive presentation that leaves the user wowed by the product and excited about its future.
 
-Use <current_deck> as your starting point and replace or update the content as needed, maintaining the bones of the presentation scaffolding. Always keep the progress bar, chevron navigation, and keyboard navigation - they are part of the scaffold.
+Maintain the bones of the presentation scaffolding. Always keep the progress bar, chevron navigation, and keyboard navigation - they are part of the scaffold.
 
 ### Rules
 - The deck must be a single HTML file \u2014 it will be rendered in an iframe.
@@ -5303,14 +5336,18 @@ Use <current_deck> as your starting point and replace or update the content as n
 - Code must be clean, bug free, and easy to parse. Use GSAP for animations. Pay close attention to layout and alignment to make sure everything is perfect.
 - Keep the progress bar and edge chevrons from the shell \u2014 they are part of the navigation UX.
 
-Respond only with the complete HTML file and absolutely no other text. Your response will be written directly to an html file.`;
-        const result = await designExpertTool.execute({ task }, context);
-        const htmlMatch = result.match(
-          /```(?:html|wireframe)\n([\s\S]*?)```/
-        );
-        const html = htmlMatch ? htmlMatch[1].trim() : result;
-        fs19.writeFileSync(filePath, html, "utf-8");
-        return `Pitch deck written successfully.`;
+${delivery}`;
+        const result = await runDesignExpertRender({ task }, context);
+        context.subAgentMessages?.set(context.toolCallId, result.messages);
+        if (!fs19.existsSync(filePath)) {
+          return `Error: the design expert did not write ${filePath}. Its reply was:
+${result.text}`;
+        }
+        if (before !== null && fs19.statSync(filePath).mtimeMs === before) {
+          return `Error: the pitch deck at ${filePath} was not modified. The design expert's reply was:
+${result.text}`;
+        }
+        return `Pitch deck written to ${filePath}. ${result.text}`;
       } catch (err) {
         return `Error generating pitch deck: ${err.message}`;
       }
@@ -5544,7 +5581,7 @@ import fs20 from "fs";
 var OVERVIEW_FILE = "src/overview.html";
 var DESIGN_BRIEF = `We are building the Build Overview for this app \u2014 the home page of its Spec tab. It is a calm, dense, one-page reference of everything the app actually contains, including the parts the user can't see. It renders flush inside the Spec tab's content panel (the IDE supplies the surrounding nav).
 
-Take the plain-language copy in <overview_copy> and lay it out and skin it into a single, beautiful, self-contained HTML document in the app's own brand. If <current_overview> is non-empty, use it as your starting point and preserve its established skin, updating only what the copy changed.
+Take the plain-language copy in <overview_copy> and lay it out and skin it into a single, beautiful, self-contained HTML document in the app's own brand.
 
 ### The single hard rule
 The copy in <overview_copy> is final \u2014 it was authored and edited before it reached you. Treat it as locked content to typeset, not a draft to improve. Reproduce the words exactly: do not rewrite, rephrase, shorten, expand, reorder, or "polish" them, and do not run them through any copy tool. This is the opposite of your usual role \u2014 here you own layout, typography, and visual design only, and the words (every number, name, label, claim, and sentence) are fixed. A single changed word or wrong number breaks this document's purpose.
@@ -5559,9 +5596,7 @@ The copy in <overview_copy> is final \u2014 it was authored and edited before it
 
 ### Constraints
 - A single self-contained HTML file. Fonts may load from a CDN; everything else (CSS, the logo SVG) is inline.
-- Responsive: fills the embedded panel width and collapses gracefully at narrow widths.
-
-Respond only with the complete HTML file and absolutely no other text. Your response will be written directly to src/overview.html.`;
+- Responsive: fills the embedded panel width and collapses gracefully at narrow widths.`;
 var OVERVIEW_SHELL = `<!DOCTYPE html>
 <html lang="en">
 <head>
@@ -5582,6 +5617,22 @@ var OVERVIEW_SHELL = `<!DOCTYPE html>
      app's spec. -->
 </body>
 </html>`;
+function initialDelivery() {
+  return `### Your deliverable
+Write the complete Build Overview to \`${OVERVIEW_FILE}\`. The file does not exist yet \u2014 start from this scaffold, which carries the technical hygiene for the iframed render context (keep the viewport meta and the reset). Layout, sections, type, and styling are yours to compose.
+
+<overview_shell>
+${OVERVIEW_SHELL}
+</overview_shell>
+
+Reply with a one-line summary of what you wrote \u2014 not the HTML.`;
+}
+function refreshDelivery() {
+  return `### Your deliverable
+The Build Overview already exists at \`${OVERVIEW_FILE}\`. Read it, then update it to reflect <overview_copy>, preserving its established skin \u2014 change only what the copy changed.
+
+Reply with a one-line summary of what you changed \u2014 not the HTML.`;
+}
 var buildOverviewTool = {
   clearable: false,
   definition: {
@@ -5606,21 +5657,29 @@ var buildOverviewTool = {
     if (!content) {
       return "Error: writeBuildOverview requires non-empty `content` (the overview copy).";
     }
-    try {
-      const existing = fs20.existsSync(OVERVIEW_FILE) ? fs20.readFileSync(OVERVIEW_FILE, "utf-8").trim() : "";
-      const currentOverview = existing || OVERVIEW_SHELL;
-      const task = `<overview_copy>${content}</overview_copy>
+    const exists = fs20.existsSync(OVERVIEW_FILE);
+    const task = `<overview_copy>${content}</overview_copy>
 
-<current_overview>${currentOverview}</current_overview>
+${DESIGN_BRIEF}
 
-${DESIGN_BRIEF}`;
-      const result = await designExpertTool.execute({ task }, context);
-      const htmlMatch = result.match(
-        /```(?:html|wireframe)\n([\s\S]*?)```/
-      );
-      const html = htmlMatch ? htmlMatch[1].trim() : result;
-      fs20.writeFileSync(OVERVIEW_FILE, html, "utf-8");
-      return "Build overview written successfully to src/overview.html.";
+${exists ? refreshDelivery() : initialDelivery()}`;
+    try {
+      if (exists) {
+        input.background = true;
+        const result2 = await runDesignExpertRender(
+          { task, background: true, reportingName: "writeBuildOverview" },
+          context
+        );
+        context.subAgentMessages?.set(context.toolCallId, result2.messages);
+        return result2.text;
+      }
+      const result = await runDesignExpertRender({ task }, context);
+      context.subAgentMessages?.set(context.toolCallId, result.messages);
+      if (!fs20.existsSync(OVERVIEW_FILE)) {
+        return `Error: the design expert did not write ${OVERVIEW_FILE}. Its reply was:
+${result.text}`;
+      }
+      return `Build overview written to ${OVERVIEW_FILE}. ${result.text}`;
     } catch (err) {
       return `Error generating build overview: ${err.message}`;
     }

package/dist/index.js

@@ -938,8 +938,11 @@ var init_updatePlanStatus = __esm({
           required: ["status"]
         }
       },
-      async execute(input) {
+      async execute(input, context) {
         const status = input.status;
+        if (context?.onboardingState === "intake") {
+          return `The initial plan isn't approved or rejected through this tool \u2014 the user decides via "Start Building". Keep discussing, and revise the plan with writePlan if they want changes.`;
+        }
         let content;
         try {
           content = await fs7.readFile(PLAN_FILE2, "utf-8");
@@ -1893,11 +1896,17 @@ function parseFrontmatter(filePath) {
     return { name: "", description: "", type: "" };
   }
 }
-function loadPlanStatus() {
+function loadPlanStatus(onboardingState) {
   try {
     const content = fs10.readFileSync(".remy-plan.md", "utf-8");
     const match = content.match(/^---\n([\s\S]*?)\n---/);
     const status = match?.[1]?.match(/^status:\s*(.+)$/m)?.[1]?.trim();
+    if (status === "pending" && onboardingState === "intake") {
+      return `
+<pending_initial_plan>
+This is your initial plan, proposed via writePlan and awaiting the user's decision. The user approves it by pressing "Start Building" \u2014 you'll get an approveInitialPlan message when they do, and it will tell you to begin. Until then, stay in intake: keep discussing, and revise with writePlan if the user asks. Don't start building on your own, even if the user says "looks good" in chat.
+</pending_initial_plan>`;
+    }
     if (status === "pending") {
       return `
 <pending_plan>
@@ -2292,7 +2301,7 @@ The user is currently in ${viewContext?.mode ?? "code"} mode.
 ${viewContext?.activeFile ? `Active file: ${viewContext.activeFile}` : ""}
 </view_context>
 
-${loadPlanStatus()}
+${loadPlanStatus(onboardingState)}
 `;
   return resolveIncludes(template);
 }
@@ -5979,7 +5988,48 @@ var init_history = __esm({
 });
 
 // src/subagents/designExpert/index.ts
-var DESCRIPTION, designExpertTool;
+async function runDesignExpert(opts, context) {
+  const history = context.conversationMessages ? getSubAgentHistory(context.conversationMessages, "visualDesignExpert") : [];
+  return runSubAgent({
+    system: getDesignExpertPrompt(context.onboardingState),
+    task: opts.task,
+    history: history.length > 0 ? history : void 0,
+    tools: opts.enableWrite ? DESIGN_EXPERT_RENDER_TOOLS : DESIGN_EXPERT_TOOLS,
+    externalTools: /* @__PURE__ */ new Set(),
+    executeTool: (name, input, toolCallId, onLog, sams) => {
+      const childCtx = toolCallId ? { ...deriveContext(context, toolCallId), subAgentMessages: sams } : { ...context, subAgentMessages: sams };
+      if (COMMON_READ_TOOL_NAMES.has(name)) {
+        return executeTool(name, input, childCtx);
+      }
+      if (opts.enableWrite && RENDER_WRITE_TOOL_NAMES.has(name)) {
+        return executeTool(name, input, childCtx);
+      }
+      return executeDesignExpertTool(name, input, childCtx, toolCallId, onLog);
+    },
+    apiConfig: context.apiConfig,
+    model: resolveModel("visualDesignExpert", context.models, context.model),
+    subAgentId: "visualDesignExpert",
+    signal: context.signal,
+    parentToolId: context.toolCallId,
+    requestId: context.requestId,
+    onEvent: context.onEvent,
+    resolveExternalTool: context.resolveExternalTool,
+    toolRegistry: context.toolRegistry,
+    background: opts.background,
+    onBackgroundComplete: opts.background ? (bgResult) => {
+      context.onBackgroundComplete?.(
+        context.toolCallId,
+        opts.reportingName ?? "visualDesignExpert",
+        bgResult.text,
+        bgResult.messages
+      );
+    } : void 0
+  });
+}
+async function runDesignExpertRender(opts, context) {
+  return runDesignExpert({ ...opts, enableWrite: true }, context);
+}
+var DESCRIPTION, RENDER_WRITE_TOOL_NAMES, DESIGN_EXPERT_RENDER_TOOLS, designExpertTool;
 var init_designExpert = __esm({
   "src/subagents/designExpert/index.ts"() {
     "use strict";
@@ -5990,9 +6040,17 @@ var init_designExpert = __esm({
     init_prompt3();
     init_history();
     init_surfaces();
+    init_writeFile();
+    init_editFile();
     DESCRIPTION = `
 Visual design expert. Describe the situation and what you need \u2014 the agent decides what to deliver. It reads the spec files automatically. Include relevant user requirements and context it can't get from the spec, but do not list specific deliverables or tell it how to do its job. Do not suggest implementation details or ideas - only relay what is needed.
 `.trim();
+    RENDER_WRITE_TOOL_NAMES = /* @__PURE__ */ new Set(["writeFile", "editFile"]);
+    DESIGN_EXPERT_RENDER_TOOLS = [
+      ...DESIGN_EXPERT_TOOLS,
+      writeFileTool.definition,
+      editFileTool.definition
+    ];
     designExpertTool = {
       clearable: false,
       definition: {
@@ -6017,45 +6075,13 @@ Visual design expert. Describe the situation and what you need \u2014 the agent
         if (!context) {
           return "Error: visual design expert requires execution context";
         }
-        const history = context.conversationMessages ? getSubAgentHistory(context.conversationMessages, "visualDesignExpert") : [];
-        const result = await runSubAgent({
-          system: getDesignExpertPrompt(context.onboardingState),
-          task: input.task,
-          history: history.length > 0 ? history : void 0,
-          tools: DESIGN_EXPERT_TOOLS,
-          externalTools: /* @__PURE__ */ new Set(),
-          executeTool: (name, input2, toolCallId, onLog, sams) => {
-            const childCtx = toolCallId ? { ...deriveContext(context, toolCallId), subAgentMessages: sams } : { ...context, subAgentMessages: sams };
-            if (COMMON_READ_TOOL_NAMES.has(name)) {
-              return executeTool(name, input2, childCtx);
-            }
-            return executeDesignExpertTool(
-              name,
-              input2,
-              childCtx,
-              toolCallId,
-              onLog
-            );
+        const result = await runDesignExpert(
+          {
+            task: input.task,
+            background: input.background
           },
-          apiConfig: context.apiConfig,
-          model: resolveModel("visualDesignExpert", context.models, context.model),
-          subAgentId: "visualDesignExpert",
-          signal: context.signal,
-          parentToolId: context.toolCallId,
-          requestId: context.requestId,
-          onEvent: context.onEvent,
-          resolveExternalTool: context.resolveExternalTool,
-          toolRegistry: context.toolRegistry,
-          background: input.background,
-          onBackgroundComplete: input.background ? (bgResult) => {
-            context.onBackgroundComplete?.(
-              context.toolCallId,
-              "visualDesignExpert",
-              bgResult.text,
-              bgResult.messages
-            );
-          } : void 0
-        });
+          context
+        );
         context.subAgentMessages?.set(context.toolCallId, result.messages);
         return result.text;
       }
@@ -6168,16 +6194,25 @@ ${unifiedDiff(filePath, oldContent, "")}`;
       const filePath = resolve("pitch.html");
       try {
         fs18.mkdirSync(ROADMAP_DIR, { recursive: true });
-        const existing = fs18.existsSync(filePath) ? fs18.readFileSync(filePath, "utf-8").trim() : "";
-        const currentDeck = existing || PITCH_DECK_SHELL;
+        const exists = fs18.existsSync(filePath);
+        const before = exists ? fs18.statSync(filePath).mtimeMs : null;
+        const delivery = exists ? `### Your deliverable
+The pitch deck already exists at \`${filePath}\`. Read it, then update it for the new <pitch_content>, keeping the presentation scaffolding intact \u2014 change only what needs to change.
+
+Reply with a one-line summary of what you changed \u2014 not the HTML.` : `### Your deliverable
+Write the complete pitch deck to \`${filePath}\`. It does not exist yet \u2014 start from this scaffold, keeping its progress bar, chevron navigation, keyboard navigation, and transition mechanics intact:
+
+<pitch_deck_shell>
+${PITCH_DECK_SHELL}
+</pitch_deck_shell>
+
+Reply with a one-line summary of what you wrote \u2014 not the HTML.`;
         const task = `
 <pitch_content>${input.task}</pitch_content>
 
-<current_deck>${currentDeck}</current_deck>
-
 We are building the pitch deck for the app. Using the provided <pitch_content>, as well as the app's spec data, think about what would make a compelling, interactive, self-contained horizontally-scrolling HTML slide deck for this product. Keep it simple, clean, powerful. Giant text, large logo, big, bold stats and claims. Edit the content as necessary to create the most impactful, bold, and beautiful slides. This should not feel like an essay, and it should not feel like a landing page \u2014 it should feel like a modern interactive presentation that leaves the user wowed by the product and excited about its future.
 
-Use <current_deck> as your starting point and replace or update the content as needed, maintaining the bones of the presentation scaffolding. Always keep the progress bar, chevron navigation, and keyboard navigation - they are part of the scaffold.
+Maintain the bones of the presentation scaffolding. Always keep the progress bar, chevron navigation, and keyboard navigation - they are part of the scaffold.
 
 ### Rules
 - The deck must be a single HTML file \u2014 it will be rendered in an iframe.
@@ -6187,14 +6222,18 @@ Use <current_deck> as your starting point and replace or update the content as n
 - Code must be clean, bug free, and easy to parse. Use GSAP for animations. Pay close attention to layout and alignment to make sure everything is perfect.
 - Keep the progress bar and edge chevrons from the shell \u2014 they are part of the navigation UX.
 
-Respond only with the complete HTML file and absolutely no other text. Your response will be written directly to an html file.`;
-        const result = await designExpertTool.execute({ task }, context);
-        const htmlMatch = result.match(
-          /```(?:html|wireframe)\n([\s\S]*?)```/
-        );
-        const html = htmlMatch ? htmlMatch[1].trim() : result;
-        fs18.writeFileSync(filePath, html, "utf-8");
-        return `Pitch deck written successfully.`;
+${delivery}`;
+        const result = await runDesignExpertRender({ task }, context);
+        context.subAgentMessages?.set(context.toolCallId, result.messages);
+        if (!fs18.existsSync(filePath)) {
+          return `Error: the design expert did not write ${filePath}. Its reply was:
+${result.text}`;
+        }
+        if (before !== null && fs18.statSync(filePath).mtimeMs === before) {
+          return `Error: the pitch deck at ${filePath} was not modified. The design expert's reply was:
+${result.text}`;
+        }
+        return `Pitch deck written to ${filePath}. ${result.text}`;
       } catch (err) {
         return `Error generating pitch deck: ${err.message}`;
       }
@@ -6489,6 +6528,22 @@ var init_scrapeWebUrl2 = __esm({
 
 // src/tools/spec/writeBuildOverview.ts
 import fs19 from "fs";
+function initialDelivery() {
+  return `### Your deliverable
+Write the complete Build Overview to \`${OVERVIEW_FILE}\`. The file does not exist yet \u2014 start from this scaffold, which carries the technical hygiene for the iframed render context (keep the viewport meta and the reset). Layout, sections, type, and styling are yours to compose.
+
+<overview_shell>
+${OVERVIEW_SHELL}
+</overview_shell>
+
+Reply with a one-line summary of what you wrote \u2014 not the HTML.`;
+}
+function refreshDelivery() {
+  return `### Your deliverable
+The Build Overview already exists at \`${OVERVIEW_FILE}\`. Read it, then update it to reflect <overview_copy>, preserving its established skin \u2014 change only what the copy changed.
+
+Reply with a one-line summary of what you changed \u2014 not the HTML.`;
+}
 var OVERVIEW_FILE, DESIGN_BRIEF, OVERVIEW_SHELL, buildOverviewTool;
 var init_writeBuildOverview = __esm({
   "src/tools/spec/writeBuildOverview.ts"() {
@@ -6497,7 +6552,7 @@ var init_writeBuildOverview = __esm({
     OVERVIEW_FILE = "src/overview.html";
     DESIGN_BRIEF = `We are building the Build Overview for this app \u2014 the home page of its Spec tab. It is a calm, dense, one-page reference of everything the app actually contains, including the parts the user can't see. It renders flush inside the Spec tab's content panel (the IDE supplies the surrounding nav).
 
-Take the plain-language copy in <overview_copy> and lay it out and skin it into a single, beautiful, self-contained HTML document in the app's own brand. If <current_overview> is non-empty, use it as your starting point and preserve its established skin, updating only what the copy changed.
+Take the plain-language copy in <overview_copy> and lay it out and skin it into a single, beautiful, self-contained HTML document in the app's own brand.
 
 ### The single hard rule
 The copy in <overview_copy> is final \u2014 it was authored and edited before it reached you. Treat it as locked content to typeset, not a draft to improve. Reproduce the words exactly: do not rewrite, rephrase, shorten, expand, reorder, or "polish" them, and do not run them through any copy tool. This is the opposite of your usual role \u2014 here you own layout, typography, and visual design only, and the words (every number, name, label, claim, and sentence) are fixed. A single changed word or wrong number breaks this document's purpose.
@@ -6512,9 +6567,7 @@ The copy in <overview_copy> is final \u2014 it was authored and edited before it
 
 ### Constraints
 - A single self-contained HTML file. Fonts may load from a CDN; everything else (CSS, the logo SVG) is inline.
-- Responsive: fills the embedded panel width and collapses gracefully at narrow widths.
-
-Respond only with the complete HTML file and absolutely no other text. Your response will be written directly to src/overview.html.`;
+- Responsive: fills the embedded panel width and collapses gracefully at narrow widths.`;
     OVERVIEW_SHELL = `<!DOCTYPE html>
 <html lang="en">
 <head>
@@ -6559,21 +6612,29 @@ Respond only with the complete HTML file and absolutely no other text. Your resp
         if (!content) {
           return "Error: writeBuildOverview requires non-empty `content` (the overview copy).";
         }
-        try {
-          const existing = fs19.existsSync(OVERVIEW_FILE) ? fs19.readFileSync(OVERVIEW_FILE, "utf-8").trim() : "";
-          const currentOverview = existing || OVERVIEW_SHELL;
-          const task = `<overview_copy>${content}</overview_copy>
+        const exists = fs19.existsSync(OVERVIEW_FILE);
+        const task = `<overview_copy>${content}</overview_copy>
 
-<current_overview>${currentOverview}</current_overview>
+${DESIGN_BRIEF}
 
-${DESIGN_BRIEF}`;
-          const result = await designExpertTool.execute({ task }, context);
-          const htmlMatch = result.match(
-            /```(?:html|wireframe)\n([\s\S]*?)```/
-          );
-          const html = htmlMatch ? htmlMatch[1].trim() : result;
-          fs19.writeFileSync(OVERVIEW_FILE, html, "utf-8");
-          return "Build overview written successfully to src/overview.html.";
+${exists ? refreshDelivery() : initialDelivery()}`;
+        try {
+          if (exists) {
+            input.background = true;
+            const result2 = await runDesignExpertRender(
+              { task, background: true, reportingName: "writeBuildOverview" },
+              context
+            );
+            context.subAgentMessages?.set(context.toolCallId, result2.messages);
+            return result2.text;
+          }
+          const result = await runDesignExpertRender({ task }, context);
+          context.subAgentMessages?.set(context.toolCallId, result.messages);
+          if (!fs19.existsSync(OVERVIEW_FILE)) {
+            return `Error: the design expert did not write ${OVERVIEW_FILE}. Its reply was:
+${result.text}`;
+          }
+          return `Build overview written to ${OVERVIEW_FILE}. ${result.text}`;
         } catch (err) {
           return `Error generating build overview: ${err.message}`;
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.229",
+  "version": "0.1.231",
   "description": "Remy coding agent",
   "repository": {
     "type": "git",