@mindstudio-ai/remy 0.1.71 → 0.1.73

package/dist/headless.js

@@ -5916,6 +5916,7 @@ ${xmlParts}
       return;
     }
     if (action === "get_history") {
+      applyPendingBlockUpdates();
       dispatchSimple(requestId, "history", () => handleGetHistory(state));
       return;
     }

package/dist/index.js

@@ -6531,6 +6531,7 @@ ${xmlParts}
       return;
     }
     if (action === "get_history") {
+      applyPendingBlockUpdates();
       dispatchSimple(requestId, "history", () => handleGetHistory(state));
       return;
     }

package/dist/prompt/static/team.md

@@ -40,7 +40,7 @@ Always consult the code sanity check before writing code in initialCodegen with
 
 For verifying complex stateful interactions: multi-step form submissions, auth flows, real-time updates, flows that require specific data/role setup. This spins up a full chrome browser automation — it's heavyweight and takes minutes to complete a full test. Do not use it for basic rendering or navigation checks. If you can verify something with a screenshot or by reading the code, do that instead. Don't run it constantly after making small changes - save it for meaningful work. Run a scenario first to seed test data and set user roles. The user is able to watch QA work on their screen via a live browser preview - the cursor will move, type, etc - so you can also use this to demo functionality to the user and help them understand how to use their app.
 
-The QA agent can see the screen. Describe what to test, not how — it will figure out what to click, what to check, and what values to use.
+The QA agent can see the screen. Describe what to test, not how — it will figure out what to click, what to check, and what values to use. Never give it explicit values to use when filling out forms or creating accounts - it will use its own judgement (and sometimes it needs to use specific values to trigger dev-mode bypasses of things like login verification codes).
 
 ### Background Execution
 

package/dist/subagents/browserAutomation/prompt.md

@@ -7,7 +7,7 @@ You are a browser smoke test agent. You verify that features work end to end by
 The user is watching the automation happen on their screen in real-time. When typing into forms or inputs, behave like a realistic user of this specific app. Use the app context (if provided) to understand the audience and tone. Type the way that audience would actually type — not formal, not robotic. The app developer's name is Remy - you must use that and the email remy@mindstudio.ai as the basis for any testing that requires a persona.
 
 ### Auth Testing
-When the app has a login or signup flow, you must use `remy@mindstudio.ai` for email and `+15551234567` for phone number. In the dev environment, verification codes are bypassed — enter any 6-digit code (e.g., `123456`) and it will be accepted. If the content you are trying to test is gated behind auth, always use these credentials to login and continue testing.
+When the app has a login or signup flow, you must use `remy@mindstudio.ai` for email and `+15551234567` for phone number. In the dev environment, verification codes are bypassed for this email address only and any 555-prefixed phone number — enter any 6-digit code (e.g., `123456`) and it will be accepted. If the content you are trying to test is gated behind auth, always use these credentials to login and continue testing.
 
 ## Browser Commands
 ### Snapshot format

package/dist/subagents/designExpert/prompts/images.md

@@ -61,6 +61,9 @@ Remember: It's 2026. Everything is lifestyle and editorial these days. Even a la
 
 Default to photography with real subjects — people, scenes, moments, environments. Use editorial and fashion photography vocabulary in your prompts. When abstract art is the right call (textures, editorial collages, gradient art), make it bold and intentional, not generic gradient blobs.
 
+#### Match style to context
+Editorial photography is the right call for hero images, landing pages, marketing sites, and branding. But when generating images for scenario seed data — sample posts, user uploads, profile content, anything that's supposed to look like a real user created it — the target is authentic user-generated content, not a photographer's portfolio. A social app's seed photos should look like they came from someone's phone camera roll in 2026: well-lit because the phone's computational photography is good, but casually framed, slightly imperfect, real-life backgrounds. Think "my friend posted this on Instagram" not "Unsplash top pick." The difference between a compelling demo and a fake-feeling one is whether the seed content feels like real people made it.
+
 The developer should never need to source their own imagery. Always provide URLs.
 
 ### When to use images

package/dist/subagents/designExpert/tools/images/enhance-image-prompt.md

@@ -44,6 +44,8 @@ For photorealistic images, be specific about:
 - Camera: close-up, wide angle, shallow depth of field, slightly grainy, film texture
 - Mood: the emotional quality — intimate, dramatic, serene, energetic
 
+**Casual / phone photography:** When the brief calls for candid, user-generated, or social-media-style photos, steer away from professional photography language. Instead describe the qualities of a good 2026 smartphone photo: sharp subject with computational HDR, natural ambient lighting, slightly busy or imperfect backgrounds, centered or off-center casual framing, no deliberate composition or artistic bokeh. The subject should look like someone pointed their phone and tapped — not posed, not art-directed. Describe it as "phone photo" or "iPhone photo" style, not "digital photography with shallow depth of field." Real people's photos are well-lit (phones are good now) but unpolished — a messy kitchen counter in frame, a friend mid-laugh with eyes half-closed, a dog blurry because it moved. That imperfection is what makes them feel authentic.
+
 ## Output
 
 Respond with ONLY the enhanced prompt. 3-5 sentences maximum. Be specific and visual, not abstract or conceptual.

package/package.json

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