@agent-native/core 0.145.8 → 0.146.1

package/corpus/templates/mail/.agents/skills/turn-into-app/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Turn visible project context, a proven thread, skill, or workflow into a
   runnable Agent-Native app with simple buttons, visible agent steps, preview,
   and deployment handoff. Use when a user invokes `/turn-into-app` or asks to
-  make a workflow into an app.
+  make a workflow into an app, including from Claude or ChatGPT on the web.
 user-invocable: true
 scope: both
 metadata:
@@ -13,9 +13,36 @@ metadata:
 
 # Turn Into App
 
+## Host execution boundary
+
+The build location depends on the host. Treat this as a hard routing rule:
+
+- In Claude Web, ChatGPT Web, or a Claude/ChatGPT Project on the web, you are
+  the source analyst and handoff orchestrator. You must not build the app in
+  the host sandbox. Do not run `npm`, `pnpm`, `npx`, `agent-native create`, or
+  `add-app`; do not edit files, create artifacts, or start a local dev server.
+  After writing the bounded source brief, call the connected Dispatch action
+  `start-workspace-app-creation`. Pass the brief and repeatable workflow in
+  `prompt`, plus the inferred `appId`, `description`, `template`, and selected
+  `resourceIds` when available. This is the Builder handoff.
+- Do not substitute the generic `create_workspace_app` MCP tool in an online
+  host. That tool is a local workspace scaffolder, not the Builder handoff.
+- Connect the Agent-Native Dispatch MCP connector only. Dispatch uses the
+  authenticated Builder Projects API to reuse or provision the workspace
+  project before starting the Builder Cloud Agent; a separate Builder CMS MCP
+  connection is not required for this workflow.
+- If `start-workspace-app-creation` is not available or Dispatch is not
+  authenticated, stop with the connector setup needed. Do not fall back to a
+  local build or claim that the app exists.
+- In Claude Code, Codex Code, or another local code-agent runtime with a target
+  workspace, follow the local implementation steps below. The local agent may
+  scaffold, edit, run, and verify the app there.
+
 ## Default behavior
 
-This is an end-to-end build skill, not a request for an app proposal.
+For a local code-agent runtime this is an end-to-end build skill, not a request
+for an app proposal. For an online host, the end-to-end result is a verified
+Builder handoff and the resulting workspace app, not code written in the host.
 
 - With no argument, choose the source in this order: visible project context,
   then the current thread. A fresh Claude or ChatGPT Project is a valid source
@@ -47,9 +74,12 @@ private web access, invent an importer, add fake OAuth, or scrape a logged-in
 page. If the needed context is not visible, ask for an export, transcript, or
 attachment and treat that artifact as imported source material.
 
-Deliver a fresh app in a new directory, implement the repeatable workflow with
-buttons and agent handoffs, start its dev server, verify the main path, and
-continue through build/deployment handoff. Do not stop at a plan.
+For local code-agent runtimes, deliver a fresh app in a new directory,
+implement the repeatable workflow with buttons and agent handoffs, start its dev
+server, verify the main path, and continue through build/deployment handoff. Do
+not stop at a plan. For online hosts, call Dispatch first after the source brief,
+then report the returned Builder branch/path and verify the workspace app through
+Dispatch when it becomes available.
 
 ## Fresh project context mode
 
@@ -190,12 +220,12 @@ Do not use `create` for an existing workspace; it scaffolds a new standalone
 workspace rather than adding an app to the current one.
 
 When the source came from a fresh external Project and the target is a Builder
-workspace, prefer the available Dispatch MCP workspace handoff after writing
-the source brief. Call `start-workspace-app-creation` with a concise prompt,
-the inferred app id, and the brief's repeatable workflow. Pass selected
-workspace resource IDs when they are available, rather than pasting entire
-knowledge files. Continue from the returned workspace path or Builder handoff
-and report the actual verification result.
+workspace, the online host path is mandatory: after writing the source brief,
+call `start-workspace-app-creation` with a concise prompt, the inferred app id,
+and the brief's repeatable workflow. Pass selected workspace resource IDs when
+they are available, rather than pasting entire knowledge files. Continue from
+the returned workspace path or Builder branch handoff and report the actual
+verification result. Do not run the local scaffold commands in this host mode.
 
 Use a first-party template only when it materially fits the workflow. Keep the
 new app independent from the source thread's working tree unless the user

