@mindstudio-ai/remy 0.1.278 → 0.1.279

package/README.md

@@ -86,6 +86,7 @@ Available in all onboarding states. Used for authoring and editing MSFM specs in
 | `editsFinished` | Signal that file edits are complete for live preview |
 | `runScenario` | Run a scenario to seed the dev database with test data |
 | `runMethod` | Run a method in the dev environment and return the result |
+| `testJewel` | Run a method's jewel against a test input and return its pair record |
 | `screenshot` | Capture a screenshot of the app preview and get a description of what's on screen |
 | `runAutomatedBrowserTest` | Run an automated browser test against the live preview with DOM snapshots and interaction execution (sub-agent) |
 

package/dist/automatedActions/approveInitialPlan.md

@@ -5,9 +5,7 @@ next: buildFromInitialSpec
 
 The user has approved your initial plan. Time to bring it to life.
 
-First, call `setProjectOnboardingState({ state: "building" })` to transition the UI.
-
-Then, write the full spec. Follow the instructions in <spec_authoring_instructions> to write all spec files: app.md, web.md, brand (visual.md, colors.md, typography.md, voice.md), and any others the project needs. Consult the design expert for brand and visual direction. Be thorough: the spec drives everything downstream.
+First, write the full spec. Follow the instructions in <spec_authoring_instructions> to write all spec files: app.md, web.md, brand (visual.md, colors.md, typography.md, voice.md), and any others the project needs. Consult the design expert for brand and visual direction. Be thorough: the spec drives everything downstream.
 
 As the final step of spec authoring, dispatch `productVision` with `background: true` to seed the initial roadmap and generate the pitch deck. It runs long and it keeps working after this turn ends, reporting back later as an automated message — so hand it off and move on rather than waiting on it.
 

package/dist/automatedActions/postBuildPolish.md

@@ -16,4 +16,4 @@ When everything is working and polished:
 1. Write the Build Overview. Author the full copy of everything this build actually produced — the data stores and what each holds, the backend operations, the interfaces, any access and role boundaries, background jobs, and seeded scenarios, including the parts the user can't see — in plain, calm, present-tense language, with real names and exact counts. Then call `writeBuildOverview` to render it. Do this now, before compacting, while the build is still fresh in context.
 2. Use `productVision` to mark the MVP roadmap item as done.
 3. Call `compactConversation` to summarize the build session and free up context for the next phase of work.
-4. Call `setProjectOnboardingState({ state: "buildComplete" })`. This triggers the reveal experience on the frontend, where the user sees their finished app and its Build Overview for the first time.
+4. Call `markBuildComplete`. The user lands on the Build Overview — their first look at the finished app — and the editor fully unlocks.