@runtypelabs/persona 4.20.0 → 4.21.1

package/dist/index.d.cts

@@ -1684,8 +1684,10 @@ type RuntypeExecutionStreamEvent = ({
         message: string;
     };
     executionId: string;
+    finalOutput?: string;
     kind: "agent" | "flow";
     seq: number;
+    stopReason?: string;
     type: "execution_error";
     upgradeUrl?: string;
 }) | ({
@@ -3214,6 +3216,22 @@ type AgentWidgetWebMcpConfig = {
      * `window.confirm` fallback only applies when no widget UI is attached.
      */
     onConfirm?: WebMcpConfirmHandler;
+    /**
+     * How the widget runs the `webmcp:*` calls of ONE turn when the model emits
+     * several at once.
+     *
+     * - `'parallel'` (default): every call executes concurrently and a gated
+     *   sibling's approval never blocks another's execution. Right for
+     *   independent, order-insensitive tools (catalog lookups, add-to-cart).
+     * - `'sequential'`: calls execute one at a time, in the order the model
+     *   emitted them; the next starts only after the previous one settles
+     *   (including its approval bubble). Use this when the page tools share
+     *   mutable state that concurrent execution would interleave, e.g. a
+     *   canvas where every stroke selects a color/tool before drawing.
+     *
+     * Either way, all outputs still return to the server in a single `/resume`.
+     */
+    execution?: 'parallel' | 'sequential';
 };
 /**
  * Agent execution state tracking.
@@ -7722,6 +7740,10 @@ type ClientSession = {
     targetId?: string;
     /** Opaque change token; differs whenever the conversation transcript mutated. */
     conversationRevision?: string;
+    /** Server-negotiated durable reconnect support for this client-token session. */
+    durableRecovery?: {
+        enabled: boolean;
+    };
     /** Visitor grant backing history. `token` appears only at mint. */
     visitor?: ClientVisitorGrant;
     /** Configuration from the server */
@@ -7760,6 +7782,10 @@ type ClientInitResponse = {
     conversationId?: string;
     targetId?: string;
     conversationRevision?: string;
+    /** Present on servers that understand the durable-recovery negotiation. */
+    durableRecovery?: {
+        enabled: boolean;
+    };
     visitor?: ClientVisitorGrant;
     config: {
         welcomeMessage: string | null;
@@ -7843,6 +7869,17 @@ interface WidgetHistoryInternals {
     /** Persist the revision beside the active conversation id (internal only). */
     setStoredConversationRevision?: (revision: string | null) => void;
     getStoredConversationRevision?: () => string | null;
+    /** Internal client-token durable resume handle, persisted with widget state. */
+    setStoredResumableHandle?: (handle: {
+        executionId: string;
+        after: string;
+    } | null) => void;
+    getStoredResumableHandle?: () => {
+        executionId: string;
+        after: string;
+    } | null;
+    /** True only while Persona owns a persisted client-token recovery attempt. */
+    shouldResumeDurableConversation?: () => boolean;
     /** "Show earlier messages" cursor for the persisted transcript. */
     setStoredMessageCursor?: (cursor: string | null) => void;
     getStoredMessageCursor?: () => string | null;
@@ -10390,6 +10427,12 @@ declare class AgentWidgetClient {
      * Get the current client session (if any)
      */
     getClientSession(): ClientSession | null;
+    /** Persona's built-in reconnect transport for client-token sessions. */
+    reconnectClientTokenStream(ctx: {
+        executionId: string;
+        after: string;
+        signal: AbortSignal;
+    }): Promise<Response>;
     /**
      * Initialize session for client token mode.
      * Called automatically on first message if not already initialized.
@@ -10704,6 +10747,7 @@ declare class AgentWidgetClient {
     resumeFlow(executionId: string, toolOutputs: Record<string, unknown>, options?: {
         streamResponse?: boolean;
         signal?: AbortSignal;
+        after?: string;
     }): Promise<Response>;
     /**
      * The opt-in structured mention channel: the MOST RECENT user turn's
@@ -11584,10 +11628,12 @@ declare class AgentWidgetSession {
     /**
      * Resolve one or more parallel local-tool awaits sharing one paused
      * executionId with a SINGLE `/resume` (core#3878); `resolveWebMcpToolCall`
-     * delegates size-1 resolves here after its guards. Each call is executed
-     * against the page registry concurrently: every gated call renders its own
-     * native approval bubble, and a sibling's confirm Promise never blocks
-     * another's execution. Outputs are keyed by per-call `webMcpToolCallId`
+     * delegates size-1 resolves here after its guards. By default each call is
+     * executed against the page registry concurrently: every gated call renders
+     * its own native approval bubble, and a sibling's confirm Promise never
+     * blocks another's execution. With `webmcp.execution: "sequential"` the
+     * calls run one at a time in emission order instead (see the config docs
+     * for when that matters). Outputs are keyed by per-call `webMcpToolCallId`
      * (server prefers it over tool name; name-keying remains the fallback for
      * legacy single/distinct-tool turns), so two calls to the SAME tool no longer
      * collide. The server is tolerant: any call we omit (declined-after-abort,

package/dist/index.d.ts

@@ -1684,8 +1684,10 @@ type RuntypeExecutionStreamEvent = ({
         message: string;
     };
     executionId: string;
+    finalOutput?: string;
     kind: "agent" | "flow";
     seq: number;
+    stopReason?: string;
     type: "execution_error";
     upgradeUrl?: string;
 }) | ({
@@ -3214,6 +3216,22 @@ type AgentWidgetWebMcpConfig = {
      * `window.confirm` fallback only applies when no widget UI is attached.
      */
     onConfirm?: WebMcpConfirmHandler;
+    /**
+     * How the widget runs the `webmcp:*` calls of ONE turn when the model emits
+     * several at once.
+     *
+     * - `'parallel'` (default): every call executes concurrently and a gated
+     *   sibling's approval never blocks another's execution. Right for
+     *   independent, order-insensitive tools (catalog lookups, add-to-cart).
+     * - `'sequential'`: calls execute one at a time, in the order the model
+     *   emitted them; the next starts only after the previous one settles
+     *   (including its approval bubble). Use this when the page tools share
+     *   mutable state that concurrent execution would interleave, e.g. a
+     *   canvas where every stroke selects a color/tool before drawing.
+     *
+     * Either way, all outputs still return to the server in a single `/resume`.
+     */
+    execution?: 'parallel' | 'sequential';
 };
 /**
  * Agent execution state tracking.
@@ -7722,6 +7740,10 @@ type ClientSession = {
     targetId?: string;
     /** Opaque change token; differs whenever the conversation transcript mutated. */
     conversationRevision?: string;
+    /** Server-negotiated durable reconnect support for this client-token session. */
+    durableRecovery?: {
+        enabled: boolean;
+    };
     /** Visitor grant backing history. `token` appears only at mint. */
     visitor?: ClientVisitorGrant;
     /** Configuration from the server */
@@ -7760,6 +7782,10 @@ type ClientInitResponse = {
     conversationId?: string;
     targetId?: string;
     conversationRevision?: string;
+    /** Present on servers that understand the durable-recovery negotiation. */
+    durableRecovery?: {
+        enabled: boolean;
+    };
     visitor?: ClientVisitorGrant;
     config: {
         welcomeMessage: string | null;
@@ -7843,6 +7869,17 @@ interface WidgetHistoryInternals {
     /** Persist the revision beside the active conversation id (internal only). */
     setStoredConversationRevision?: (revision: string | null) => void;
     getStoredConversationRevision?: () => string | null;
+    /** Internal client-token durable resume handle, persisted with widget state. */
+    setStoredResumableHandle?: (handle: {
+        executionId: string;
+        after: string;
+    } | null) => void;
+    getStoredResumableHandle?: () => {
+        executionId: string;
+        after: string;
+    } | null;
+    /** True only while Persona owns a persisted client-token recovery attempt. */
+    shouldResumeDurableConversation?: () => boolean;
     /** "Show earlier messages" cursor for the persisted transcript. */
     setStoredMessageCursor?: (cursor: string | null) => void;
     getStoredMessageCursor?: () => string | null;
@@ -10390,6 +10427,12 @@ declare class AgentWidgetClient {
      * Get the current client session (if any)
      */
     getClientSession(): ClientSession | null;
+    /** Persona's built-in reconnect transport for client-token sessions. */
+    reconnectClientTokenStream(ctx: {
+        executionId: string;
+        after: string;
+        signal: AbortSignal;
+    }): Promise<Response>;
     /**
      * Initialize session for client token mode.
      * Called automatically on first message if not already initialized.
@@ -10704,6 +10747,7 @@ declare class AgentWidgetClient {
     resumeFlow(executionId: string, toolOutputs: Record<string, unknown>, options?: {
         streamResponse?: boolean;
         signal?: AbortSignal;
+        after?: string;
     }): Promise<Response>;
     /**
      * The opt-in structured mention channel: the MOST RECENT user turn's
@@ -11584,10 +11628,12 @@ declare class AgentWidgetSession {
     /**
      * Resolve one or more parallel local-tool awaits sharing one paused
      * executionId with a SINGLE `/resume` (core#3878); `resolveWebMcpToolCall`
-     * delegates size-1 resolves here after its guards. Each call is executed
-     * against the page registry concurrently: every gated call renders its own
-     * native approval bubble, and a sibling's confirm Promise never blocks
-     * another's execution. Outputs are keyed by per-call `webMcpToolCallId`
+     * delegates size-1 resolves here after its guards. By default each call is
+     * executed against the page registry concurrently: every gated call renders
+     * its own native approval bubble, and a sibling's confirm Promise never
+     * blocks another's execution. With `webmcp.execution: "sequential"` the
+     * calls run one at a time in emission order instead (see the config docs
+     * for when that matters). Outputs are keyed by per-call `webMcpToolCallId`
      * (server prefers it over tool name; name-keying remains the fallback for
      * legacy single/distinct-tool turns), so two calls to the SAME tool no longer
      * collide. The server is tolerant: any call we omit (declined-after-abort,