package/corpus/templates/mail/.agents/skills/turn-into-app/references/fresh-project.md

@@ -50,14 +50,33 @@ skills. For a ChatGPT Project or any host that exposes only the MCP connector,
 also place the skill instructions or this reference in the Project
 instructions/knowledge files. Then add and authenticate the Dispatch MCP
 connector from the packaged `adapters/chatgpt-mcp/connector.json`.
+This single connector is enough: Dispatch provisions or reuses the Builder
+project through the Builder Projects API, so do not ask the user to add a
+separate Builder CMS MCP for app creation.
+Builder's separate Fusion MCP is available as a custom remote connector at
+`https://mcp.builder.io/mcp/fusion` for direct Builder work. It can run an
+existing project, but it cannot provision the repo-backed Agent-Native
+workspace project, so it is optional and not a replacement for the Dispatch
+handoff in this skill. Do not add Builder's CMS MCP for this workflow.
+
+For Claude Web, ChatGPT Web, and their web Projects, the host is an
+orchestrator, not the build environment. After forming the source brief, call
+the Dispatch `start-workspace-app-creation` action so Builder creates the app
+in the connected workspace. Do not use the host's code interpreter, shell,
+artifact editor, `create_workspace_app`, or local `pnpm`/`npm` commands. If the
+handoff action is unavailable, stop and ask the user to authenticate Dispatch;
+do not fall back to a local sandbox build. Claude Code and Codex Code are the
+local-agent exception and may follow the implementation steps in the main
+skill.
 
 In a new Project chat, say:
 
 ```text
 Turn this project into an app. Use the visible Project instructions,
 knowledge files, and any selected successful runs as the source. Create the
-app in the connected Agent-Native workspace, keep the source brief bounded,
-and report the real path and verification result.
+app in the connected Agent-Native workspace through Dispatch and Builder, keep
+the source brief bounded, and report the real Builder branch/path and
+verification result. Do not build it in this chat's sandbox.
 ```
 
 If the host does not show the Project instructions or files to the model, stop

package/corpus/templates/plan/.agents/skills/turn-into-app/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Turn visible project context, a proven thread, skill, or workflow into a
   runnable Agent-Native app with simple buttons, visible agent steps, preview,
   and deployment handoff. Use when a user invokes `/turn-into-app` or asks to
-  make a workflow into an app.
+  make a workflow into an app, including from Claude or ChatGPT on the web.
 user-invocable: true
 scope: both
 metadata:
@@ -13,9 +13,36 @@ metadata:
 
 # Turn Into App
 
+## Host execution boundary
+
+The build location depends on the host. Treat this as a hard routing rule:
+
+- In Claude Web, ChatGPT Web, or a Claude/ChatGPT Project on the web, you are
+  the source analyst and handoff orchestrator. You must not build the app in
+  the host sandbox. Do not run `npm`, `pnpm`, `npx`, `agent-native create`, or
+  `add-app`; do not edit files, create artifacts, or start a local dev server.
+  After writing the bounded source brief, call the connected Dispatch action
+  `start-workspace-app-creation`. Pass the brief and repeatable workflow in
+  `prompt`, plus the inferred `appId`, `description`, `template`, and selected
+  `resourceIds` when available. This is the Builder handoff.
+- Do not substitute the generic `create_workspace_app` MCP tool in an online
+  host. That tool is a local workspace scaffolder, not the Builder handoff.
+- Connect the Agent-Native Dispatch MCP connector only. Dispatch uses the
+  authenticated Builder Projects API to reuse or provision the workspace
+  project before starting the Builder Cloud Agent; a separate Builder CMS MCP
+  connection is not required for this workflow.
+- If `start-workspace-app-creation` is not available or Dispatch is not
+  authenticated, stop with the connector setup needed. Do not fall back to a
+  local build or claim that the app exists.
+- In Claude Code, Codex Code, or another local code-agent runtime with a target
+  workspace, follow the local implementation steps below. The local agent may
+  scaffold, edit, run, and verify the app there.
+
 ## Default behavior
 
