@genesislcap/ai-assistant 14.494.0 → 14.495.0

package/dist/ai-assistant.api.json

@@ -856,7 +856,7 @@
             {
               "kind": "PropertySignature",
               "canonicalReference": "@genesislcap/ai-assistant!AgenticActivityEvents#\"tool-loop-end\":member",
-              "docComment": "/**\n * Fired when the tool loop completes for the current turn and control returns to the user on the **main chat prompt** (i.e. the next free-form user message can now be accepted).\n *\n * Boundary: this is the moment the user regains control of the main chat input. It is **not** fired when a tool handler hands a widget to the user mid-loop (e.g. while a planning widget is awaiting a click) — widget pauses are still inside the loop, the assistant still owns the turn, and the main chat input may be hidden during them. Wait for this event when you need to know that the assistant is fully idle and the user can type freely again.\n *\n * Emitted from the finally block of each `ChatDriver`'s `sendMessage` and `continueFromHistory`, so a multi-agent handoff fires this event once per agent.\n *\n * Distinct from {@link AgenticActivityEvents.'halo-stop'} — the halo event tracks the spinner animation lifecycle (which can flap mid-turn as tool calls resolve), whereas this event is a one-shot per turn boundary. Use this for hooks tied to a turn ending (telemetry flushes, post-turn workspace transitions, deferred state recomputation).\n */\n",
+              "docComment": "/**\n * Fired when the tool loop completes for the current turn and control returns to the user on the **main chat prompt** (i.e. the next free-form user message can now be accepted).\n *\n * Boundary: this is the moment the user regains control of the main chat input. It is **not** fired when a tool handler hands a widget to the user mid-loop (e.g. while a planning widget is awaiting a click) — widget pauses are still inside the loop, the assistant still owns the turn, and the main chat input may be hidden during them. Wait for this event when you need to know that the assistant is fully idle and the user can type freely again.\n *\n * Emitted from the finally block of each `ChatDriver`'s `sendMessage` and `continueFromHistory`, so a multi-agent handoff fires this event once per agent.\n *\n * Distinct from {@link AgenticActivityEvents.'halo-stop'} — the halo event tracks the spinner animation lifecycle (which can flap mid-turn as tool calls resolve), whereas this event is a one-shot per turn boundary. Use this for hooks tied to a turn ending (telemetry flushes, post-turn workspace transitions, deferred state recomputation).\n *\n * The detail carries the turn's outcome (PTC-0): on a failure it is `{ failureReason }` with the typed `TurnFailureReason`; on a clean completion, a user cancel, a driver dispose, and an agent handoff the detail is `undefined` — the historical shape, kept byte-identical so subscribers that only care about the boundary can keep ignoring it. Structured-cloneable so it survives the cross-tab BroadcastChannel hop.\n */\n",
               "excerptTokens": [
                 {
                   "kind": "Content",
@@ -864,7 +864,16 @@
                 },
                 {
                   "kind": "Content",
-                  "text": "undefined"
+                  "text": "{\n        failureReason?: "
+                },
+                {
+                  "kind": "Reference",
+                  "text": "TurnFailureReason",
+                  "canonicalReference": "@genesislcap/foundation-ai!TurnFailureReason:type"
+                },
+                {
+                  "kind": "Content",
+                  "text": ";\n    } | undefined"
                 },
                 {
                   "kind": "Content",
@@ -877,7 +886,7 @@
               "name": "\"tool-loop-end\"",
               "propertyTypeTokenRange": {
                 "startIndex": 1,
-                "endIndex": 2
+                "endIndex": 4
               }
             },
             {

package/dist/ai-assistant.d.ts

@@ -18,6 +18,7 @@ import { InterfaceSymbol } from '@microsoft/fast-foundation';
 import type { Modal } from '@genesislcap/rapid-design-system';
 import { ModelTagAppearance } from '@genesislcap/foundation-ai';
 import type { SubAgentFailureReason } from '@genesislcap/foundation-ai';
+import type { TurnFailureReason } from '@genesislcap/foundation-ai';
 import { ViewTemplate } from '@genesislcap/web-core';
 
 /** Sentinel value used by the segmented control / select to represent "Auto". */
@@ -179,8 +180,16 @@ export declare interface AgenticActivityEvents {
      * spinner animation lifecycle (which can flap mid-turn as tool calls resolve), whereas
      * this event is a one-shot per turn boundary. Use this for hooks tied to a turn ending
      * (telemetry flushes, post-turn workspace transitions, deferred state recomputation).
+     *
+     * The detail carries the turn's outcome (PTC-0): on a failure it is `{ failureReason }`
+     * with the typed `TurnFailureReason`; on a clean completion, a user cancel, a
+     * driver dispose, and an agent handoff the detail is `undefined` — the historical shape,
+     * kept byte-identical so subscribers that only care about the boundary can keep ignoring
+     * it. Structured-cloneable so it survives the cross-tab BroadcastChannel hop.
      */
-    'tool-loop-end': undefined;
+    'tool-loop-end': {
+        failureReason?: TurnFailureReason;
+    } | undefined;
     /**
      * Fired when a tool handler hands a widget to the user mid-loop and parks awaiting it
      * (`requestInteraction`) — the turn is suspended between provider calls, with no request
@@ -1268,6 +1277,23 @@ export declare class ChatDriver extends EventTarget implements AiDriver {
      * cached history would otherwise gain a stray marker on remount).
      */
     private completeAbortedTurn;
+    /**
+     * Build the `done` loop result, carrying the typed failure reason when the turn
+     * bailed (PTC-0). The discriminant stays `'done'` either way — the same value a
+     * clean turn returns — so consumers matching on `reason === 'done'` are unchanged;
+     * `failureReason` is simply present on a failure and absent on success. Omitted
+     * (rather than set to `undefined`) so a happy-path result stays byte-identical to
+     * the historical `{ reason: 'done' }`.
+     */
+    private turnDone;
+    /** The typed failure reason on a loop result, or `undefined` for a clean turn / handoff. */
+    private static failureReasonOf;
+    /**
+     * Build the `tool-loop-end` event detail for a turn's result. A failure carries a
+     * `{ failureReason }` detail; a clean turn emits `undefined` — the historical shape,
+     * kept byte-identical so subscribers see exactly what they always have.
+     */
+    private static loopEndDetail;
     /**
      * Swap in a new agent's configuration. Called by OrchestratingDriver before
      * each specialist turn so the shared driver runs with the right tools and prompt.
@@ -3698,6 +3724,8 @@ export declare interface ToolTreeNode extends ChatToolDefinition {
     tools?: ToolTreeNode[];
 }
 
+export { TurnFailureReason }
+
 /**
  * One captured frame of what the LLM saw on a single tool-loop iteration.
  * The driver records these as a ring buffer (cap: configurable via

package/dist/custom-elements.json

@@ -151,6 +151,14 @@
             "package": "./utils/tool-fold"
           }
         },
+        {
+          "kind": "js",
+          "name": "TurnFailureReason",
+          "declaration": {
+            "name": "TurnFailureReason",
+            "module": "./state/debug-event-log"
+          }
+        },
         {
           "kind": "js",
           "name": "TimelineMessage",
@@ -865,6 +873,195 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "src/config/config.ts",
+      "declarations": [
+        {
+          "kind": "function",
+          "name": "defineAgent",
+          "description": "Identity helper that infers the narrowest possible type for an agent config,\npreserving string literal types (including `name`) without requiring `as const`.\n\nUse this when you need `typeof myAgent` to carry the literal `name` type —\nfor example, when wiring `ChatToolHandlers<typeof myAgent>`.\n\n```ts\nconst myAgent = defineAgent({ name: 'my_agent', ... });\ntype Handlers = ChatToolHandlers<typeof myAgent>;\n// requestSubAgent name param is now typed as 'my_agent'\n```"
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "CachePolicy",
+          "declaration": {
+            "name": "CachePolicy",
+            "module": "src/config/config.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "ChatInputDuringExecutionMode",
+          "declaration": {
+            "name": "ChatInputDuringExecutionMode",
+            "module": "src/config/config.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "ChatToolChoice",
+          "declaration": {
+            "name": "ChatToolChoice",
+            "module": "src/config/config.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "defineAgent",
+          "declaration": {
+            "name": "defineAgent",
+            "module": "src/config/config.ts"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/config/define-stateful-agent.ts",
+      "declarations": [
+        {
+          "kind": "function",
+          "name": "restoreMachine",
+          "return": {
+            "type": {
+              "text": "void"
+            }
+          },
+          "parameters": [
+            {
+              "name": "machine",
+              "type": {
+                "text": "{ stop: () => void; start: (options?: { state?: unknown }) => void }"
+              },
+              "description": "the machine to restore (already constructed/started)."
+            },
+            {
+              "name": "restored",
+              "type": {
+                "text": "unknown"
+              },
+              "description": "the agent's serialized image (`ctx.restored` in `init`)."
+            },
+            {
+              "name": "key",
+              "default": "'machine'",
+              "description": "the property the machine occupies in the snapshot; defaults to\n`'machine'` to match the conventional `{ machine }` state bag."
+            }
+          ],
+          "description": "Restore a foundation-state-machine instance from a snapshot produced by the\ndefault serializer (or `machine.getPersistedSnapshot()`). Call inside a\nstateful agent's `init` to resume the machine in its exact prior place:\n\n```ts\ninit: ({ restored }) => {\n  const machine = new MyMachine();\n  restoreMachine(machine, restored); // resume, or no-op on a fresh start\n  return { machine };\n}\n```\n\nNo-ops when there is nothing to restore (a fresh session), leaving the\nfreshly-constructed machine in its initial state."
+        },
+        {
+          "kind": "function",
+          "name": "defineStatefulAgent",
+          "return": {
+            "type": {
+              "text": "AgentConfig"
+            }
+          },
+          "parameters": [
+            {
+              "name": "opts",
+              "type": {
+                "text": "StatefulAgentInit<S>"
+              }
+            }
+          ],
+          "description": "Build an `AgentConfig` whose `systemPrompt`, `toolDefinitions`, and tool\nhandlers all close over a long-lived state object created on activation.\n\nThe framework wires the lifecycle: `init` on `onActivate`, `dispose` on\n`onDeactivate`. State is held inside the helper's closure — never exposed on\nthe resulting `AgentConfig` — so the redux serializer doesn't see it."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "restoreMachine",
+          "declaration": {
+            "name": "restoreMachine",
+            "module": "src/config/define-stateful-agent.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "defineStatefulAgent",
+          "declaration": {
+            "name": "defineStatefulAgent",
+            "module": "src/config/define-stateful-agent.ts"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/config/fallback-agents.ts",
+      "declarations": [
+        {
+          "kind": "variable",
+          "name": "friendlyFallbackAgent",
+          "type": {
+            "text": "FallbackAgentConfig"
+          },
+          "default": "{\n  name: 'Assistant',\n  fallback: true,\n  systemPrompt: `You are a warm, friendly assistant. For general conversation like \"Hi\" or \"How are you\", you can have a friendly chat. For anything more complex, you cannot directly help, but you can explain what specialists are available. The available specialists are:\\n\\n{{agents}}\\n\\nPolitely let the user know what you can help with and invite them to rephrase their request if it is outside your scope.`,\n}",
+          "description": "A warm, conversational fallback agent. Acknowledges it can't help directly,\nexplains what the available specialists can do, and invites the user to retry.\n\nThe system prompt is generated at runtime by `OrchestratingDriver` from the\nspecialist list — no manual authoring required."
+        },
+        {
+          "kind": "variable",
+          "name": "strictFallbackAgent",
+          "type": {
+            "text": "FallbackAgentConfig"
+          },
+          "default": "{\n  name: 'Assistant',\n  fallback: true,\n  systemPrompt: `You are a concise assistant. The user's request is outside your scope. Respond with a single short sentence stating what you can assist with. Do not elaborate. The available specialists are: {{agents}}.`,\n}",
+          "description": "A brief, professional fallback agent. States what is available without\nelaboration. The `{{agents}}` placeholder is replaced at runtime by\n`OrchestratingDriver` with the generated specialist list."
+        }
+      ],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "friendlyFallbackAgent",
+          "declaration": {
+            "name": "friendlyFallbackAgent",
+            "module": "src/config/fallback-agents.ts"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "strictFallbackAgent",
+          "declaration": {
+            "name": "strictFallbackAgent",
+            "module": "src/config/fallback-agents.ts"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/config/index.ts",
+      "declarations": [],
+      "exports": [
+        {
+          "kind": "js",
+          "name": "*",
+          "declaration": {
+            "name": "*",
+            "package": "./config"
+          }
+        },
+        {
+          "kind": "js",
+          "name": "*",
+          "declaration": {
+            "name": "*",
+            "package": "./fallback-agents"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "src/config/validate-providers.ts",
+      "declarations": [],
+      "exports": []
+    },
     {
       "kind": "javascript-module",
       "path": "src/main/index.ts",
@@ -3536,195 +3733,6 @@
         }
       ]
     },
-    {
-      "kind": "javascript-module",
-      "path": "src/config/config.ts",
-      "declarations": [
-        {
-          "kind": "function",
-          "name": "defineAgent",
-          "description": "Identity helper that infers the narrowest possible type for an agent config,\npreserving string literal types (including `name`) without requiring `as const`.\n\nUse this when you need `typeof myAgent` to carry the literal `name` type —\nfor example, when wiring `ChatToolHandlers<typeof myAgent>`.\n\n```ts\nconst myAgent = defineAgent({ name: 'my_agent', ... });\ntype Handlers = ChatToolHandlers<typeof myAgent>;\n// requestSubAgent name param is now typed as 'my_agent'\n```"
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "CachePolicy",
-          "declaration": {
-            "name": "CachePolicy",
-            "module": "src/config/config.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "ChatInputDuringExecutionMode",
-          "declaration": {
-            "name": "ChatInputDuringExecutionMode",
-            "module": "src/config/config.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "ChatToolChoice",
-          "declaration": {
-            "name": "ChatToolChoice",
-            "module": "src/config/config.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "defineAgent",
-          "declaration": {
-            "name": "defineAgent",
-            "module": "src/config/config.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/config/define-stateful-agent.ts",
-      "declarations": [
-        {
-          "kind": "function",
-          "name": "restoreMachine",
-          "return": {
-            "type": {
-              "text": "void"
-            }
-          },
-          "parameters": [
-            {
-              "name": "machine",
-              "type": {
-                "text": "{ stop: () => void; start: (options?: { state?: unknown }) => void }"
-              },
-              "description": "the machine to restore (already constructed/started)."
-            },
-            {
-              "name": "restored",
-              "type": {
-                "text": "unknown"
-              },
-              "description": "the agent's serialized image (`ctx.restored` in `init`)."
-            },
-            {
-              "name": "key",
-              "default": "'machine'",
-              "description": "the property the machine occupies in the snapshot; defaults to\n`'machine'` to match the conventional `{ machine }` state bag."
-            }
-          ],
-          "description": "Restore a foundation-state-machine instance from a snapshot produced by the\ndefault serializer (or `machine.getPersistedSnapshot()`). Call inside a\nstateful agent's `init` to resume the machine in its exact prior place:\n\n```ts\ninit: ({ restored }) => {\n  const machine = new MyMachine();\n  restoreMachine(machine, restored); // resume, or no-op on a fresh start\n  return { machine };\n}\n```\n\nNo-ops when there is nothing to restore (a fresh session), leaving the\nfreshly-constructed machine in its initial state."
-        },
-        {
-          "kind": "function",
-          "name": "defineStatefulAgent",
-          "return": {
-            "type": {
-              "text": "AgentConfig"
-            }
-          },
-          "parameters": [
-            {
-              "name": "opts",
-              "type": {
-                "text": "StatefulAgentInit<S>"
-              }
-            }
-          ],
-          "description": "Build an `AgentConfig` whose `systemPrompt`, `toolDefinitions`, and tool\nhandlers all close over a long-lived state object created on activation.\n\nThe framework wires the lifecycle: `init` on `onActivate`, `dispose` on\n`onDeactivate`. State is held inside the helper's closure — never exposed on\nthe resulting `AgentConfig` — so the redux serializer doesn't see it."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "restoreMachine",
-          "declaration": {
-            "name": "restoreMachine",
-            "module": "src/config/define-stateful-agent.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "defineStatefulAgent",
-          "declaration": {
-            "name": "defineStatefulAgent",
-            "module": "src/config/define-stateful-agent.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/config/fallback-agents.ts",
-      "declarations": [
-        {
-          "kind": "variable",
-          "name": "friendlyFallbackAgent",
-          "type": {
-            "text": "FallbackAgentConfig"
-          },
-          "default": "{\n  name: 'Assistant',\n  fallback: true,\n  systemPrompt: `You are a warm, friendly assistant. For general conversation like \"Hi\" or \"How are you\", you can have a friendly chat. For anything more complex, you cannot directly help, but you can explain what specialists are available. The available specialists are:\\n\\n{{agents}}\\n\\nPolitely let the user know what you can help with and invite them to rephrase their request if it is outside your scope.`,\n}",
-          "description": "A warm, conversational fallback agent. Acknowledges it can't help directly,\nexplains what the available specialists can do, and invites the user to retry.\n\nThe system prompt is generated at runtime by `OrchestratingDriver` from the\nspecialist list — no manual authoring required."
-        },
-        {
-          "kind": "variable",
-          "name": "strictFallbackAgent",
-          "type": {
-            "text": "FallbackAgentConfig"
-          },
-          "default": "{\n  name: 'Assistant',\n  fallback: true,\n  systemPrompt: `You are a concise assistant. The user's request is outside your scope. Respond with a single short sentence stating what you can assist with. Do not elaborate. The available specialists are: {{agents}}.`,\n}",
-          "description": "A brief, professional fallback agent. States what is available without\nelaboration. The `{{agents}}` placeholder is replaced at runtime by\n`OrchestratingDriver` with the generated specialist list."
-        }
-      ],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "friendlyFallbackAgent",
-          "declaration": {
-            "name": "friendlyFallbackAgent",
-            "module": "src/config/fallback-agents.ts"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "strictFallbackAgent",
-          "declaration": {
-            "name": "strictFallbackAgent",
-            "module": "src/config/fallback-agents.ts"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/config/index.ts",
-      "declarations": [],
-      "exports": [
-        {
-          "kind": "js",
-          "name": "*",
-          "declaration": {
-            "name": "*",
-            "package": "./config"
-          }
-        },
-        {
-          "kind": "js",
-          "name": "*",
-          "declaration": {
-            "name": "*",
-            "package": "./fallback-agents"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "src/config/validate-providers.ts",
-      "declarations": [],
-      "exports": []
-    },
     {
       "kind": "javascript-module",
       "path": "src/state/ai-assistant-slice.ts",
@@ -3971,6 +3979,14 @@
             "module": "src/state/debug-event-log.ts"
           }
         },
+        {
+          "kind": "js",
+          "name": "TurnFailureReason",
+          "declaration": {
+            "name": "TurnFailureReason",
+            "module": "src/state/debug-event-log.ts"
+          }
+        },
         {
           "kind": "js",
           "name": "recordTurnError",
@@ -6892,6 +6908,66 @@
               },
               "description": "Finish a turn whose signal aborted. A user cancel adds a subtle \"Stopped.\"\nmarker; a dispose-driven abort stops quietly (the widget is gone and the\ncached history would otherwise gain a stray marker on remount)."
             },
+            {
+              "kind": "method",
+              "name": "turnDone",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "ChatDriverResult"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "failureReason",
+                  "optional": true,
+                  "type": {
+                    "text": "TurnFailureReason"
+                  }
+                }
+              ],
+              "description": "Build the `done` loop result, carrying the typed failure reason when the turn\nbailed (PTC-0). The discriminant stays `'done'` either way — the same value a\nclean turn returns — so consumers matching on `reason === 'done'` are unchanged;\n`failureReason` is simply present on a failure and absent on success. Omitted\n(rather than set to `undefined`) so a happy-path result stays byte-identical to\nthe historical `{ reason: 'done' }`."
+            },
+            {
+              "kind": "method",
+              "name": "failureReasonOf",
+              "privacy": "private",
+              "static": true,
+              "return": {
+                "type": {
+                  "text": "TurnFailureReason | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "result",
+                  "type": {
+                    "text": "ChatDriverResult"
+                  }
+                }
+              ],
+              "description": "The typed failure reason on a loop result, or `undefined` for a clean turn / handoff."
+            },
+            {
+              "kind": "method",
+              "name": "loopEndDetail",
+              "privacy": "private",
+              "static": true,
+              "return": {
+                "type": {
+                  "text": "{ failureReason: TurnFailureReason } | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "result",
+                  "type": {
+                    "text": "ChatDriverResult"
+                  }
+                }
+              ],
+              "description": "Build the `tool-loop-end` event detail for a turn's result. A failure carries a\n`{ failureReason }` detail; a clean turn emits `undefined` — the historical shape,\nkept byte-identical so subscribers see exactly what they always have."
+            },
             {
               "kind": "method",
               "name": "applyAgent",

package/dist/dts/channel/ai-activity-channel.d.ts

@@ -1,3 +1,4 @@
+import type { TurnFailureReason } from '@genesislcap/foundation-ai';
 /**
  * Event map for the AI activity bus.
  *
@@ -61,8 +62,16 @@ export interface AgenticActivityEvents {
      * spinner animation lifecycle (which can flap mid-turn as tool calls resolve), whereas
      * this event is a one-shot per turn boundary. Use this for hooks tied to a turn ending
      * (telemetry flushes, post-turn workspace transitions, deferred state recomputation).
+     *
+     * The detail carries the turn's outcome (PTC-0): on a failure it is `{ failureReason }`
+     * with the typed `TurnFailureReason`; on a clean completion, a user cancel, a
+     * driver dispose, and an agent handoff the detail is `undefined` — the historical shape,
+     * kept byte-identical so subscribers that only care about the boundary can keep ignoring
+     * it. Structured-cloneable so it survives the cross-tab BroadcastChannel hop.
      */
-    'tool-loop-end': undefined;
+    'tool-loop-end': {
+        failureReason?: TurnFailureReason;
+    } | undefined;
     /**
      * Fired when a tool handler hands a widget to the user mid-loop and parks awaiting it
      * (`requestInteraction`) — the turn is suspended between provider calls, with no request

package/dist/dts/channel/ai-activity-channel.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ai-activity-channel.d.ts","sourceRoot":"","sources":["../../../src/channel/ai-activity-channel.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,MAAM,WAAW,qBAAqB;IACpC,2FAA2F;IAC3F,YAAY,EAAE;QAAE,SAAS,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC;IACtC,iFAAiF;IACjF,WAAW,EAAE,SAAS,CAAC;IACvB,mJAAmJ;IACnJ,aAAa,EAAE,SAAS,CAAC;IACzB,wJAAwJ;IACxJ,YAAY,EAAE,SAAS,CAAC;IACxB;;;;;;;;;;;;;;;;;;OAkBG;IACH,iBAAiB,EAAE,SAAS,CAAC;IAC7B;;;;;;;;;;;;;;;;;;OAkBG;IACH,eAAe,EAAE,SAAS,CAAC;IAC3B;;;;;;;;;;;OAWG;IACH,uBAAuB,EAAE,SAAS,CAAC;IACnC;;;;;OAKG;IACH,sBAAsB,EAAE,SAAS,CAAC;CACnC"}
+{"version":3,"file":"ai-activity-channel.d.ts","sourceRoot":"","sources":["../../../src/channel/ai-activity-channel.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,4BAA4B,CAAC;AAEpE;;;;;;;;;;;;;GAaG;AACH,MAAM,WAAW,qBAAqB;IACpC,2FAA2F;IAC3F,YAAY,EAAE;QAAE,SAAS,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC;IACtC,iFAAiF;IACjF,WAAW,EAAE,SAAS,CAAC;IACvB,mJAAmJ;IACnJ,aAAa,EAAE,SAAS,CAAC;IACzB,wJAAwJ;IACxJ,YAAY,EAAE,SAAS,CAAC;IACxB;;;;;;;;;;;;;;;;;;OAkBG;IACH,iBAAiB,EAAE,SAAS,CAAC;IAC7B;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;IACH,eAAe,EAAE;QAAE,aAAa,CAAC,EAAE,iBAAiB,CAAA;KAAE,GAAG,SAAS,CAAC;IACnE;;;;;;;;;;;OAWG;IACH,uBAAuB,EAAE,SAAS,CAAC;IACnC;;;;;OAKG;IACH,sBAAsB,EAAE,SAAS,CAAC;CACnC"}

package/dist/dts/components/chat-driver/chat-driver.d.ts

@@ -398,6 +398,23 @@ export declare class ChatDriver extends EventTarget implements AiDriver {
      * cached history would otherwise gain a stray marker on remount).
      */
     private completeAbortedTurn;
+    /**
+     * Build the `done` loop result, carrying the typed failure reason when the turn
+     * bailed (PTC-0). The discriminant stays `'done'` either way — the same value a
+     * clean turn returns — so consumers matching on `reason === 'done'` are unchanged;
+     * `failureReason` is simply present on a failure and absent on success. Omitted
+     * (rather than set to `undefined`) so a happy-path result stays byte-identical to
+     * the historical `{ reason: 'done' }`.
+     */
+    private turnDone;
+    /** The typed failure reason on a loop result, or `undefined` for a clean turn / handoff. */
+    private static failureReasonOf;
+    /**
+     * Build the `tool-loop-end` event detail for a turn's result. A failure carries a
+     * `{ failureReason }` detail; a clean turn emits `undefined` — the historical shape,
+     * kept byte-identical so subscribers see exactly what they always have.
+     */
+    private static loopEndDetail;
     /**
      * Swap in a new agent's configuration. Called by OrchestratingDriver before
      * each specialist turn so the shared driver runs with the right tools and prompt.