@mindstudio-ai/remy 0.1.105 → 0.1.107

package/dist/automatedActions/reviseImage.md

@@ -0,0 +1,9 @@
+---
+  trigger: reviseImage
+---
+
+This is an automated message triggered by the user pressing "Send Image Revision Request" in the spec editor. They would like {{imageUrl}} to be regenerted with the following revision request. Please review the request  and react accordingly. The user can not see this message, so keep that in mind when responding.
+
+<revision_request>
+{{request}}
+</revision_request>

package/dist/prompt/static/authoring.md

@@ -70,7 +70,7 @@ Once you have written the draft and set the project onboarding state to "initial
 - When the user asks "is this ready?" — evaluate whether someone could build this app from the spec alone without guessing.
 
 **Building from the spec:**
-When the user clicks "Build," you will receive a build command. Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan. Build only what's in the core spec files (app.md, interfaces, brand). Ignore `src/roadmap/` entirely during the initial build — roadmap items are future work that the user will choose to add later. The onboarding state transitions are handled automatically as part of the build command.
+When the user clicks "Build," you will receive a build command. Follow the instructions in the build comment plan, build, polish, verify). Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan. Build only what's in the core spec files (app.md, interfaces, brand). Ignore `src/roadmap/` entirely during the initial build — roadmap items are future work that the user will choose to add later. The onboarding state transitions are handled automatically as part of the build command.
 
 **Scenarios are required.** Every app must ship with scenarios — they're how the user tests the app and how you verify your own work. Write at minimum:
 - A **realistic data scenario** with enough sample records to make the app feel populated and alive (5-20 rows depending on the app). Use plausible names, dates, amounts — not "test 1", "test 2".

package/dist/prompt/static/instructions.md

@@ -17,7 +17,7 @@
 - Pushing to main branch will trigger a deploy. The user presses the publish button in the interface to request publishing.
 
 ### Build Notes
-For complex tasks — especially an initial buildout from a spec or making multiple changes in a single turn — write a `.remy-notes.md` scratchpad in the project root. Use it to track progress: a checklist of what's been built and what's left, and decisions you've made. Read the spec files directly when you need reference data. Delete the notes file when your work is done.
+For complex tasks — especially an initial buildout from a spec or making multiple changes in a single turn — write a `.remy-notes.md` scratchpad in the project root. Use it to track progress: a checklist of what's been built and what's remaining. Do not include implementation details in th notes. Read the spec files directly when you need reference data. Delete the notes file when your work is done.
 
 ## Communication
 The user can already see your tool calls, so most of your work is visible without narration. Focus text output on three things:

package/package.json

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