-This is an end-to-end build skill, not a request for an app proposal.
+For a local code-agent runtime this is an end-to-end build skill, not a request
+for an app proposal. For an online host, the end-to-end result is a verified
+Builder handoff and the resulting workspace app, not code written in the host.
 
 - With no argument, choose the source in this order: visible project context,
   then the current thread. A fresh Claude or ChatGPT Project is a valid source
@@ -47,9 +74,12 @@ private web access, invent an importer, add fake OAuth, or scrape a logged-in
 page. If the needed context is not visible, ask for an export, transcript, or
 attachment and treat that artifact as imported source material.
 
-Deliver a fresh app in a new directory, implement the repeatable workflow with
-buttons and agent handoffs, start its dev server, verify the main path, and
-continue through build/deployment handoff. Do not stop at a plan.
+For local code-agent runtimes, deliver a fresh app in a new directory,
+implement the repeatable workflow with buttons and agent handoffs, start its dev
+server, verify the main path, and continue through build/deployment handoff. Do
+not stop at a plan. For online hosts, call Dispatch first after the source brief,
+then report the returned Builder branch/path and verify the workspace app through
+Dispatch when it becomes available.
 
 ## Fresh project context mode
 
@@ -190,12 +220,12 @@ Do not use `create` for an existing workspace; it scaffolds a new standalone
 workspace rather than adding an app to the current one.
 
 When the source came from a fresh external Project and the target is a Builder
-workspace, prefer the available Dispatch MCP workspace handoff after writing
-the source brief. Call `start-workspace-app-creation` with a concise prompt,
-the inferred app id, and the brief's repeatable workflow. Pass selected
-workspace resource IDs when they are available, rather than pasting entire
-knowledge files. Continue from the returned workspace path or Builder handoff
-and report the actual verification result.
+workspace, the online host path is mandatory: after writing the source brief,
+call `start-workspace-app-creation` with a concise prompt, the inferred app id,
+and the brief's repeatable workflow. Pass selected workspace resource IDs when
+they are available, rather than pasting entire knowledge files. Continue from
+the returned workspace path or Builder branch handoff and report the actual
+verification result. Do not run the local scaffold commands in this host mode.
 
 Use a first-party template only when it materially fits the workflow. Keep the
 new app independent from the source thread's working tree unless the user

package/corpus/templates/plan/.agents/skills/turn-into-app/references/fresh-project.md

@@ -50,14 +50,33 @@ skills. For a ChatGPT Project or any host that exposes only the MCP connector,
 also place the skill instructions or this reference in the Project
 instructions/knowledge files. Then add and authenticate the Dispatch MCP
 connector from the packaged `adapters/chatgpt-mcp/connector.json`.
+This single connector is enough: Dispatch provisions or reuses the Builder
+project through the Builder Projects API, so do not ask the user to add a
+separate Builder CMS MCP for app creation.
+Builder's separate Fusion MCP is available as a custom remote connector at
+`https://mcp.builder.io/mcp/fusion` for direct Builder work. It can run an
+existing project, but it cannot provision the repo-backed Agent-Native
+workspace project, so it is optional and not a replacement for the Dispatch
+handoff in this skill. Do not add Builder's CMS MCP for this workflow.
+
+For Claude Web, ChatGPT Web, and their web Projects, the host is an
+orchestrator, not the build environment. After forming the source brief, call
+the Dispatch `start-workspace-app-creation` action so Builder creates the app
+in the connected workspace. Do not use the host's code interpreter, shell,
+artifact editor, `create_workspace_app`, or local `pnpm`/`npm` commands. If the
+handoff action is unavailable, stop and ask the user to authenticate Dispatch;
+do not fall back to a local sandbox build. Claude Code and Codex Code are the
+local-agent exception and may follow the implementation steps in the main
+skill.
 
 In a new Project chat, say:
 
 ```text
 Turn this project into an app. Use the visible Project instructions,
 knowledge files, and any selected successful runs as the source. Create the
-app in the connected Agent-Native workspace, keep the source brief bounded,
-and report the real path and verification result.
+app in the connected Agent-Native workspace through Dispatch and Builder, keep
+the source brief bounded, and report the real Builder branch/path and
+verification result. Do not build it in this chat's sandbox.
 ```
 
 If the host does not show the Project instructions or files to the model, stop

