@runtypelabs/persona 4.6.1 → 4.7.0

package/dist/index.d.cts

@@ -6200,6 +6200,7 @@ declare class AgentWidgetClient {
     private sessionInitPromise;
     private lastSentClientToolsFingerprint;
     private clientToolsFingerprintSessionId;
+    private sentNonEmptyClientToolsSessionId;
     private readonly webMcpBridge;
     constructor(config?: AgentWidgetConfig);
     /**
@@ -6395,8 +6396,13 @@ declare class AgentWidgetClient {
      *  - **client-token mode**: POST `${apiBase}/v1/client/resume` (the
      *    session-authenticated sibling of `/v1/client/chat`; runtypelabs/core#3889),
      *    with the active `sessionId` in the body and no Bearer key: a browser
-     *    client-token page holds no secret. `clientTools` are already persisted
-     *    server-side from the dispatch turn, so only `toolOutputs` is re-sent.
+     *    client-token page holds no secret. The page's tool registry is
+     *    re-snapshotted and sent alongside `toolOutputs` via the same diff-only
+     *    `clientTools` / `clientToolsFingerprint` protocol as `/v1/client/chat`
+     *    (runtypelabs/core#5361), so tools registered by a mid-run page
+     *    navigation replace the run's dispatch-time set and become callable on
+     *    the next model turn. Old servers strip the unknown fields and keep the
+     *    frozen-at-dispatch behavior.
      *  - **dispatch / proxy mode**: POST `${apiUrl}/resume`: Runtype mounts
      *    resume as a child of `/v1/dispatch`, so the URL is `${apiUrl}/resume`,
      *    and proxies follow the same shape (`/api/chat/dispatch/resume`).
@@ -6408,6 +6414,39 @@ declare class AgentWidgetClient {
      * @param toolOutputs - Map keyed by per-call `toolCallId` (core#3878),
      *   falling back to tool name for legacy servers → the tool's result value.
      */
+    /**
+     * Diff-only / send-once WebMCP clientTools transport, shared by the
+     * client-token chat (`/v1/client/chat`) and resume (`/v1/client/resume`)
+     * paths — both routes speak the same protocol (runtypelabs/core#5361).
+     *
+     * Decides, against the shared fingerprint cache, whether this request ships
+     * the full `clientTools[]` + fingerprint (first send under this session, or
+     * a changed set) or the fingerprint alone (unchanged set; the server reuses
+     * its stored copy). Runs `doFetch` with the chosen fields and retries
+     * EXACTLY once with the full array on a
+     * `409 { error: 'client_tools_resend_required' }` registry miss — the retry
+     * is 409-*triggered*, never 409-*expected*, so servers predating the
+     * protocol (which strip the unknown fields and never 409) work unchanged.
+     * The 409 body is probed on a `clone()` so the original response body stays
+     * readable by the caller's error handling.
+     *
+     * The cache is NOT committed here: callers invoke the returned `commit()`
+     * only after the server has accepted the request (response OK / stream
+     * started), so a failed request can never record a fingerprint the server
+     * never stored. A resend-required miss invalidates the cached fingerprint
+     * immediately so later turns keep resending in full until a clean success
+     * commits a fresh one.
+     *
+     * `emptyMeansReplace` (resume only): when the live snapshot is empty but a
+     * non-empty set was committed under this session and never explicitly
+     * cleared (the paused tool navigated to a page with no tool registry), ship
+     * an explicit `clientTools: []` so the server REPLACES the persisted
+     * dispatch-time set with nothing and clears its stored registry. Chat keeps
+     * its omit-when-empty behavior: on `/chat`, absent fields already mean "no
+     * tools this turn", whereas on `/resume` absence means "keep the frozen
+     * dispatch-time set".
+     */
+    private sendWithClientToolsDiff;
     resumeFlow(executionId: string, toolOutputs: Record<string, unknown>, options?: {
         streamResponse?: boolean;
         signal?: AbortSignal;

package/dist/index.d.ts

@@ -6200,6 +6200,7 @@ declare class AgentWidgetClient {
     private sessionInitPromise;
     private lastSentClientToolsFingerprint;
     private clientToolsFingerprintSessionId;
+    private sentNonEmptyClientToolsSessionId;
     private readonly webMcpBridge;
     constructor(config?: AgentWidgetConfig);
     /**
@@ -6395,8 +6396,13 @@ declare class AgentWidgetClient {
      *  - **client-token mode**: POST `${apiBase}/v1/client/resume` (the
      *    session-authenticated sibling of `/v1/client/chat`; runtypelabs/core#3889),
      *    with the active `sessionId` in the body and no Bearer key: a browser
-     *    client-token page holds no secret. `clientTools` are already persisted
-     *    server-side from the dispatch turn, so only `toolOutputs` is re-sent.
+     *    client-token page holds no secret. The page's tool registry is
+     *    re-snapshotted and sent alongside `toolOutputs` via the same diff-only
+     *    `clientTools` / `clientToolsFingerprint` protocol as `/v1/client/chat`
+     *    (runtypelabs/core#5361), so tools registered by a mid-run page
+     *    navigation replace the run's dispatch-time set and become callable on
+     *    the next model turn. Old servers strip the unknown fields and keep the
+     *    frozen-at-dispatch behavior.
      *  - **dispatch / proxy mode**: POST `${apiUrl}/resume`: Runtype mounts
      *    resume as a child of `/v1/dispatch`, so the URL is `${apiUrl}/resume`,
      *    and proxies follow the same shape (`/api/chat/dispatch/resume`).
@@ -6408,6 +6414,39 @@ declare class AgentWidgetClient {
      * @param toolOutputs - Map keyed by per-call `toolCallId` (core#3878),
      *   falling back to tool name for legacy servers → the tool's result value.
      */
+    /**
+     * Diff-only / send-once WebMCP clientTools transport, shared by the
+     * client-token chat (`/v1/client/chat`) and resume (`/v1/client/resume`)
+     * paths — both routes speak the same protocol (runtypelabs/core#5361).
+     *
+     * Decides, against the shared fingerprint cache, whether this request ships
+     * the full `clientTools[]` + fingerprint (first send under this session, or
+     * a changed set) or the fingerprint alone (unchanged set; the server reuses
+     * its stored copy). Runs `doFetch` with the chosen fields and retries
+     * EXACTLY once with the full array on a
+     * `409 { error: 'client_tools_resend_required' }` registry miss — the retry
+     * is 409-*triggered*, never 409-*expected*, so servers predating the
+     * protocol (which strip the unknown fields and never 409) work unchanged.
+     * The 409 body is probed on a `clone()` so the original response body stays
+     * readable by the caller's error handling.
+     *
+     * The cache is NOT committed here: callers invoke the returned `commit()`
+     * only after the server has accepted the request (response OK / stream
+     * started), so a failed request can never record a fingerprint the server
+     * never stored. A resend-required miss invalidates the cached fingerprint
+     * immediately so later turns keep resending in full until a clean success
+     * commits a fresh one.
+     *
+     * `emptyMeansReplace` (resume only): when the live snapshot is empty but a
+     * non-empty set was committed under this session and never explicitly
+     * cleared (the paused tool navigated to a page with no tool registry), ship
+     * an explicit `clientTools: []` so the server REPLACES the persisted
+     * dispatch-time set with nothing and clears its stored registry. Chat keeps
+     * its omit-when-empty behavior: on `/chat`, absent fields already mean "no
+     * tools this turn", whereas on `/resume` absence means "keep the frozen
+     * dispatch-time set".
+     */
+    private sendWithClientToolsDiff;
     resumeFlow(executionId: string, toolOutputs: Record<string, unknown>, options?: {
         streamResponse?: boolean;
         signal?: AbortSignal;