@agent-native/core 0.146.0 → 0.146.1

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

@@ -50,6 +50,14 @@ 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

package/corpus/templates/factory/server/plugins/factory-scheduler-job.ts

@@ -169,9 +169,10 @@ const AUTOMATION_SEEDS: AutomationSeed[] = [
 # Factory Slack feedback triage
 
 Read the Factory configuration. When Slack polling is enabled and a channel is
-configured, call poll-slack-channel first. Then list a bounded page of
-received Slack items and call get-slack-feedback-context for each item before
-classifying it.
+configured, call poll-slack-channel first. Then list at most 2 received Slack
+items by passing limit 2, process them sequentially, and call
+get-slack-feedback-context for each item before classifying it. Never use the
+action's default page size.
 
 Start work only for a clear bug: a concrete broken behavior, reproducible
 failure, error, regression, stuck run, incorrect result, or a report with a
@@ -203,9 +204,9 @@ PR, merge, or fix unless an action returned that state.
 # Factory Sentry error triage
 
 Read the Factory configuration. When Sentry polling is enabled and a Sentry
-organization is configured, call poll-sentry-errors. List a bounded page of
-received Sentry items and inspect the title, culprit, level, event count, and
-errorReport metadata.
+organization is configured, call poll-sentry-errors. List at most 3 received
+Sentry items by passing limit 3 and inspect the title, culprit, level, event
+count, and errorReport metadata. Never use the action's default page size.
 
 Only classify a concrete unresolved error as a clear bug when the Sentry
 evidence is sufficient to investigate. Do not dispatch on noise, expected
@@ -226,7 +227,8 @@ run callback or PR observation confirms it.
 
 Read the Factory configuration. When GitHub source polling is enabled and a
 repository is configured, call poll-github-sources with includeIssues true and
-includePullRequests false. List a bounded page of received github_issue items.
+includePullRequests false. List at most 3 received github_issue items by
+passing limit 3. Never use the action's default page size.
 
 Treat an issue as a clear bug only when it has a concrete error report,
 reproduction, incorrect behavior, regression, or specific failing path. Do
@@ -247,7 +249,8 @@ confirmation.
 
 Read the Factory configuration. When GitHub polling is enabled and a repository
 is configured, call poll-github-sources with includeIssues false and
-includePullRequests true. List a bounded page of github pull-request items.
+includePullRequests true. List at most 3 github pull-request items by passing
+limit 3. Never use the action's default page size.
 
 For each open agent-native PR, inspect the item and classify whether it is a
 clear bug fix or has product or UX implications. Call
@@ -275,7 +278,8 @@ governance action confirms it.
 
 Read the Factory configuration. When GitHub polling is enabled and a repository
 is configured, call poll-github-sources with includeIssues false and
-includePullRequests true. List a bounded page of open github pull-request items.
+includePullRequests true. List at most 3 open github pull-request items by
+passing limit 3. Never use the action's default page size.
 
 For each item, call babysit-agent-native-pull-request. That action fetches fresh
 GitHub and ai-services evidence and is the only place allowed to decide whether
@@ -312,6 +316,22 @@ function defaultGithubPollingEnabled(): 0 | 1 {
     : 0;
 }
 
+function automationPromptGuard(name: string): string | undefined {
+  switch (name) {
+    case "factory-slack-feedback":
+      return "Runtime safety bound: pass limit 2 to list-triage-items, process at most two Slack items sequentially, and never use the default page size.";
+    case "factory-sentry-errors":
+      return "Runtime safety bound: pass limit 3 to list-triage-items and process at most three Sentry items.";
+    case "factory-github-issues":
+      return "Runtime safety bound: pass limit 3 to list-triage-items and process at most three GitHub issue items.";
+    case "factory-pr-governance":
+    case "factory-pr-babysit":
+      return "Runtime safety bound: pass limit 3 to list-triage-items and process at most three pull-request items.";
+    default:
+      return undefined;
+  }
+}
+
 function setFrontmatterField(
   content: string,
   key: string,
@@ -388,6 +408,10 @@ async function ensureOrganizationAutomations(
       repaired = setFrontmatterField(repaired, "orgId", orgId);
       repaired = setFrontmatterField(repaired, "createdBy", ownerEmail);
       repaired = setFrontmatterField(repaired, "runAs", "creator");
+      const promptGuard = automationPromptGuard(seed.name);
+      if (promptGuard && !repaired.includes(promptGuard)) {
+        repaired = `${repaired.trimEnd()}\n\n${promptGuard}\n`;
+      }
       if (repaired === existing.content) return;
 
       const updated = await resourcePutIfCurrent({
@@ -415,11 +439,16 @@ async function ensureDefaultTriageConfig(
   const db = getDb();
   const existing = (
     await db
-      .select({ id: triageConfig.id })
+      .select({
+        id: triageConfig.id,
+      })
       .from(triageConfig)
       .where(and(eq(triageConfig.id, orgId), eq(triageConfig.orgId, orgId)))
       .limit(1)
   )[0];
+  const repository = defaultRepository();
+  // Existing rows are operator-owned. An empty repository plus disabled
+  // polling can be an intentional choice, so do not infer bootstrap state.
   if (existing) return;
   const now = new Date().toISOString();
   await db.insert(triageConfig).values({
@@ -432,7 +461,7 @@ async function ensureDefaultTriageConfig(
     sentryPollingEnabled: 0,
     lastSlackTs: null,
     slackHistoryCursor: null,
-    repository: defaultRepository(),
+    repository,
     sentryOrgSlug: null,
     sentryProjectSlug: null,
     sentryEnvironment: null,
@@ -445,17 +474,25 @@ async function ensureDefaultTriageConfig(
 }
 
 async function ensureSchedulerJobs(): Promise<void> {
-  const ownerEmail = workspaceOwnerEmail();
-  if (!ownerEmail) {
-    throw new Error(
-      "WORKSPACE_OWNER_EMAIL is required to seed Factory automations",
-    );
-  }
-  const orgId = await resolveOrgIdForEmail(ownerEmail);
-  if (!orgId) {
-    throw new Error(
-      "The Factory deployment owner must belong to an organization before automations can be seeded",
-    );
+  let ownerEmail = workspaceOwnerEmail();
+  let orgId = ownerEmail ? await resolveOrgIdForEmail(ownerEmail) : undefined;
+  if (!ownerEmail || !orgId) {
+    const existingConfigs = await getDb()
+      .select({
+        id: triageConfig.id,
+        ownerEmail: triageConfig.ownerEmail,
+        orgId: triageConfig.orgId,
+      })
+      .from(triageConfig)
+      .limit(2);
+    if (existingConfigs.length !== 1) {
+      throw new Error(
+        "WORKSPACE_OWNER_EMAIL is required to seed Factory automations when the Factory organization is not uniquely configured",
+      );
+    }
+    const existingConfig = existingConfigs[0];
+    ownerEmail = existingConfig.ownerEmail.trim().toLowerCase();
+    orgId = existingConfig.orgId?.trim() || existingConfig.id;
   }
   await ensureDefaultTriageConfig(ownerEmail, orgId);
   await ensureOrganizationAutomations(ownerEmail, orgId);

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

@@ -27,6 +27,10 @@ The build location depends on the host. Treat this as a hard routing rule:
   `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.

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

@@ -50,6 +50,14 @@ 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

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

@@ -27,6 +27,10 @@ The build location depends on the host. Treat this as a hard routing rule:
   `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.

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

@@ -50,6 +50,14 @@ 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

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

@@ -27,6 +27,10 @@ The build location depends on the host. Treat this as a hard routing rule:
   `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.

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

@@ -50,6 +50,14 @@ 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

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

@@ -27,6 +27,10 @@ The build location depends on the host. Treat this as a hard routing rule:
   `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.

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

@@ -50,6 +50,14 @@ 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

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

@@ -27,6 +27,10 @@ The build location depends on the host. Treat this as a hard routing rule:
   `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.

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

@@ -50,6 +50,14 @@ 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

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"
             >

package/corpus/templates/slides/app/components/editor/ImageGenPanel.tsx

@@ -80,7 +80,7 @@ export function buildImageGenerationContext({
   }
 
   contextParts.push(
-    '\nGenerate 3 variations. Show each as an inline rendered image preview using markdown image syntax (![Variation 1](url)), not a plain text link — the chat renders "![]()" as an actual image but "[]()" as a bare link. Let the user pick their favorite, then insert the chosen generated image into the slide content in the right place.',
+    '\nGenerate 3 preview-only variations. Show each as an inline rendered image preview using markdown image syntax (![Variation 1](url)), not a plain text link — the chat renders "![]()" as an actual image but "[]()" as a bare link. After the user chooses one, place that preview URL with update-slide and then get-deck to verify the persisted slide HTML contains it before claiming success. For a direct one-image request instead, call `generate-image-api` with insertIntoSlide: true plus deckId and slideId; claim it was added only if the action returns inserted: true.',
   );
 
   return contextParts.join("\n");

package/corpus/templates/slides/changelog/2026-08-07-deleting-a-deck-no-longer-freezes-the-slides-browser.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-08-07
+---
+
+Deleting a deck no longer freezes the Slides browser

package/corpus/templates/slides/changelog/2026-08-07-slides-verify-generated-images-are-persisted-on-the-target-s.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-08-07
+---
+
+Slides verify generated images are persisted on the target slide