package/corpus/templates/slides/.agents/skills/image-generation-via-a2a/SKILL.md

@@ -53,6 +53,14 @@ Call the action with the destination so Assets can ground the generation:
 generate-image-api { prompt, deckId, slideId, slideContent }
 ```
 
+For direct insertion, add `insertIntoSlide: true`. This requires both IDs and
+only returns `inserted: true` after Slides writes the transformed HTML through
+`update-slide` and re-reads it through `get-deck` to find the image source.
+Never say the image was added based on `url`, `previewUrl`, or a completed
+Assets reply alone. For preview-only variations, leave `insertIntoSlide` false;
+after choosing one, use `update-slide` and verify the persisted source with
+`get-deck` before claiming insertion.
+
 Do **not** reach for the generic `call-agent` tool to ask Assets for an image.
 It talks to the same app, so it looks equivalent, but it skips the slide
 grounding, the completed-vs-failed task handling, and the ready-to-render
@@ -65,7 +73,8 @@ generation settings, and provenance. Include the active design system's
 image-style guidance in the prompt context, but do not ask Assets to invent a
 competing brand direction.
 
-Drop the returned `previewUrl` into the slide HTML's `<img src="...">`.
+Use the returned `previewUrl` for previews. Do not drop it into slide HTML
+without the verified insertion workflow above.
 
 ## Showing the result in chat
 

package/corpus/templates/slides/.agents/skills/slide-images/SKILL.md

@@ -34,8 +34,13 @@ legacy image action directly:
    image syntax (`![Variation 1](url)`), not a plain link (`[Variation 1](url)`)
    — the chat renders `![]()` as an actual image but `[]()` as a bare link.
 4. Preserve the returned `assetId`, `runId`, `previewUrl`, and `downloadUrl`.
-5. Insert the chosen image into the slide content through the normal action.
-6. For feedback, refine the same asset rather than starting an unrelated run.
+5. For direct insertion, call `generate-image-api` with `insertIntoSlide: true`,
+   `deckId`, and `slideId`. Only say the image was added when it returns
+   `inserted: true`; a preview URL is not proof of a slide write.
+6. For preview-only variations, place the chosen URL with `update-slide`, then
+   re-read that slide with `get-deck` and confirm the persisted HTML contains
+   the image source before reporting success.
+7. For feedback, refine the same asset rather than starting an unrelated run.
 
 ### Context to pass
 
@@ -72,4 +77,6 @@ pnpm action search-images --q "Acme logo transparent" --count 5
 - Use `.fmd-img-placeholder` divs in slides before real images are generated
 - Use one canonical provider action per conceptual search; do not loop legacy
   provider scripts or manually guess provider URLs
-- After inserting an image, update the deck via the API
+- Never claim image insertion from a generation response alone; require the
+  verified `inserted: true` response, or an `update-slide` plus `get-deck`
+  verification for preview-only placement

package/corpus/templates/slides/.agents/skills/turn-into-app/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   Turn visible project context, a proven thread, skill, or workflow into a
   runnable Agent-Native app with simple buttons, visible agent steps, preview,
   and deployment handoff. Use when a user invokes `/turn-into-app` or asks to
-  make a workflow into an app.
+  make a workflow into an app, including from Claude or ChatGPT on the web.
 user-invocable: true
 scope: both
 metadata:
@@ -13,9 +13,36 @@ metadata:
 
 # Turn Into App
 
+## Host execution boundary
+
+The build location depends on the host. Treat this as a hard routing rule:
+
+- In Claude Web, ChatGPT Web, or a Claude/ChatGPT Project on the web, you are
+  the source analyst and handoff orchestrator. You must not build the app in
+  the host sandbox. Do not run `npm`, `pnpm`, `npx`, `agent-native create`, or
+  `add-app`; do not edit files, create artifacts, or start a local dev server.
+  After writing the bounded source brief, call the connected Dispatch action
+  `start-workspace-app-creation`. Pass the brief and repeatable workflow in
+  `prompt`, plus the inferred `appId`, `description`, `template`, and selected
+  `resourceIds` when available. This is the Builder handoff.
+- Do not substitute the generic `create_workspace_app` MCP tool in an online
+  host. That tool is a local workspace scaffolder, not the Builder handoff.
+- Connect the Agent-Native Dispatch MCP connector only. Dispatch uses the
+  authenticated Builder Projects API to reuse or provision the workspace
+  project before starting the Builder Cloud Agent; a separate Builder CMS MCP
+  connection is not required for this workflow.
+- If `start-workspace-app-creation` is not available or Dispatch is not
+  authenticated, stop with the connector setup needed. Do not fall back to a
+  local build or claim that the app exists.
+- In Claude Code, Codex Code, or another local code-agent runtime with a target
+  workspace, follow the local implementation steps below. The local agent may
+  scaffold, edit, run, and verify the app there.
+
 ## Default behavior
 
-This is an end-to-end build skill, not a request for an app proposal.
+For a local code-agent runtime this is an end-to-end build skill, not a request
+for an app proposal. For an online host, the end-to-end result is a verified
+Builder handoff and the resulting workspace app, not code written in the host.
 
 - With no argument, choose the source in this order: visible project context,
   then the current thread. A fresh Claude or ChatGPT Project is a valid source
@@ -47,9 +74,12 @@ private web access, invent an importer, add fake OAuth, or scrape a logged-in
 page. If the needed context is not visible, ask for an export, transcript, or
 attachment and treat that artifact as imported source material.
 
-Deliver a fresh app in a new directory, implement the repeatable workflow with
-buttons and agent handoffs, start its dev server, verify the main path, and
-continue through build/deployment handoff. Do not stop at a plan.
+For local code-agent runtimes, deliver a fresh app in a new directory,
+implement the repeatable workflow with buttons and agent handoffs, start its dev
+server, verify the main path, and continue through build/deployment handoff. Do
+not stop at a plan. For online hosts, call Dispatch first after the source brief,
+then report the returned Builder branch/path and verify the workspace app through
+Dispatch when it becomes available.
 
 ## Fresh project context mode
 
@@ -190,12 +220,12 @@ Do not use `create` for an existing workspace; it scaffolds a new standalone
 workspace rather than adding an app to the current one.
 
 When the source came from a fresh external Project and the target is a Builder
-workspace, prefer the available Dispatch MCP workspace handoff after writing
-the source brief. Call `start-workspace-app-creation` with a concise prompt,
-the inferred app id, and the brief's repeatable workflow. Pass selected
-workspace resource IDs when they are available, rather than pasting entire
-knowledge files. Continue from the returned workspace path or Builder handoff
-and report the actual verification result.
+workspace, the online host path is mandatory: after writing the source brief,
+call `start-workspace-app-creation` with a concise prompt, the inferred app id,
+and the brief's repeatable workflow. Pass selected workspace resource IDs when
+they are available, rather than pasting entire knowledge files. Continue from
+the returned workspace path or Builder branch handoff and report the actual
+verification result. Do not run the local scaffold commands in this host mode.
 
 Use a first-party template only when it materially fits the workflow. Keep the
 new app independent from the source thread's working tree unless the user

package/corpus/templates/slides/.agents/skills/turn-into-app/references/fresh-project.md

@@ -50,14 +50,33 @@ skills. For a ChatGPT Project or any host that exposes only the MCP connector,
 also place the skill instructions or this reference in the Project
 instructions/knowledge files. Then add and authenticate the Dispatch MCP
 connector from the packaged `adapters/chatgpt-mcp/connector.json`.
+This single connector is enough: Dispatch provisions or reuses the Builder
+project through the Builder Projects API, so do not ask the user to add a
+separate Builder CMS MCP for app creation.
+Builder's separate Fusion MCP is available as a custom remote connector at
+`https://mcp.builder.io/mcp/fusion` for direct Builder work. It can run an
+existing project, but it cannot provision the repo-backed Agent-Native
+workspace project, so it is optional and not a replacement for the Dispatch
+handoff in this skill. Do not add Builder's CMS MCP for this workflow.
+
+For Claude Web, ChatGPT Web, and their web Projects, the host is an
+orchestrator, not the build environment. After forming the source brief, call
+the Dispatch `start-workspace-app-creation` action so Builder creates the app
+in the connected workspace. Do not use the host's code interpreter, shell,
+artifact editor, `create_workspace_app`, or local `pnpm`/`npm` commands. If the
+handoff action is unavailable, stop and ask the user to authenticate Dispatch;
+do not fall back to a local sandbox build. Claude Code and Codex Code are the
+local-agent exception and may follow the implementation steps in the main
+skill.
 
 In a new Project chat, say:
 
 ```text
 Turn this project into an app. Use the visible Project instructions,
 knowledge files, and any selected successful runs as the source. Create the
-app in the connected Agent-Native workspace, keep the source brief bounded,
-and report the real path and verification result.
+app in the connected Agent-Native workspace through Dispatch and Builder, keep
+the source brief bounded, and report the real Builder branch/path and
+verification result. Do not build it in this chat's sandbox.
 ```
 
 If the host does not show the Project instructions or files to the model, stop

