@mindstudio-ai/remy 0.1.154 → 0.1.156

package/dist/automatedActions/postBuildPolish.md

@@ -5,11 +5,11 @@
 This is an automated follow-up after the initial build. The code is written and verified. Now it's time to polish and finalize so we can deliver something beautiful and magical as the user's first experience with our work.
 
 ## Polishing
-Take a step back and do an explicit polish pass. Re-read the spec files and the design expert's guidance, then walk through each frontend file looking for design details that got skipped in the initial build: layout animations, transitions, hover states, micro-interactions, spring physics, entrance reveals, gesture handling, layout issues, responsiveness, and anything else. We need this to feel truly amazing and wow the user - it's worth it to take the time to get it right.
+Take a step back and do an explicit polish pass focused on UX and interaction quality. Re-read the spec files and the design expert's guidance, then walk through each frontend file looking for behavioral details that got skipped in the initial build: layout animations, transitions, hover states, micro-interactions, spring physics, entrance reveals, gesture handling, responsiveness across breakpoints, focus and keyboard handling, and loading/empty/error states.
 
 The initial build prioritizes getting everything connected and functional, but this pass closes the gap between "it works" and "it feels great." In many ways this is *the* most important part of the initial build, as the user's first experience of the deliverable will set their expectations for every iteration that follows. Don't mess this up.
 
-When you have finished, ask the `visualDesignExpert` to take a screenshot and verify that the visual design looks correct. Fix any issues it flags. We want the user's first time seeing the finished product to truly wow them.
+The visual assets — photography, generated images, brand colors, typography — were already locked in upstream by the design expert during intake. Treat them as fixed inputs to this pass. Polish the *behavior* of the page, not the pixels of generated imagery.
 
 ## Finalizing
 When everything is working and polished:

package/dist/headless.js

