fix(mastra): migrate approval details to interrupt sessions

Author: blove

apps/website/content/docs/runtimes/mastra/how-it-connects.mdx

@@ -18,13 +18,13 @@ This page records the AG-UI wire behavior measured for Mastra on 2026-08-31. It
 
 The service refuses to boot without `AG_UI_INTERNAL_TOKEN`, rejects any non-health route without a matching header, and maps an error from the underlying observable to a `RUN_ERROR` frame rather than dropping the socket. Any route other than `/ok` that arrives without a matching header returns `401 {"detail":"unauthorized"}`; with a valid token, an unknown path or method returns `404 {"detail":"not found"}` and an unregistered topic returns `404 {"detail":"no such topic: <topic>"}`.
 
-In your own application this is still an ordinary `provideAgent({ url: '/agent' })`; the example in this repository passes a factory only because it resolves its endpoint at runtime. The token is injected by the dev proxy in front of the app, never by the browser.
+In your own application this is still an ordinary `provideAgent({ url: '/agent', interruptTransport: 'mastra-command' })`; the example in this repository passes a factory only because it resolves its endpoint at runtime. The token is injected by the dev proxy in front of the app, never by the browser.
 
 ## Interrupts arrive by both conventions
 
 Mastra is the only measured runtime that signals an interrupt twice: it emits a `CUSTOM` event named `on_interrupt` **and** finishes the run with the protocol-standard interrupt outcome.
 
-AWS Strands and Microsoft Agent Framework emit only the outcome. The LangGraph bridge emits only `on_interrupt`. The adapter accepts either, and within a single run the first signal it sees wins, so a runtime that emits both is handled without special-casing.
+AWS Strands and Microsoft Agent Framework emit only the outcome. The LangGraph bridge emits only `on_interrupt`. The adapter retains both forms in one session. The native batch drives the display projection, while `interruptSession().legacy?.value` preserves the Mastra suspend details used by the approval card.
 
 ## Resume uses interruptEvent
 
@@ -40,7 +40,7 @@ Mastra reads resume data from `forwardedProps.command.interruptEvent`, carrying
 }
 ```
 
-That is a third distinct shape. Strands and Microsoft Agent Framework read a top-level `resume` array; the LangGraph bridge reads `forwardedProps.command.resume`. Application code passes one neutral `submit({ resume })` and the adapter derives the wire shape from how the interrupt arrived.
+That is a third distinct shape. Strands and Microsoft Agent Framework read a top-level `resume` array; the LangGraph bridge reads `forwardedProps.command.resume`. Application code passes one neutral `submit({ resume })`. The Mastra provider selects `interruptTransport: 'mastra-command'` explicitly because this backend emits both compatibility and native interrupts, and `auto` otherwise selects the native wire shape.
 
 ## Suspend and resume require persistent storage
 

apps/website/content/docs/runtimes/mastra/overview.mdx

@@ -113,7 +113,7 @@ The class supplies that payload and maps the two actions onto resume calls.
 
 <ExampleCode file="mastra.component.ts" region="approval-actions" title="mastra.component.ts — reading the interrupt and resuming" />
 
-`agent.interrupt()` carries the parsed `CUSTOM on_interrupt` payload as its `value`, and because that payload carries a tool-call id, `submit({ resume })` goes back out as `forwardedProps.command = { resume, interruptEvent: { toolCallId, runId } }` — the shape the Mastra bridge reads to reopen the suspended run.
+`agent.interruptSession().legacy?.value` carries the parsed `CUSTOM on_interrupt` payload alongside the native interrupt batch. The provider selects `interruptTransport: 'mastra-command'`, so `submit({ resume })` goes back out as `forwardedProps.command = { resume, interruptEvent: { toolCallId, runId } }` — the shape the Mastra bridge reads to reopen the suspended run.
 
 ## What the integration demonstrates
 

cockpit/runtimes/mastra/angular/src/app/app.config.ts

@@ -11,6 +11,7 @@ export const appConfig: ApplicationConfig = {
       }
       return {
         url: connection.url,
+        interruptTransport: 'mastra-command',
       };
     }),
   ],

cockpit/runtimes/mastra/angular/src/app/mastra.component.ts

@@ -50,8 +50,9 @@ interface PackingList {
  *   packing list.
  * - A suspended tool (`reserve_campsite`) surfaces BOTH interrupt
  *   conventions: CUSTOM `on_interrupt` (payload carrying toolCallId + runId)
- *   and the protocol-standard RUN_FINISHED interrupt outcome. The reducer's
- *   first-signal-wins rule keeps the Mastra-shaped payload, so
+ *   and the protocol-standard RUN_FINISHED interrupt outcome. The session
+ *   retains the Mastra payload alongside the native batch. The explicit
+ *   `mastra-command` transport in app.config.ts ensures
  *   `submit({ resume })` goes out as
  *   `forwardedProps.command = { resume, interruptEvent: { toolCallId, runId } }`
  *   — exactly what the Mastra bridge requires to resume the suspended run.
@@ -251,13 +252,13 @@ export class MastraComponent {
 
   // #region approval-actions
   /**
-   * The pending Mastra suspend. The reducer stores the parsed CUSTOM
+   * The pending Mastra suspend. The session retains the parsed CUSTOM
    * `on_interrupt` payload: `{ type: 'mastra_suspend', toolCallId, toolName,
-   * suspendPayload, args, resumeSchema, runId }` (first-signal-wins over the
-   * RUN_FINISHED outcome that follows it on the wire).
+   * suspendPayload, args, resumeSchema, runId }` alongside the native
+   * RUN_FINISHED outcome that follows it on the wire.
    */
   private readonly suspendValue = computed(() => {
-    return this.agent.interrupt?.()?.value as
+    return this.agent.interruptSession().legacy?.value as
       | { toolName?: string; suspendPayload?: { site?: string; nights?: number; total_usd?: number } }
       | undefined;
   });