@runtypelabs/persona 4.28.0 → 4.28.1

package/dist/session-reconnect.d.cts

@@ -3214,9 +3214,8 @@ type WebMcpConfirmInfo = {
     };
     /**
      * Why the confirm was requested. Currently always `'gate'`: the default
-     * confirm-by-default gate that fires before every `webmcp:*` call. (The
-     * `@mcp-b/webmcp-polyfill` owns the spec's `requestUserInteraction` callback
-     * internally, so Persona no longer surfaces a nested in-tool confirm.)
+     * confirm-by-default gate that fires before every `webmcp:*` call. Tool
+     * callbacks on v6 receive an AbortSignal, not a nested confirmation API.
      */
     reason: 'gate';
 };
@@ -9287,8 +9286,11 @@ type AgentWidgetConfig = {
     /**
      * WebMCP: consume page-registered tools (`document.modelContext.registerTool`).
      * When `enabled`, the widget installs `@mcp-b/webmcp-polyfill`, snapshots the
-     * registry on every dispatch, ships it as `clientTools[]`, and executes
-     * returned `webmcp:*` tool calls with confirm-by-default gating.
+     * current document's registry on every dispatch, ships it as `clientTools[]`,
+     * and executes returned `webmcp:*` calls with confirm-by-default gating.
+     * Supports host-installed v5 JSON-string and v6 object-input contracts.
+     * The automatic fallback stays on v5 to preserve existing browser support
+     * and callback-result behavior.
      *
      * Server-side policy on the chat surface is the source of truth: these
      * fields layer on top.

package/dist/session-reconnect.d.ts

@@ -3214,9 +3214,8 @@ type WebMcpConfirmInfo = {
     };
     /**
      * Why the confirm was requested. Currently always `'gate'`: the default
-     * confirm-by-default gate that fires before every `webmcp:*` call. (The
-     * `@mcp-b/webmcp-polyfill` owns the spec's `requestUserInteraction` callback
-     * internally, so Persona no longer surfaces a nested in-tool confirm.)
+     * confirm-by-default gate that fires before every `webmcp:*` call. Tool
+     * callbacks on v6 receive an AbortSignal, not a nested confirmation API.
      */
     reason: 'gate';
 };
@@ -9287,8 +9286,11 @@ type AgentWidgetConfig = {
     /**
      * WebMCP: consume page-registered tools (`document.modelContext.registerTool`).
      * When `enabled`, the widget installs `@mcp-b/webmcp-polyfill`, snapshots the
-     * registry on every dispatch, ships it as `clientTools[]`, and executes
-     * returned `webmcp:*` tool calls with confirm-by-default gating.
+     * current document's registry on every dispatch, ships it as `clientTools[]`,
+     * and executes returned `webmcp:*` calls with confirm-by-default gating.
+     * Supports host-installed v5 JSON-string and v6 object-input contracts.
+     * The automatic fallback stays on v5 to preserve existing browser support
+     * and callback-result behavior.
      *
      * Server-side policy on the chat surface is the source of truth: these
      * fields layer on top.

package/dist/smart-dom-reader.d.cts

@@ -3483,9 +3483,8 @@ type WebMcpConfirmInfo = {
     };
     /**
      * Why the confirm was requested. Currently always `'gate'`: the default
-     * confirm-by-default gate that fires before every `webmcp:*` call. (The
-     * `@mcp-b/webmcp-polyfill` owns the spec's `requestUserInteraction` callback
-     * internally, so Persona no longer surfaces a nested in-tool confirm.)
+     * confirm-by-default gate that fires before every `webmcp:*` call. Tool
+     * callbacks on v6 receive an AbortSignal, not a nested confirmation API.
      */
     reason: 'gate';
 };
@@ -9556,8 +9555,11 @@ type AgentWidgetConfig = {
     /**
      * WebMCP: consume page-registered tools (`document.modelContext.registerTool`).
      * When `enabled`, the widget installs `@mcp-b/webmcp-polyfill`, snapshots the
-     * registry on every dispatch, ships it as `clientTools[]`, and executes
-     * returned `webmcp:*` tool calls with confirm-by-default gating.
+     * current document's registry on every dispatch, ships it as `clientTools[]`,
+     * and executes returned `webmcp:*` calls with confirm-by-default gating.
+     * Supports host-installed v5 JSON-string and v6 object-input contracts.
+     * The automatic fallback stays on v5 to preserve existing browser support
+     * and callback-result behavior.
      *
      * Server-side policy on the chat surface is the source of truth: these
      * fields layer on top.

package/dist/smart-dom-reader.d.ts

@@ -3483,9 +3483,8 @@ type WebMcpConfirmInfo = {
     };
     /**
      * Why the confirm was requested. Currently always `'gate'`: the default
-     * confirm-by-default gate that fires before every `webmcp:*` call. (The
-     * `@mcp-b/webmcp-polyfill` owns the spec's `requestUserInteraction` callback
-     * internally, so Persona no longer surfaces a nested in-tool confirm.)
+     * confirm-by-default gate that fires before every `webmcp:*` call. Tool
+     * callbacks on v6 receive an AbortSignal, not a nested confirmation API.
      */
     reason: 'gate';
 };
@@ -9556,8 +9555,11 @@ type AgentWidgetConfig = {
     /**
      * WebMCP: consume page-registered tools (`document.modelContext.registerTool`).
      * When `enabled`, the widget installs `@mcp-b/webmcp-polyfill`, snapshots the
-     * registry on every dispatch, ships it as `clientTools[]`, and executes
-     * returned `webmcp:*` tool calls with confirm-by-default gating.
+     * current document's registry on every dispatch, ships it as `clientTools[]`,
+     * and executes returned `webmcp:*` calls with confirm-by-default gating.
+     * Supports host-installed v5 JSON-string and v6 object-input contracts.
+     * The automatic fallback stays on v5 to preserve existing browser support
+     * and callback-result behavior.
      *
      * Server-side policy on the chat surface is the source of truth: these
      * fields layer on top.