@@ -835,7 +835,7 @@ async function generateSummary(apiConfig, name, compactionPrompt, messagesToSumm
   let summaryText = "";
   const useMainCache = !!mainSystem;
   const system = useMainCache ? mainSystem : compactionPrompt;
-  const tools2 = useMainCache ? mainTools ?? [] : [];
+  const tools2 = [];
   const userContent = useMainCache ? `${compactionPrompt}
 
 ---
@@ -2078,11 +2078,12 @@ ${unifiedDiff(input.path, content, updated)}`;
 import { spawn as spawn2 } from "child_process";
 var DEFAULT_TIMEOUT_MS = 12e4;
 var DEFAULT_MAX_LINES3 = 500;
+var MAX_OUTPUT_BYTES = 3e4;
 var bashTool = {
   clearable: true,
   definition: {
     name: "bash",
-    description: "Run a shell command and return stdout + stderr. 120-second timeout by default (configurable). Use for: npm install/build/test, git operations, tsc --noEmit, or any CLI tool. Prefer dedicated tools over bash when available (use grep instead of bash + rg, readFile instead of bash + cat). Output is truncated to 500 lines by default.",
+    description: "Run a shell command and return stdout + stderr. 120-second timeout by default (configurable). Use for: npm install/build/test, git operations, tsc --noEmit, or any CLI tool. Prefer dedicated tools over bash when available (use grep instead of bash + rg, readFile instead of bash + cat). Output is truncated to 500 lines or 30KB, whichever comes first. If a command would emit a lot of data, narrow it down (grep, head/tail, --short flags) rather than reading everything.",
     inputSchema: {
       type: "object",
       properties: {
@@ -2138,12 +2139,32 @@ var bashTool = {
           }
           return;
         }
-        const lines = output.split("\n");
-        if (lines.length > maxLines) {
+        const totalBytes = Buffer.byteLength(output, "utf-8");
+        let truncated = output;
+        let byteTruncated = false;
+        if (totalBytes > MAX_OUTPUT_BYTES) {
+          truncated = Buffer.from(output, "utf-8").subarray(0, MAX_OUTPUT_BYTES).toString("utf-8");
+          byteTruncated = true;
+        }
+        const lines = truncated.split("\n");
+        const lineTruncated = lines.length > maxLines;
+        if (lineTruncated) {
+          truncated = lines.slice(0, maxLines).join("\n");
+        }
+        if (byteTruncated || lineTruncated) {
+          const reasons = [];
+          if (lineTruncated) {
+            reasons.push(`${maxLines} lines`);
+          }
+          if (byteTruncated) {
+            reasons.push(
+              `${(MAX_OUTPUT_BYTES / 1024).toFixed(0)}KB of ${(totalBytes / 1024).toFixed(0)}KB`
+            );
+          }
           resolve2(
-            lines.slice(0, maxLines).join("\n") + `
+            truncated + `
 
-(truncated at ${maxLines} lines of ${lines.length} total \u2014 increase maxLines to see more)`
+(truncated at ${reasons.join(" / ")} \u2014 narrow the command (grep, head/tail, smaller paths) instead of increasing limits)`
           );
         } else {
           resolve2(output);
@@ -2655,6 +2676,21 @@ ${opts.styleMap}
 ${TEXT_WRAP_DISCLAIMER}`;
   return p;
 }
+async function streamScreenshotAnalysis(opts) {
+  const { url, prompt, styleMap, onLog } = opts;
+  onLog?.(JSON.stringify({ url, analysis: null }));
+  const analysisPrompt = buildScreenshotAnalysisPrompt({ prompt, styleMap });
+  let accumulated = "";
+  const analysis = await analyzeImage({
+    prompt: analysisPrompt,
+    imageUrl: url,
+    onLog: (chunk) => {
+      accumulated += chunk;
+      onLog?.(JSON.stringify({ url, analysis: accumulated }));
+    }
+  });
+  return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
+}
 async function captureAndAnalyzeScreenshot(promptOrOptions) {
   let prompt;
   let existingUrl;
@@ -2689,16 +2725,12 @@ async function captureAndAnalyzeScreenshot(promptOrOptions) {
   if (prompt === false) {
     return url;
   }
-  const analysisPrompt = buildScreenshotAnalysisPrompt({
+  return streamScreenshotAnalysis({
+    url,
     prompt: prompt || void 0,
-    styleMap
-  });
-  const analysis = await analyzeImage({
-    prompt: analysisPrompt,
-    imageUrl: url,
+    styleMap,
     onLog
   });
-  return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
 }
 
 // src/tools/_helpers/browserLock.ts
@@ -2718,9 +2750,10 @@ function startStatusWatcher(config) {
   const { apiConfig, getContext, onStatus, interval = 5e3, signal } = config;
   let inflight = false;
   let stopped = false;
+  let pauseCount = 0;
   const url = `${apiConfig.baseUrl}/_internal/v2/agent/remy/generate-status`;
   async function tick() {
-    if (stopped || signal?.aborted || inflight) {
+    if (stopped || signal?.aborted || inflight || pauseCount > 0) {
       return;
     }
     inflight = true;
@@ -2745,6 +2778,9 @@ function startStatusWatcher(config) {
       if (!data.label) {
         return;
       }
+      if (pauseCount > 0) {
+        return;
+      }
       onStatus(data.label);
     } catch {
     } finally {
@@ -2758,6 +2794,12 @@ function startStatusWatcher(config) {
     stop() {
       stopped = true;
       clearInterval(timer);
+    },
+    pause() {
+      pauseCount++;
+    },
+    resume() {
+      pauseCount = Math.max(0, pauseCount - 1);
     }
   };
 }
@@ -3613,7 +3655,7 @@ var screenshotTool = {
         },
         instructions: {
           type: "string",
-          description: "If the screenshot you need requires interaction first (dismissing a modal, clicking a tab, filling out a form, navigating a flow, getting through a login/auth checkpoint), describe the steps to get there. A browser automation agent will follow these instructions before capturing the screenshot - it can bypass auth and get right to where it needs to be if you tell it to authenticate as a test user and give it the path/screen to start its test at. You will always get back a full-height screenshot of the entire page. Do not attempt to scroll or capture specific areas. Only use instructions when you need to trigger stateful changes. Never describe what names or values to use when applying the isntructions - the browser automation agent must use its own values for it to work properly. If a specific auth role is required to access the content, be sure to note that - it can automatically assume it for the purpose of testing."
+          description: "If the screenshot you need requires interaction first (dismissing a modal, clicking a tab, filling out a form, navigating a flow, getting through a login/auth checkpoint), describe the steps to get there. A browser automation agent will follow these instructions before capturing the screenshot - it can bypass auth and get right to where it needs to be if you tell it to authenticate as a test user and give it the path/screen to start its test at. You will always get back a full-height screenshot of the entire page. Do not attempt to scroll or capture specific areas. Never describe what names or values to use when applying the instructions - the browser automation agent must use its own values for it to work properly. If a specific auth role is required to access the content, be sure to note that - it can automatically assume it for the purpose of testing. Use only when interaction is required to *reach* the state you want to capture \u2014 log in, dismiss a modal, switch a tab, follow a route. If your steps are exercising the app's functionality across multiple states (running flows, asserting behavior under interaction, multi-step QA), use `runAutomatedBrowserTest` instead."
         }
       }
     }
@@ -3642,20 +3684,12 @@ var screenshotTool = {
         if (!url) {
           return `Error: browser navigation completed but no screenshot URL was returned. Agent output: ${resultStr}`;
         }
-        const analysisPrompt = buildScreenshotAnalysisPrompt({
+        return await streamScreenshotAnalysis({
+          url,
           prompt: input.prompt,
-          styleMap
-        });
-        const analysis = await analyzeImage({
-          prompt: analysisPrompt,
-          imageUrl: url,
+          styleMap,
           onLog: context?.onLog
         });
-        return JSON.stringify({
-          url,
-          analysis,
-          ...styleMap ? { styleMap } : {}
-        });
       }
       const release = await acquireBrowserLock();
       try {
@@ -3973,20 +4007,12 @@ async function execute5(input, onLog, context) {
       if (!url) {
         return `Error: browser navigation completed but no screenshot URL was returned. Agent output: ${resultStr}`;
       }
-      const analysisPrompt = buildScreenshotAnalysisPrompt({
+      return await streamScreenshotAnalysis({
+        url,
         prompt: input.prompt,
-        styleMap
-      });
-      const analysis = await analyzeImage({
-        prompt: analysisPrompt,
-        imageUrl: url,
+        styleMap,
         onLog
       });
-      return JSON.stringify({
-        url,
-        analysis,
-        ...styleMap ? { styleMap } : {}
-      });
     } catch (err) {
       return `Error taking interactive screenshot: ${err.message}`;
     }
@@ -5456,6 +5482,11 @@ var EXTERNAL_TOOLS = /* @__PURE__ */ new Set([
   "browserCommand",
   "setProjectMetadata"
 ]);
+var USER_BLOCKING_EXTERNAL_TOOLS = /* @__PURE__ */ new Set([
+  "promptUser",
+  "presentPublishPlan",
+  "confirmDestructiveAction"
+]);
 function createAgentState() {
   return { messages: [] };
 }
@@ -5545,6 +5576,8 @@ async function runTurn(params) {
     let subAgentText = "";
     let currentToolNames = "";
     const statusWatcher = isFirstMessage ? { stop() {
+    }, pause() {
+    }, resume() {
     } } : startStatusWatcher({
       apiConfig,
       getContext: () => {
@@ -5849,7 +5882,17 @@ async function runTurn(params) {
                 toolCallId: tc.id,
                 name: tc.name
               });
-              result = await resolveExternalTool(tc.id, tc.name, input);
+              const blocksUser = USER_BLOCKING_EXTERNAL_TOOLS.has(tc.name);
+              if (blocksUser) {
+                statusWatcher.pause();
+              }
+              try {
+                result = await resolveExternalTool(tc.id, tc.name, input);
+              } finally {
+                if (blocksUser) {
+                  statusWatcher.resume();
+                }
+              }
             } else {
               result = await executeTool(tc.name, input, {
                 apiConfig,

package/dist/index.js

@@ -1550,7 +1550,7 @@ async function generateSummary(apiConfig, name, compactionPrompt, messagesToSumm
   let summaryText = "";
   const useMainCache = !!mainSystem;
   const system = useMainCache ? mainSystem : compactionPrompt;
-  const tools2 = useMainCache ? mainTools ?? [] : [];
+  const tools2 = [];
   const userContent = useMainCache ? `${compactionPrompt}
 
 ---
@@ -2264,17 +2264,18 @@ ${unifiedDiff(input.path, content, updated)}`;
 
 // src/tools/code/bash.ts
 import { spawn as spawn2 } from "child_process";
-var DEFAULT_TIMEOUT_MS, DEFAULT_MAX_LINES3, bashTool;
+var DEFAULT_TIMEOUT_MS, DEFAULT_MAX_LINES3, MAX_OUTPUT_BYTES, bashTool;
 var init_bash = __esm({
   "src/tools/code/bash.ts"() {
     "use strict";
     DEFAULT_TIMEOUT_MS = 12e4;
     DEFAULT_MAX_LINES3 = 500;
+    MAX_OUTPUT_BYTES = 3e4;
     bashTool = {
       clearable: true,
       definition: {
         name: "bash",
-        description: "Run a shell command and return stdout + stderr. 120-second timeout by default (configurable). Use for: npm install/build/test, git operations, tsc --noEmit, or any CLI tool. Prefer dedicated tools over bash when available (use grep instead of bash + rg, readFile instead of bash + cat). Output is truncated to 500 lines by default.",
+        description: "Run a shell command and return stdout + stderr. 120-second timeout by default (configurable). Use for: npm install/build/test, git operations, tsc --noEmit, or any CLI tool. Prefer dedicated tools over bash when available (use grep instead of bash + rg, readFile instead of bash + cat). Output is truncated to 500 lines or 30KB, whichever comes first. If a command would emit a lot of data, narrow it down (grep, head/tail, --short flags) rather than reading everything.",
         inputSchema: {
           type: "object",
           properties: {
@@ -2330,12 +2331,32 @@ var init_bash = __esm({
               }
               return;
             }
-            const lines = output.split("\n");
-            if (lines.length > maxLines) {
+            const totalBytes = Buffer.byteLength(output, "utf-8");
+            let truncated = output;
+            let byteTruncated = false;
+            if (totalBytes > MAX_OUTPUT_BYTES) {
+              truncated = Buffer.from(output, "utf-8").subarray(0, MAX_OUTPUT_BYTES).toString("utf-8");
+              byteTruncated = true;
+            }
+            const lines = truncated.split("\n");
+            const lineTruncated = lines.length > maxLines;
+            if (lineTruncated) {
+              truncated = lines.slice(0, maxLines).join("\n");
+            }
+            if (byteTruncated || lineTruncated) {
+              const reasons = [];
+              if (lineTruncated) {
+                reasons.push(`${maxLines} lines`);
+              }
+              if (byteTruncated) {
+                reasons.push(
+                  `${(MAX_OUTPUT_BYTES / 1024).toFixed(0)}KB of ${(totalBytes / 1024).toFixed(0)}KB`
+                );
+              }
               resolve2(
-                lines.slice(0, maxLines).join("\n") + `
+                truncated + `
 
-(truncated at ${maxLines} lines of ${lines.length} total \u2014 increase maxLines to see more)`
+(truncated at ${reasons.join(" / ")} \u2014 narrow the command (grep, head/tail, smaller paths) instead of increasing limits)`
               );
             } else {
               resolve2(output);
@@ -2922,6 +2943,21 @@ ${opts.styleMap}
 ${TEXT_WRAP_DISCLAIMER}`;
   return p;
 }
+async function streamScreenshotAnalysis(opts) {
+  const { url, prompt, styleMap, onLog } = opts;
+  onLog?.(JSON.stringify({ url, analysis: null }));
+  const analysisPrompt = buildScreenshotAnalysisPrompt({ prompt, styleMap });
+  let accumulated = "";
+  const analysis = await analyzeImage({
+    prompt: analysisPrompt,
+    imageUrl: url,
+    onLog: (chunk) => {
+      accumulated += chunk;
+      onLog?.(JSON.stringify({ url, analysis: accumulated }));
+    }
+  });
+  return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
+}
 async function captureAndAnalyzeScreenshot(promptOrOptions) {
   let prompt;
   let existingUrl;
@@ -2956,16 +2992,12 @@ async function captureAndAnalyzeScreenshot(promptOrOptions) {
   if (prompt === false) {
     return url;
   }
-  const analysisPrompt = buildScreenshotAnalysisPrompt({
+  return streamScreenshotAnalysis({
+    url,
     prompt: prompt || void 0,
-    styleMap
-  });
-  const analysis = await analyzeImage({
-    prompt: analysisPrompt,
-    imageUrl: url,
+    styleMap,
     onLog
   });
-  return JSON.stringify({ url, analysis, ...styleMap ? { styleMap } : {} });
 }
 var SCREENSHOT_ANALYSIS_PROMPT, TEXT_WRAP_DISCLAIMER;
 var init_screenshot = __esm({
@@ -3003,9 +3035,10 @@ function startStatusWatcher(config) {
   const { apiConfig, getContext, onStatus, interval = 5e3, signal } = config;
   let inflight = false;
   let stopped = false;
+  let pauseCount = 0;
   const url = `${apiConfig.baseUrl}/_internal/v2/agent/remy/generate-status`;
   async function tick() {
-    if (stopped || signal?.aborted || inflight) {
+    if (stopped || signal?.aborted || inflight || pauseCount > 0) {
       return;
     }
     inflight = true;
@@ -3030,6 +3063,9 @@ function startStatusWatcher(config) {
       if (!data.label) {
         return;
       }
+      if (pauseCount > 0) {
+        return;
+      }
       onStatus(data.label);
     } catch {
     } finally {
@@ -3043,6 +3079,12 @@ function startStatusWatcher(config) {
     stop() {
       stopped = true;
       clearInterval(timer);
+    },
+    pause() {
+      pauseCount++;
+    },
+    resume() {
+      pauseCount = Math.max(0, pauseCount - 1);
     }
   };
 }
@@ -3935,7 +3977,6 @@ var init_screenshot2 = __esm({
     "use strict";
     init_screenshot();
     init_browserLock();
-    init_analyzeImage();
     init_browserAutomation();
     screenshotTool = {
       clearable: true,
@@ -3959,7 +4000,7 @@ var init_screenshot2 = __esm({
             },
             instructions: {
               type: "string",
-              description: "If the screenshot you need requires interaction first (dismissing a modal, clicking a tab, filling out a form, navigating a flow, getting through a login/auth checkpoint), describe the steps to get there. A browser automation agent will follow these instructions before capturing the screenshot - it can bypass auth and get right to where it needs to be if you tell it to authenticate as a test user and give it the path/screen to start its test at. You will always get back a full-height screenshot of the entire page. Do not attempt to scroll or capture specific areas. Only use instructions when you need to trigger stateful changes. Never describe what names or values to use when applying the isntructions - the browser automation agent must use its own values for it to work properly. If a specific auth role is required to access the content, be sure to note that - it can automatically assume it for the purpose of testing."
+              description: "If the screenshot you need requires interaction first (dismissing a modal, clicking a tab, filling out a form, navigating a flow, getting through a login/auth checkpoint), describe the steps to get there. A browser automation agent will follow these instructions before capturing the screenshot - it can bypass auth and get right to where it needs to be if you tell it to authenticate as a test user and give it the path/screen to start its test at. You will always get back a full-height screenshot of the entire page. Do not attempt to scroll or capture specific areas. Never describe what names or values to use when applying the instructions - the browser automation agent must use its own values for it to work properly. If a specific auth role is required to access the content, be sure to note that - it can automatically assume it for the purpose of testing. Use only when interaction is required to *reach* the state you want to capture \u2014 log in, dismiss a modal, switch a tab, follow a route. If your steps are exercising the app's functionality across multiple states (running flows, asserting behavior under interaction, multi-step QA), use `runAutomatedBrowserTest` instead."
             }
           }
         }
@@ -3988,20 +4029,12 @@ var init_screenshot2 = __esm({
             if (!url) {
               return `Error: browser navigation completed but no screenshot URL was returned. Agent output: ${resultStr}`;
             }
-            const analysisPrompt = buildScreenshotAnalysisPrompt({
+            return await streamScreenshotAnalysis({
+              url,
               prompt: input.prompt,
-              styleMap
-            });
-            const analysis = await analyzeImage({
-              prompt: analysisPrompt,
-              imageUrl: url,
+              styleMap,
               onLog: context?.onLog
             });
-            return JSON.stringify({
-              url,
-              analysis,
-              ...styleMap ? { styleMap } : {}
-            });
           }
           const release = await acquireBrowserLock();
           try {
@@ -4335,20 +4368,12 @@ async function execute5(input, onLog, context) {
       if (!url) {
         return `Error: browser navigation completed but no screenshot URL was returned. Agent output: ${resultStr}`;
       }
-      const analysisPrompt = buildScreenshotAnalysisPrompt({
+      return await streamScreenshotAnalysis({
+        url,
         prompt: input.prompt,
-        styleMap
-      });
-      const analysis = await analyzeImage({
-        prompt: analysisPrompt,
-        imageUrl: url,
+        styleMap,
         onLog
       });
-      return JSON.stringify({
-        url,
-        analysis,
-        ...styleMap ? { styleMap } : {}
-      });
     } catch (err) {
       return `Error taking interactive screenshot: ${err.message}`;
     }
@@ -4372,7 +4397,6 @@ var init_screenshot3 = __esm({
     "use strict";
     init_screenshot();
     init_browserLock();
-    init_analyzeImage();
     init_browserAutomation();
     definition5 = {
       clearable: true,
@@ -6135,6 +6159,8 @@ async function runTurn(params) {
     let subAgentText = "";
     let currentToolNames = "";
     const statusWatcher = isFirstMessage ? { stop() {
+    }, pause() {
+    }, resume() {
     } } : startStatusWatcher({
       apiConfig,
       getContext: () => {
@@ -6439,7 +6465,17 @@ async function runTurn(params) {
                 toolCallId: tc.id,
                 name: tc.name
               });
-              result = await resolveExternalTool(tc.id, tc.name, input);
+              const blocksUser = USER_BLOCKING_EXTERNAL_TOOLS.has(tc.name);
+              if (blocksUser) {
+                statusWatcher.pause();
+              }
+              try {
+                result = await resolveExternalTool(tc.id, tc.name, input);
+              } finally {
+                if (blocksUser) {
+                  statusWatcher.resume();
+                }
+              }
             } else {
               result = await executeTool(tc.name, input, {
                 apiConfig,
@@ -6544,7 +6580,7 @@ async function runTurn(params) {
     }
   }
 }
-var log8, EXTERNAL_TOOLS;
+var log8, EXTERNAL_TOOLS, USER_BLOCKING_EXTERNAL_TOOLS;
 var init_agent = __esm({
   "src/agent.ts"() {
     "use strict";
@@ -6570,6 +6606,11 @@ var init_agent = __esm({
       "browserCommand",
       "setProjectMetadata"
     ]);
+    USER_BLOCKING_EXTERNAL_TOOLS = /* @__PURE__ */ new Set([
+      "promptUser",
+      "presentPublishPlan",
+      "confirmDestructiveAction"
+    ]);
   }
 });
 

package/dist/prompt/compiled/auth.md

@@ -208,6 +208,8 @@ auth.requireRole('admin');
 auth.requireRole('admin', 'approver');  // any of these
 ```
 
+**Require login: check `auth.userId`. Roles are RBAC** — only declare roles that map to real business distinctions (vendor/buyer/admin), and only check them when behavior should differ. Newly verified users have `roles: []` until your code assigns them.
+
 ### `auth.hasRole(...roles)`
 
 Returns `boolean`. Same logic as `requireRole` but doesn't throw.
@@ -375,4 +377,6 @@ Auth works the same in dev/preview as in production — real verification codes
 
 All other emails and phone numbers receive real codes. There is no dev-mode bypass, no fake code, and no way to skip verification. When testing auth flows in the preview, use one of the test bypasses above or a real email/phone.
 
+The `runMethod` tool's `userId: "testUser"` shortcut resolves to this same dev-bypass identity. The platform find-or-creates a real users-table row for it on first call and caches the row's UUID for the rest of the dev session. **`auth.userId` inside the method is that UUID — not the literal string `"testUser"`.** The user row already exists, so don't try to insert it. If you need the UUID to seed app-specific rows that reference it (profiles, preferences, foreign keys), read it from any method response or query the users table directly: `SELECT id FROM users WHERE email = 'remy@mindstudio.ai'` (or `phone = '+15555555555'` for SMS-auth apps).
+
 Browser automation tools (screenshots, automated browser tests) handle their own auth sessions. Scenarios seed database data but do not create browser auth sessions.

package/dist/prompt/static/coding.md

@@ -11,11 +11,13 @@ Run `lspDiagnostics` after every turn where you have edited code in any meaningf
 
 - Spot-check methods with `runMethod`. The dev database is a disposable snapshot that will have been seeded with scenario data, so don't worry about being destructive.
 - For frontend work, take a single `screenshot` to confirm the main view renders correctly or look at the browser log for any console errors in the user's preview.
-- Use `runAutomatedBrowserTest` to verify an interactive flow that you can't confirm from a screenshot, or when the user reports something broken that you can't identify from code alone.
+- Use `runAutomatedBrowserTest` to verify an interactive flow that you can't confirm from a screenshot, when the user reports something broken that you can't identify from code alone, or whenever the verification involves driving the app through multiple interactions.
 - If the browser is unavailable, skip the visual check and verify through methods, logs, and code instead. Browser unavailability is an infrastructure issue, not a code problem — don't try to diagnose or fix it.
 
 Aim for confidence that the core happy paths work. If the 80% case is solid, the remaining edge cases are likely fine and the user can surface them in chat. Don't screenshot every page, test every permutation, or verify every secondary flow. One or two runtime checks that confirm the app loads and data flows through is enough.
 
+When making mechanical edits as part of iterating with the user (e.g., moving elements, changing labels, small redesigns and refactors), don't re-screenshot to confirm, simply trust your code. Re-screenshot only when changes are structural enough that the visual outcome is genuinely uncertain (new layout, new component composition, new route), or when the user reports something visible that you can't see in the code.
+
 ### Process Logs
 
 Process logs are available at .logs/ in NDJSON format (one JSON object per line) for debugging. Each line has at minimum ts (unix millis) and msg fields, plus structured context like level, module, requestId, toolCallId where available. You can use `jq` to examine logs and debug failures. Tools like run method or run scenario execute synchronously, so log data will be available by the time those tools return their results to you, there is no need to `sleep` before querying logfiles.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.154",
+  "version": "0.1.156",
   "description": "MindStudio coding agent",
   "repository": {
     "type": "git",