@mindstudio-ai/remy 0.1.235 → 0.1.237

package/dist/headless.js

@@ -421,6 +421,13 @@ var MODEL_SURFACES = {
     modelType: "text",
     userPickable: true
   },
+  specSync: {
+    default: "claude-5-sonnet",
+    label: "Spec Sync Agent",
+    description: "Keeps your spec in sync with the code as you build, updating the affected sections in the background after changes.",
+    modelType: "text",
+    userPickable: true
+  },
   imageGeneration: {
     default: "seedream-4.5",
     label: "Image Generation",
@@ -3231,6 +3238,7 @@ async function runSubAgent(config) {
     requestId,
     history,
     background,
+    acquireLock,
     onBackgroundComplete,
     captureArtifacts
   } = config;
@@ -3623,7 +3631,15 @@ ${partial}` : "[INTERRUPTED] Agent was interrupted before producing output.",
     agentName: subAgentId || "agent",
     task
   });
-  wrapRun().then((finalResult) => {
+  const runDetached = async () => {
+    const release = acquireLock ? await acquireLock() : null;
+    try {
+      return await wrapRun();
+    } finally {
+      release?.();
+    }
+  };
+  runDetached().then((finalResult) => {
     toolRegistry?.unregister(parentToolId);
     onBackgroundComplete?.(finalResult);
   }).catch((err) => {
@@ -5571,6 +5587,102 @@ var codeSanityCheckTool = {
   }
 };
 
+// src/subagents/specSync/tools.ts
+var SPEC_SYNC_TOOLS = [
+  ...COMMON_READ_TOOLS,
+  readSpecTool.definition,
+  editSpecTool.definition,
+  writeSpecTool.definition
+];
+
+// src/subagents/specSync/lock.ts
+var lockQueue2 = Promise.resolve();
+function acquireSpecSyncLock() {
+  let release;
+  const next = new Promise((res) => {
+    release = res;
+  });
+  const wait = lockQueue2;
+  lockQueue2 = next;
+  return wait.then(() => release);
+}
+
+// src/subagents/specSync/index.ts
+var BASE_PROMPT5 = readAsset("subagents/specSync", "prompt.md");
+var MSFM_DOCS = `<mindstudio_flavored_markdown_spec_docs>
+${readAsset(
+  "prompt",
+  "compiled/msfm.md"
+)}
+</mindstudio_flavored_markdown_spec_docs>`;
+var specSyncTool = {
+  clearable: false,
+  backgroundOnly: true,
+  definition: {
+    name: "specSync",
+    description: "Reconcile the spec to bring it in line with code changes you have made. Provide a brief, bulleted list of what changed and why; it finds the affected spec sections and updates them to match. Always runs in the background \u2014 it returns immediately and reports back when done.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        task: {
+          type: "string",
+          description: "What you changed in the code and why, in plain language \u2014 the way you would explain it to a teammate. The specialist reads the spec itself and decides which sections to update; you do not need to name files or spec locations."
+        }
+      },
+      required: ["task"]
+    }
+  },
+  async execute(input, context) {
+    if (!context) {
+      return "Error: spec sync requires execution context";
+    }
+    if (context.onboardingState !== "onboardingFinished") {
+      return "Spec sync runs only after the build is finished (onboardingFinished). During intake and the initial build you author the spec directly, so there is nothing to reconcile yet.";
+    }
+    const specIndex = loadSpecIndex();
+    const parts = [
+      BASE_PROMPT5,
+      loadPlatformBrief(),
+      MSFM_DOCS,
+      "<!-- cache_breakpoint -->"
+    ];
+    if (specIndex) {
+      parts.push(specIndex);
+    }
+    const system = parts.join("\n\n");
+    const result = await runSubAgent({
+      system,
+      task: input.task,
+      tools: SPEC_SYNC_TOOLS,
+      externalTools: /* @__PURE__ */ new Set(),
+      executeTool: (name, toolInput) => executeTool(name, toolInput, context),
+      apiConfig: context.apiConfig,
+      model: resolveModel("specSync", context.models, context.model),
+      subAgentId: "specSync",
+      signal: context.signal,
+      parentToolId: context.toolCallId,
+      requestId: context.requestId,
+      onEvent: context.onEvent,
+      resolveExternalTool: context.resolveExternalTool,
+      toolRegistry: context.toolRegistry,
+      // Always background + serialized: never blocks Remy's turn, and two
+      // reconciliations queue (FIFO) instead of running at once.
+      background: true,
+      acquireLock: acquireSpecSyncLock,
+      onBackgroundComplete: (bgResult) => {
+        context.onBackgroundComplete?.(
+          context.toolCallId,
+          "specSync",
+          bgResult.text,
+          bgResult.messages
+        );
+      }
+    });
+    context.subAgentMessages?.set(context.toolCallId, result.messages);
+    return result.text;
+  }
+};
+
 // src/tools/common/scrapeWebUrl.ts
 var scrapeWebUrlTool = {
   clearable: false,
@@ -5739,6 +5851,8 @@ var ALL_TOOLS = [
   productVisionTool,
   codeSanityCheckTool,
   copyEditorTool,
+  specSyncTool,
+  // no-ops until onboardingFinished; kept here so the tool list stays cache-stable
   buildOverviewTool,
   compactConversationTool,
   // Post-onboarding
@@ -5776,6 +5890,7 @@ var SUBAGENT_TOOL_NAMES = /* @__PURE__ */ new Set([
   "productVision",
   "codeSanityCheck",
   "copyEditor",
+  "specSync",
   "runAutomatedBrowserTest",
   "askMindStudioSdk"
 ]);
@@ -6860,6 +6975,11 @@ var USER_BLOCKING_EXTERNAL_TOOLS = /* @__PURE__ */ new Set([
   "presentPublishPlan",
   "confirmDestructiveAction"
 ]);
+function isBackgroundCall(tc) {
+  return Boolean(
+    tc.input?.background || getToolByName(tc.name)?.backgroundOnly
+  );
+}
 function createAgentState() {
   return { messages: [] };
 }
@@ -6912,7 +7032,10 @@ async function runTurn(params) {
   onEvent({
     type: "user_message",
     text: userMessage,
-    hidden: hidden || void 0
+    hidden: hidden || void 0,
+    // Include attachments so the live event can render a queued voice/image/file
+    // bubble; a voice message has empty text and the transcript lives here.
+    ...hasAttachments && { attachments }
   });
   const isFirstMessage = state.messages.filter((m) => m.role === "user").length === 1;
   const STATUS_EXCLUDED_TOOLS = /* @__PURE__ */ new Set([
@@ -7124,16 +7247,18 @@ async function runTurn(params) {
             break;
           }
           case "tool_use": {
+            const tool = getToolByName(event.name);
             contentBlocks.push({
               type: "tool",
               id: event.id,
               name: event.name,
               input: event.input,
               startedAt: event.ts,
-              ...event.input.background && { background: true }
+              ...(event.input.background || tool?.backgroundOnly) && {
+                background: true
+              }
             });
             const acc = toolInputAccumulators.get(event.id);
-            const tool = getToolByName(event.name);
             const wasStreamed = acc?.started ?? false;
             const isInputStreaming = !!tool?.streaming?.partialInput;
             log13.info("Tool received", {
@@ -7366,7 +7491,7 @@ async function runTurn(params) {
         toolRegistry?.register(entry);
         run(tc.input);
         const r = await resultPromise;
-        if (!tc.input.background) {
+        if (!isBackgroundCall(tc)) {
           toolRegistry?.unregister(tc.id);
         }
         log13.info("Tool completed", {
@@ -8030,7 +8155,16 @@ var HeadlessSession = class {
         this.emit("turn_started", {}, rid);
         return;
       case "user_message":
-        this.emit("user_message", { text: e.text }, rid);
+        this.emit(
+          "user_message",
+          {
+            text: e.text,
+            // Forward attachments so queued voice/image/file sends render live;
+            // otherwise the bubble is blank until a get_history refresh.
+            ...e.attachments && { attachments: e.attachments }
+          },
+          rid
+        );
         return;
       // Terminal events — translate to `completed`.
       // Post-turn queue drain happens in handleMessage AFTER runTurn returns,

package/dist/index.js

@@ -1810,7 +1810,7 @@ var init_compaction = __esm({
     "use strict";
     init_api();
     init_assets();
-    init_tools7();
+    init_tools8();
     init_logger();
     init_usageLedger();
     log2 = createLogger("compaction");
@@ -2037,6 +2037,13 @@ var init_surfaces = __esm({
         modelType: "text",
         userPickable: true
       },
+      specSync: {
+        default: "claude-5-sonnet",
+        label: "Spec Sync Agent",
+        description: "Keeps your spec in sync with the code as you build, updating the affected sections in the background after changes.",
+        modelType: "text",
+        userPickable: true
+      },
       imageGeneration: {
         default: "seedream-4.5",
         label: "Image Generation",
@@ -2356,7 +2363,7 @@ var init_trigger = __esm({
     "use strict";
     init_compaction();
     init_prompt();
-    init_tools7();
+    init_tools8();
     init_logger();
     init_surfaces();
     log4 = createLogger("compaction:trigger");
@@ -3883,6 +3890,7 @@ async function runSubAgent(config) {
     requestId,
     history,
     background,
+    acquireLock,
     onBackgroundComplete,
     captureArtifacts
   } = config;
@@ -4275,7 +4283,15 @@ ${partial}` : "[INTERRUPTED] Agent was interrupted before producing output.",
     agentName: subAgentId || "agent",
     task
   });