package/corpus/templates/slides/actions/generate-image-api.ts

@@ -8,16 +8,31 @@ import {
   extractAssetUrl,
   imagePreviewMarkdown,
 } from "../server/lib/assets-image-delegation.js";
+import {
+  insertImageIntoSlideHtml,
+  slideHtmlContainsImageSource,
+} from "../server/lib/slide-image-insertion.js";
 import {
   DEFAULT_STYLE_REFERENCE_URLS,
   normalizeReferenceUrls,
 } from "../shared/api.js";
+import getDeckAction from "./get-deck.js";
+import updateSlideAction from "./update-slide.js";
 
 interface ReferenceImage {
   data: string; // base64
   mimeType: string;
 }
 
+interface DeckSlide {
+  id?: string;
+  content?: unknown;
+}
+
+interface DeckWithSlides {
+  slides?: DeckSlide[];
+}
+
 async function urlToReferenceImage(
   url: string,
 ): Promise<ReferenceImage | null> {
@@ -33,6 +48,83 @@ async function urlToReferenceImage(
   }
 }
 
+function parseGeneratedImageUrl(url: string | undefined): string {
+  if (!url) {
+    throw new Error(
+      "Image generation did not return a parseable image URL for insertion",
+    );
+  }
+  try {
+    const parsed = new URL(url);
+    if (parsed.protocol !== "https:" && parsed.protocol !== "http:") {
+      throw new Error("unsupported protocol");
+    }
+    return parsed.toString();
+  } catch {
+    throw new Error(
+      "Image generation did not return a parseable image URL for insertion",
+    );
+  }
+}
+
+async function insertGeneratedImage({
+  deckId,
+  slideId,
+  prompt,
+  url,
+}: {
+  deckId: string | undefined;
+  slideId: string | undefined;
+  prompt: string;
+  url: string | undefined;
+}): Promise<{ inserted: true; url: string }> {
+  if (!deckId || !slideId) {
+    throw new Error(
+      "deckId and slideId are required when insertIntoSlide is true",
+    );
+  }
+
+  const imageUrl = parseGeneratedImageUrl(url);
+  const deck = (await getDeckAction.run({ id: deckId })) as DeckWithSlides;
+  const slide = deck.slides?.find((candidate) => candidate.id === slideId);
+  if (!slide || typeof slide.content !== "string") {
+    throw new Error(
+      `Slide ${slideId} was not found in deck ${deckId} for image insertion`,
+    );
+  }
+
+  const fullContent = insertImageIntoSlideHtml(slide.content, imageUrl, {
+    alt: prompt,
+  });
+  const update = await updateSlideAction.run({
+    deckId,
+    slideId,
+    fullContent,
+    preserveSource: true,
+  });
+  if (!update.ok || !("applied" in update) || !update.applied) {
+    throw new Error(`Image insertion was not applied to slide ${slideId}`);
+  }
+
+  const verifiedDeck = (await getDeckAction.run({
+    id: deckId,
+  })) as DeckWithSlides;
+  const verifiedSlide = verifiedDeck.slides?.find(
+    (candidate) => candidate.id === slideId,
+  );
+  if (
+    !verifiedSlide ||
+    typeof verifiedSlide.content !== "string" ||
+    !slideHtmlContainsImageSource(verifiedSlide.content, imageUrl)
+  ) {
+    throw new Error(
+      `Image insertion could not be verified on slide ${slideId}`,
+    );
+  }
+
+  return { inserted: true, url: imageUrl };
+}
+
 export default defineAction({
   description:
     "Generate a slide image. Delegates to the Assets app over A2A so generations use the brand library, presets, and audit log; falls back to a local Gemini/OpenAI key only when Assets is unreachable. Show the returned `url` to the user as an inline markdown image (![alt](url)) so it renders in chat, never as a bare link.",
@@ -46,6 +138,13 @@ export default defineAction({
       ),
     deckId: z.string().optional().describe("Deck the image is destined for"),
     slideId: z.string().optional().describe("Slide the image is destined for"),
+    insertIntoSlide: z
+      .boolean()
+      .optional()
+      .default(false)
+      .describe(
+        "Insert the generated image into deckId/slideId and verify it persisted",
+      ),
     slideContent: z
       .string()
       .optional()
@@ -60,6 +159,11 @@ export default defineAction({
     if (!prompt?.trim()) {
       throw new Error("Prompt is required");
     }
+    if (args.insertIntoSlide && (!args.deckId || !args.slideId)) {
+      throw new Error(
+        "deckId and slideId are required when insertIntoSlide is true",
+      );
+    }
 
     const delegation = await delegateImageGenerationToAssets({
       prompt,
@@ -73,6 +177,14 @@ export default defineAction({
       const url = extractAssetUrl(delegation.reply, {
         baseUrl: delegation.target,
       });
+      const insertion = args.insertIntoSlide
+        ? await insertGeneratedImage({
+            deckId: args.deckId,
+            slideId: args.slideId,
+            prompt,
+            url: url ?? undefined,
+          })
+        : {};
       return {
         source: "assets-a2a" as const,
         prompt,
@@ -80,6 +192,7 @@ export default defineAction({
         // rather than guessing at URLs it did not return.
         reply: delegation.reply,
         ...(url ? { url, showToUser: imagePreviewMarkdown(prompt, url) } : {}),
+        ...insertion,
       };
     }
 
@@ -128,6 +241,15 @@ export default defineAction({
       );
     }
 
+    const insertion = args.insertIntoSlide
+      ? await insertGeneratedImage({
+          deckId: args.deckId,
+          slideId: args.slideId,
+          prompt,
+          url: uploaded.url,
+        })
+      : {};
+
     return {
       source: "slides-fallback" as const,
       fallbackReason: delegation.reason,
@@ -135,6 +257,7 @@ export default defineAction({
       url: uploaded.url,
       model: result.model,
       prompt,
+      ...insertion,
     };
   },
 });

package/corpus/templates/slides/app/components/deck/DeckCard.tsx

@@ -59,6 +59,7 @@ export default function DeckCard({
   const [contextOpen, setContextOpen] = useState(false);
   const inputRef = useRef<HTMLInputElement>(null);
   const pendingRenameRef = useRef(false);
+  const pendingDeleteRef = useRef(false);
   const pendingWorkspaceDefaultRef = useRef(false);
 
   useEffect(() => {
@@ -227,6 +228,11 @@ export default function DeckCard({
                 pendingWorkspaceDefaultRef.current = false;
                 onSetWorkspaceDefault?.(deck.id, !isWorkspaceDefault);
               }
+              if (pendingDeleteRef.current) {
+                e.preventDefault();
+                pendingDeleteRef.current = false;
+                setTimeout(() => onDelete(deck.id), 0);
+              }
             }}
           >
             <DropdownMenuItem
@@ -268,8 +274,10 @@ export default function DeckCard({
             )}
             <DropdownMenuSeparator />
             <DropdownMenuItem
-              onSelect={() => {
-                onDelete(deck.id);
+              onSelect={(event) => {
+                event.preventDefault();
+                pendingDeleteRef.current = true;
+                setMenuOpen(false);
               }}
               className="text-red-400 focus:text-red-400"
             >