-  wrapRun().then((finalResult) => {
+  const runDetached = async () => {
+    const release = acquireLock ? await acquireLock() : null;
+    try {
+      return await wrapRun();
+    } finally {
+      release?.();
+    }
+  };
+  runDetached().then((finalResult) => {
     toolRegistry?.unregister(parentToolId);
     onBackgroundComplete?.(finalResult);
   }).catch((err) => {
@@ -5615,7 +5631,7 @@ var init_copyEditor = __esm({
     init_assets();
     init_runner();
     init_context();
-    init_tools7();
+    init_tools8();
     init_tools3();
     init_surfaces();
     BASE_PROMPT2 = readAsset("subagents/copyEditor", "prompt.md");
@@ -5714,7 +5730,7 @@ var tools, DESIGN_EXPERT_TOOLS;
 var init_tools4 = __esm({
   "src/subagents/designExpert/tools/index.ts"() {
     "use strict";
-    init_tools7();
+    init_tools8();
     init_tools2();
     init_searchGoogle2();
     init_scrapeWebUrl();
@@ -6080,7 +6096,7 @@ var DESCRIPTION, RENDER_WRITE_TOOL_NAMES, DESIGN_EXPERT_RENDER_TOOLS, designExpe
 var init_designExpert = __esm({
   "src/subagents/designExpert/index.ts"() {
     "use strict";
-    init_tools7();
+    init_tools8();
     init_runner();
     init_tools4();
     init_tools2();
@@ -6335,7 +6351,7 @@ var productVisionTool;
 var init_productVision = __esm({
   "src/subagents/productVision/index.ts"() {
     "use strict";
-    init_tools7();
+    init_tools8();
     init_runner();
     init_tools5();
     init_tools2();
@@ -6471,7 +6487,7 @@ var init_codeSanityCheck = __esm({
     init_assets();
     init_runner();
     init_context();
-    init_tools7();
+    init_tools8();
     init_tools6();
     init_surfaces();
     BASE_PROMPT4 = readAsset("subagents/codeSanityCheck", "prompt.md");
@@ -6525,6 +6541,131 @@ var init_codeSanityCheck = __esm({
   }
 });
 
+// src/subagents/specSync/tools.ts
+var SPEC_SYNC_TOOLS;
+var init_tools7 = __esm({
+  "src/subagents/specSync/tools.ts"() {
+    "use strict";
+    init_tools2();
+    init_readSpec();
+    init_editSpec();
+    init_writeSpec();
+    SPEC_SYNC_TOOLS = [
+      ...COMMON_READ_TOOLS,
+      readSpecTool.definition,
+      editSpecTool.definition,
+      writeSpecTool.definition
+    ];
+  }
+});
+
+// src/subagents/specSync/lock.ts
+function acquireSpecSyncLock() {
+  let release;
+  const next = new Promise((res) => {
+    release = res;
+  });
+  const wait = lockQueue2;
+  lockQueue2 = next;
+  return wait.then(() => release);
+}
+var lockQueue2;
+var init_lock = __esm({
+  "src/subagents/specSync/lock.ts"() {
+    "use strict";
+    lockQueue2 = Promise.resolve();
+  }
+});
+
+// src/subagents/specSync/index.ts
+var BASE_PROMPT5, MSFM_DOCS, specSyncTool;
+var init_specSync = __esm({
+  "src/subagents/specSync/index.ts"() {
+    "use strict";
+    init_assets();
+    init_runner();
+    init_context();
+    init_tools8();
+    init_tools7();
+    init_lock();
+    init_surfaces();
+    BASE_PROMPT5 = readAsset("subagents/specSync", "prompt.md");
+    MSFM_DOCS = `<mindstudio_flavored_markdown_spec_docs>
+${readAsset(
+      "prompt",
+      "compiled/msfm.md"
+    )}
+</mindstudio_flavored_markdown_spec_docs>`;
+    specSyncTool = {
+      clearable: false,
+      backgroundOnly: true,
+      definition: {
+        name: "specSync",
+        description: "Reconcile the spec to bring it in line with code changes you have made. Provide a brief, bulleted list of what changed and why; it finds the affected spec sections and updates them to match. Always runs in the background \u2014 it returns immediately and reports back when done.",
+        inputSchema: {
+          type: "object",
+          properties: {
+            task: {
+              type: "string",
+              description: "What you changed in the code and why, in plain language \u2014 the way you would explain it to a teammate. The specialist reads the spec itself and decides which sections to update; you do not need to name files or spec locations."
+            }
+          },
+          required: ["task"]
+        }
+      },
+      async execute(input, context) {
+        if (!context) {
+          return "Error: spec sync requires execution context";
+        }
+        if (context.onboardingState !== "onboardingFinished") {
+          return "Spec sync runs only after the build is finished (onboardingFinished). During intake and the initial build you author the spec directly, so there is nothing to reconcile yet.";
+        }
+        const specIndex = loadSpecIndex();
+        const parts = [
+          BASE_PROMPT5,
+          loadPlatformBrief(),
+          MSFM_DOCS,
+          "<!-- cache_breakpoint -->"
+        ];
+        if (specIndex) {
+          parts.push(specIndex);
+        }
+        const system = parts.join("\n\n");
+        const result = await runSubAgent({
+          system,
+          task: input.task,
+          tools: SPEC_SYNC_TOOLS,
+          externalTools: /* @__PURE__ */ new Set(),
+          executeTool: (name, toolInput) => executeTool(name, toolInput, context),
+          apiConfig: context.apiConfig,
+          model: resolveModel("specSync", context.models, context.model),
+          subAgentId: "specSync",
+          signal: context.signal,
+          parentToolId: context.toolCallId,
+          requestId: context.requestId,
+          onEvent: context.onEvent,
+          resolveExternalTool: context.resolveExternalTool,
+          toolRegistry: context.toolRegistry,
+          // Always background + serialized: never blocks Remy's turn, and two
+          // reconciliations queue (FIFO) instead of running at once.
+          background: true,
+          acquireLock: acquireSpecSyncLock,
+          onBackgroundComplete: (bgResult) => {
+            context.onBackgroundComplete?.(
+              context.toolCallId,
+              "specSync",
+              bgResult.text,
+              bgResult.messages
+            );
+          }
+        });
+        context.subAgentMessages?.set(context.toolCallId, result.messages);
+        return result.text;
+      }
+    };
+  }
+});
+
 // src/tools/common/scrapeWebUrl.ts
 var scrapeWebUrlTool;
 var init_scrapeWebUrl2 = __esm({
@@ -6708,7 +6849,7 @@ function executeTool(name, input, context) {
   return tool.execute(input, context);
 }
 var ALL_TOOLS, CLEARABLE_TOOLS, SUBAGENT_TOOL_NAMES;
-var init_tools7 = __esm({
+var init_tools8 = __esm({
   "src/tools/index.ts"() {
     "use strict";
     init_readSpec();
@@ -6744,6 +6885,7 @@ var init_tools7 = __esm({
     init_productVision();
     init_codeSanityCheck();
     init_copyEditor();
+    init_specSync();
     init_scrapeWebUrl2();
     init_writeBuildOverview();
     ALL_TOOLS = [
@@ -6759,6 +6901,8 @@ var init_tools7 = __esm({
       productVisionTool,
       codeSanityCheckTool,
       copyEditorTool,
+      specSyncTool,
+      // no-ops until onboardingFinished; kept here so the tool list stays cache-stable
       buildOverviewTool,
       compactConversationTool,
       // Post-onboarding
@@ -6796,6 +6940,7 @@ var init_tools7 = __esm({
       "productVision",
       "codeSanityCheck",
       "copyEditor",
+      "specSync",
       "runAutomatedBrowserTest",
       "askMindStudioSdk"
     ]);
@@ -7562,6 +7707,11 @@ function getToolCalls(blocks) {
     (b) => b.type === "tool"
   );
 }
+function isBackgroundCall(tc) {
+  return Boolean(
+    tc.input?.background || getToolByName(tc.name)?.backgroundOnly
+  );
+}
 function createAgentState() {
   return { messages: [] };
 }
@@ -7614,7 +7764,10 @@ async function runTurn(params) {
   onEvent({
     type: "user_message",
     text: userMessage,
-    hidden: hidden || void 0
+    hidden: hidden || void 0,
+    // Include attachments so the live event can render a queued voice/image/file
+    // bubble; a voice message has empty text and the transcript lives here.
+    ...hasAttachments && { attachments }
   });
   const isFirstMessage = state.messages.filter((m) => m.role === "user").length === 1;
   const STATUS_EXCLUDED_TOOLS = /* @__PURE__ */ new Set([
@@ -7826,16 +7979,18 @@ async function runTurn(params) {
             break;
           }
           case "tool_use": {
+            const tool = getToolByName(event.name);
             contentBlocks.push({
               type: "tool",
               id: event.id,
               name: event.name,
               input: event.input,
               startedAt: event.ts,
-              ...event.input.background && { background: true }
+              ...(event.input.background || tool?.backgroundOnly) && {
+                background: true
+              }
             });
             const acc = toolInputAccumulators.get(event.id);
-            const tool = getToolByName(event.name);
             const wasStreamed = acc?.started ?? false;
             const isInputStreaming = !!tool?.streaming?.partialInput;
             log12.info("Tool received", {
@@ -8068,7 +8223,7 @@ async function runTurn(params) {
         toolRegistry?.register(entry);
         run(tc.input);
         const r = await resultPromise;
-        if (!tc.input.background) {
+        if (!isBackgroundCall(tc)) {
           toolRegistry?.unregister(tc.id);
         }
         log12.info("Tool completed", {
@@ -8135,7 +8290,7 @@ var init_agent = __esm({
   "src/agent.ts"() {
     "use strict";
     init_api();
-    init_tools7();
+    init_tools8();
     init_session();
     init_logger();
     init_usageLedger();
@@ -8143,7 +8298,7 @@ var init_agent = __esm({
     init_statusWatcher();
     init_errors();
     init_cleanMessages();
-    init_tools7();
+    init_tools8();
     init_sentinel();
     init_trigger2();
     init_surfaces();
@@ -8885,7 +9040,16 @@ var init_headless = __esm({
             this.emit("turn_started", {}, rid);
             return;
           case "user_message":
-            this.emit("user_message", { text: e.text }, rid);
+            this.emit(
+              "user_message",
+              {
+                text: e.text,
+                // Forward attachments so queued voice/image/file sends render live;
+                // otherwise the bubble is blank until a get_history refresh.
+                ...e.attachments && { attachments: e.attachments }
+              },
+              rid
+            );
             return;
           // Terminal events — translate to `completed`.
           // Post-turn queue drain happens in handleMessage AFTER runTurn returns,

package/dist/prompt/static/authoring.md

@@ -89,6 +89,6 @@ When generated code exists in `dist/`, you have both spec tools and code tools.
 
 **Key principle: spec and code stay in sync.**
 - When editing the spec, also update the affected code in the same turn.
-- When the user asks for a code change that represents a behavioral change, also update the spec.
+- When you make a code change that alters what the app does, the spec has to catch up too - but this must happen infrequently and in the background so it doesn't block your work and iteration with the user. Use the specSync tool to periodically update the spec after big/meaningful chunks of work, avoid editing the spec files directly. Remember, it is completely fine and normal for there to be some drift between the code and spec - you do not need to sync after every conversation turn. You can batch many changes together - you can trust that the specSync tool will investigate the changes and reconcile on its own.
 - Spec tools work on `src/` files: `readSpec` to read (do this before editing), `editSpec` for targeted find/replace edits (same `old_string`/`new_string` model as `editFile`), `writeSpec` for a full-file write, `listSpecFiles` to see what exists.
 - Code tools (`readFile`, `writeFile`, `editFile`, etc.) work on `dist/` and other project files.

package/dist/prompt/static/instructions.md

@@ -5,8 +5,7 @@
 4. **Iterate.** If something fails, read the error, diagnose the root cause, and try a different approach.
 
 ## Principles
-- The spec in `src/` is the source of truth. When in doubt, consult the spec before making code changes. When behavior changes, update the spec first.
-- Always keep the spec up to date after making changes to the code, especially when adding features or building things from the roadmap.
+- The spec in `src/` is the source of truth for what the app does: consult it before making behavioral code changes, and keep it in sync as the app evolves by dispatching periodic requests to the specSync tool after meaningful changes. Some amount of drift is fine and inevitable - your priority is working efficiently with the user, let the specSync tool handle things in the background.
 - Keep `src/overview.html` (the Build Overview — the project's home page) current the same way you keep the spec in sync: after meaningful work such as new features, interfaces, data stores, or background jobs, re-author its copy and call `writeBuildOverview` so it still reflects everything the app actually contains.
 - Change only what the task requires. Match existing styles. Keep solutions simple.
 - Read files before editing them. Understand the context before making changes.

package/dist/prompt/static/team.md

@@ -40,6 +40,12 @@ Always consult the code sanity check before writing code in initialCodegen with
 
 Your editor — a design expert for words. Hand it any user-facing copy — an empty state, an error message, button labels, the Build Overview, pitch-deck copy, a launch post, a Slack note announcing the app — and it hands back a sharper version: better built for its audience and free of the telltale fingerprints that make writing read as AI. You're good at deciding *what* to say; it's great at making it land. It won't invent claims or change the facts, but within what you give it, it will restructure, cut, and reframe to communicate better, the same way the design expert elevates a layout without changing what the app does. Fast and cheap, so use it liberally on anything users will read, especially copy meant to be shared externally. Give it the text plus what it's for (the medium, the audience).
 
+### Spec Sync Agent (`specSync`)
+
+Your spec keeper. Once the app is built and you're iterating on it, whenever you make code changes that alter what the app does, hand it a brief, plain-language description of what you changed and why (prefer bullet points, batch multiple changes into one invocation). It finds the affected sections of the spec in `src/` and updates them to match what has been built. It reads the spec itself and decides what to touch, so you don't need to name files or locations.
+
+It always runs in the background: it returns immediately and you keep working while it reconciles, and you'll get notified when the updated spec lands later. So don't hunt through spec files to sync them yourself and don't wait on it — hand off and move on. You decide when the spec has drifted enough to be worth a hand-off (after a meaningful change, or a batch of them - you do not need to invoke this after every change or conversation turn - some amount of drift between code and spec is completely normal and acceptable).
+
 ### QA (`runAutomatedBrowserTest`)
 
 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.
@@ -72,4 +78,4 @@ You can only background the following two tasks, unless the user specifically as
 - `productVision` seeding the intiial roadmap after writing the spec for the first time or updating the roadmap after large work sessions. This task takes a while and we can allow the user to continue building while it happens in the background.
 - After writing the spec, once you have finalized the shape of the app, ask `visualDesignExpert` to create an icon and an open graph shring image for the app, then set them with `setProjectMetadata`, alongside the app's name and short description.
 
-Do not background any other tasks.
+Do not background any other tasks. Be aware that sometimes tools like specSync will background on their own - this is not something that is within your control.

package/dist/subagents/specSync/prompt.md

@@ -0,0 +1,16 @@
+You keep the app's spec in `src/` aligned with the code. The developer has just made code changes and is handing you a description of what changed and why. Your one job is to find the spec sections that describe that behavior and update them so the spec matches the code again.
+
+Work fast. This is reconciliation, not review.
+
+## How to work
+
+1. **Trust the developer's brief.** The developer knows what it changed and why. Take the brief as ground truth for the change. Do not re-derive it, second-guess whether the change was correct, or audit the rest of the app.
+2. **Locate the affected spec.** The project's spec files are already listed for you below, each with a one-line description. Use `grep`/`readSpec` to find where the changed behavior is documented, and read only the sections you are about to touch. If the brief mentions something not yet in any spec (a new feature, table, role, interface, background job), add it to the spec file where it belongs.
+3. **Update it.** Use `editSpec` for targeted changes (read the section first so your `old_string` matches), or `writeSpec` for a full rewrite of a file. Read a spec file with `readSpec` before editing it.
+4. **Finish.** Once the spec reflects the change, you are done. Do not keep looking for more to fix, do not polish unrelated sections, do not verify the code beyond a quick read if and only if the brief is genuinely ambiguous.
+
+## What to write
+
+The spec is written in MindStudio-Flavored Markdown (MSFM); the format reference is included below. Follow it, and match the structure and voice already in the spec files. Write prose in plain, human language, the way you would describe the app to a colleague. Keep exact technical values (field names, routes, roles, limits, config) in annotations, not in the prose. Do not invent detail the brief and code do not support: describe what actually exists now, nothing more.
+
+You edit the spec only. You never edit code.

package/package.json

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