@genesislcap/ai-assistant 15.58.1 → 15.59.0

package/dist/esm/main/main.js

@@ -1206,7 +1206,7 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
         var _a, _b, _c, _d;
         const previous = (_b = (_a = this._sessionRef) === null || _a === void 0 ? void 0 : _a.store.aiAssistant.pinnedAgentName) !== null && _b !== void 0 ? _b : null;
         (_c = this._sessionRef) === null || _c === void 0 ? void 0 : _c.actions.aiAssistant.setPinnedAgentName(value);
-        (_d = this.orchestrator) === null || _d === void 0 ? void 0 : _d.setPinnedAgent(value);
+        (_d = this.driver) === null || _d === void 0 ? void 0 : _d.setPinnedAgent(value);
         // Suggestions are scoped to the active routing — resetting forces a fresh
         // fetch when the user pins/unpins so the prompts match the new agent.
         if (previous !== value) {
@@ -1231,7 +1231,7 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
     set flowOwnerAgentName(value) {
         var _a, _b;
         (_a = this._sessionRef) === null || _a === void 0 ? void 0 : _a.actions.aiAssistant.setFlowOwnerAgentName(value);
-        (_b = this.orchestrator) === null || _b === void 0 ? void 0 : _b.setFlowOwner(value);
+        (_b = this.driver) === null || _b === void 0 ? void 0 : _b.setFlowOwner(value);
     }
     get liveSubAgentTrace() {
         var _a, _b;
@@ -1576,12 +1576,12 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
         this.settings.costHistorySlotted = value;
     }
     /**
-     * This element's driver as an orchestrator, or `undefined` when the session is running a bare
-     * `ChatDriver`. The only place in this element that narrows the type; the test itself lives in
-     * `asOrchestrator`, shared with the session persister.
+     * Which kind of driver this element runs, for the `driver.created` / `assistant.connected` log
+     * lines only. Looks through any decorators (GENC-1660): behaviour goes through `AiDriver`
+     * members, which every layer forwards, so this is the one place the concrete class matters.
      */
-    get orchestrator() {
-        return asOrchestrator(this.driver);
+    get driverKind() {
+        return asOrchestrator(this.driver) ? 'orchestrating' : 'chat';
     }
     /**
      * A get/set pair over one of this element's own properties, for a controller
@@ -1751,7 +1751,7 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
             this.driver.loadHistory([...history]);
         this.logMeta('driver.created', {
             reason: 'agents-changed',
-            driverKind: this.orchestrator ? 'orchestrating' : 'chat',
+            driverKind: this.driverKind,
         });
     }
     /**
@@ -1835,14 +1835,13 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
      * times — unwires any existing listeners first.
      */
     wireDriver() {
+        var _a;
         const { driver } = this;
         if (!driver)
             return;
         // Captured, not re-read: the cleanup closures below must remove their listeners
         // from the object they were added to, even if `this.driver` has been reassigned
-        // by the time `unwireDriver` runs. Same reason `driver` itself is destructured,
-        // and reading both from `this` here means they cannot disagree.
-        const orchestrator = this.orchestrator;
+        // by the time `unwireDriver` runs.
         // Idempotent — unwire previous listeners on this component before re-wiring.
         this.unwireDriver();
         const onHistoryUpdated = (e) => {
@@ -1963,72 +1962,75 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
             () => driver.removeEventListener('interaction-stop', onInteractionStop),
             () => driver.removeEventListener('provider-changed', onProviderChanged),
         ];
-        if (orchestrator) {
-            // Restore the user pin and flow-owner lock from the session store onto
-            // the freshly built driver, so pop-in/pop-out and agents-array
-            // reassignment preserve both.
-            orchestrator.setPinnedAgent(this.pinnedAgentName);
-            orchestrator.setFlowOwner(this.flowOwnerAgentName);
-            orchestrator.setContextGuard(this.contextGateCtrl.guardPolicy);
-            const onOrchStart = () => {
-                this.showHalo = 'orchestrating';
-            };
-            const onOrchStop = () => {
-                if (this.showHalo === 'orchestrating')
-                    this.showHalo = 'agent';
-            };
-            const onAgentChanged = (e) => {
-                this.activeAgent = e.detail;
-            };
-            // User-initiated pin changes flow into the driver via the
-            // `pinnedAgentName` setter, which already calls setPinnedAgent — no
-            // event-driven mirror needed in this direction. The driver does still
-            // emit `'pinned-changed'` if other code ever calls `setPinnedAgent`
-            // directly, so keep the mirror for safety; guard against the redundant
-            // round-trip caused by our own setter call.
-            const onPinnedChanged = (e) => {
-                var _a, _b;
-                const name = e.detail;
-                if (((_a = this._sessionRef) === null || _a === void 0 ? void 0 : _a.store.aiAssistant.pinnedAgentName) !== name) {
-                    (_b = this._sessionRef) === null || _b === void 0 ? void 0 : _b.actions.aiAssistant.setPinnedAgentName(name);
-                }
-            };
-            // Orchestrator-initiated flow-owner changes (auto-lock on stateful
-            // activation, auto-clear on release). Mirror to Redux so the UI freeze
-            // state and `pinLocked` survive component remount.
-            const onFlowOwnerChanged = (e) => {
-                var _a, _b, _c, _d, _e, _f, _g, _h;
-                const name = e.detail;
-                if (((_a = this._sessionRef) === null || _a === void 0 ? void 0 : _a.store.aiAssistant.flowOwnerAgentName) !== name) {
-                    (_b = this._sessionRef) === null || _b === void 0 ? void 0 : _b.actions.aiAssistant.setFlowOwnerAgentName(name);
-                }
-                // Capture the prompt that started this flow so a non-resumable tombstone can
-                // hand it back on return (GENC-1351 §5.9). On release, clear it. Slice-backed so
-                // both element instances agree.
-                if (name) {
-                    // Prefer the message currently being sent (`send()` stashes it in
-                    // `_pendingSendPrompt`) over the driver's raw history: `flow-owner-changed` fires
-                    // while routing THIS turn — BEFORE `chatDriver.sendMessage` appends the triggering
-                    // message to raw history — so a raw-history read here captures the PREVIOUS user
-                    // turn (the bug behind an interrupted flow re-priming the wrong prompt). Fall back
-                    // to raw history for a flow that locks outside a user send.
-                    const history = (_e = (_d = (_c = this.driver) === null || _c === void 0 ? void 0 : _c.getRawHistory) === null || _d === void 0 ? void 0 : _d.call(_c)) !== null && _e !== void 0 ? _e : [];
-                    const prompt = this._pendingSendPrompt || ((_f = history[lastUserMessageIndex(history)]) === null || _f === void 0 ? void 0 : _f.content);
-                    if (prompt) {
-                        (_g = this._sessionRef) === null || _g === void 0 ? void 0 : _g.actions.aiAssistant.setFlowActivationPrompt(prompt);
-                    }
-                }
-                else {
-                    (_h = this._sessionRef) === null || _h === void 0 ? void 0 : _h.actions.aiAssistant.setFlowActivationPrompt(null);
+        // Wired on the driver this element holds, whatever it is, rather than on an orchestrator found
+        // by narrowing (GENC-1660). Every layer forwards these members and events, so this works for a
+        // bare `ChatDriver` — which now raises the lifecycle events itself (GENC-1485) — and for any
+        // decorator stack, where a narrowed orchestrator would be one layer the host should not reach.
+        //
+        // Restore the user pin and flow-owner lock from the session store onto
+        // the freshly built driver, so pop-in/pop-out and agents-array
+        // reassignment preserve both.
+        driver.setPinnedAgent(this.pinnedAgentName);
+        driver.setFlowOwner(this.flowOwnerAgentName);
+        (_a = driver.setContextGuard) === null || _a === void 0 ? void 0 : _a.call(driver, this.contextGateCtrl.guardPolicy);
+        const onOrchStart = () => {
+            this.showHalo = 'orchestrating';
+        };
+        const onOrchStop = () => {
+            if (this.showHalo === 'orchestrating')
+                this.showHalo = 'agent';
+        };
+        const onAgentChanged = (e) => {
+            this.activeAgent = e.detail;
+        };
+        // User-initiated pin changes flow into the driver via the
+        // `pinnedAgentName` setter, which already calls setPinnedAgent — no
+        // event-driven mirror needed in this direction. The driver does still
+        // emit `'pinned-changed'` if other code ever calls `setPinnedAgent`
+        // directly, so keep the mirror for safety; guard against the redundant
+        // round-trip caused by our own setter call.
+        const onPinnedChanged = (e) => {
+            var _a, _b;
+            const name = e.detail;
+            if (((_a = this._sessionRef) === null || _a === void 0 ? void 0 : _a.store.aiAssistant.pinnedAgentName) !== name) {
+                (_b = this._sessionRef) === null || _b === void 0 ? void 0 : _b.actions.aiAssistant.setPinnedAgentName(name);
+            }
+        };
+        // Orchestrator-initiated flow-owner changes (auto-lock on stateful
+        // activation, auto-clear on release). Mirror to Redux so the UI freeze
+        // state and `pinLocked` survive component remount.
+        const onFlowOwnerChanged = (e) => {
+            var _a, _b, _c, _d, _e, _f, _g, _h;
+            const name = e.detail;
+            if (((_a = this._sessionRef) === null || _a === void 0 ? void 0 : _a.store.aiAssistant.flowOwnerAgentName) !== name) {
+                (_b = this._sessionRef) === null || _b === void 0 ? void 0 : _b.actions.aiAssistant.setFlowOwnerAgentName(name);
+            }
+            // Capture the prompt that started this flow so a non-resumable tombstone can
+            // hand it back on return (GENC-1351 §5.9). On release, clear it. Slice-backed so
+            // both element instances agree.
+            if (name) {
+                // Prefer the message currently being sent (`send()` stashes it in
+                // `_pendingSendPrompt`) over the driver's raw history: `flow-owner-changed` fires
+                // while routing THIS turn — BEFORE `chatDriver.sendMessage` appends the triggering
+                // message to raw history — so a raw-history read here captures the PREVIOUS user
+                // turn (the bug behind an interrupted flow re-priming the wrong prompt). Fall back
+                // to raw history for a flow that locks outside a user send.
+                const history = (_e = (_d = (_c = this.driver) === null || _c === void 0 ? void 0 : _c.getRawHistory) === null || _d === void 0 ? void 0 : _d.call(_c)) !== null && _e !== void 0 ? _e : [];
+                const prompt = this._pendingSendPrompt || ((_f = history[lastUserMessageIndex(history)]) === null || _f === void 0 ? void 0 : _f.content);
+                if (prompt) {
+                    (_g = this._sessionRef) === null || _g === void 0 ? void 0 : _g.actions.aiAssistant.setFlowActivationPrompt(prompt);
                 }
-            };
-            orchestrator.addEventListener('orchestrating-start', onOrchStart);
-            orchestrator.addEventListener('orchestrating-stop', onOrchStop);
-            orchestrator.addEventListener('agent-changed', onAgentChanged);
-            orchestrator.addEventListener('pinned-changed', onPinnedChanged);
-            orchestrator.addEventListener('flow-owner-changed', onFlowOwnerChanged);
-            cleanups.push(() => orchestrator.removeEventListener('orchestrating-start', onOrchStart), () => orchestrator.removeEventListener('orchestrating-stop', onOrchStop), () => orchestrator.removeEventListener('agent-changed', onAgentChanged), () => orchestrator.removeEventListener('pinned-changed', onPinnedChanged), () => orchestrator.removeEventListener('flow-owner-changed', onFlowOwnerChanged));
-        }
+            }
+            else {
+                (_h = this._sessionRef) === null || _h === void 0 ? void 0 : _h.actions.aiAssistant.setFlowActivationPrompt(null);
+            }
+        };
+        driver.addEventListener('orchestrating-start', onOrchStart);
+        driver.addEventListener('orchestrating-stop', onOrchStop);
+        driver.addEventListener('agent-changed', onAgentChanged);
+        driver.addEventListener('pinned-changed', onPinnedChanged);
+        driver.addEventListener('flow-owner-changed', onFlowOwnerChanged);
+        cleanups.push(() => driver.removeEventListener('orchestrating-start', onOrchStart), () => driver.removeEventListener('orchestrating-stop', onOrchStop), () => driver.removeEventListener('agent-changed', onAgentChanged), () => driver.removeEventListener('pinned-changed', onPinnedChanged), () => driver.removeEventListener('flow-owner-changed', onFlowOwnerChanged));
         this.driverCleanup = () => {
             for (const fn of cleanups)
                 fn();
@@ -2157,7 +2159,7 @@ let FoundationAiAssistant = FoundationAiAssistant_1 = class FoundationAiAssistan
             store: isNewStore ? 'created' : 'restored',
             restoredMessages: this.messages.length,
             driver: driverExisted ? 'reused' : 'created',
-            driverKind: this.orchestrator ? 'orchestrating' : 'chat',
+            driverKind: this.driverKind,
             driverBusy: (_f = (_e = this.driver) === null || _e === void 0 ? void 0 : _e.isBusy()) !== null && _f !== void 0 ? _f : false,
         });
     }

package/dist/esm/state/debug-event-log.js

@@ -76,6 +76,10 @@ export const META_EVENT_IMPORTANCE = {
     'interaction.outcome': 'normal',
     // An outcome that could not be recorded: the widget goes on showing only the answer.
     'interaction.outcome-dropped': 'high',
+    // A claimant handing a pending interaction to the person, or taking it back.
+    'interaction.held': 'normal',
+    // A claim on a `userOnly` interaction, refused. Expected when an interceptor claims broadly.
+    'interaction.claim-refused': 'low',
     'external-diagnostics.folded': 'normal',
     'session.cleared': 'normal',
     'session.switched': 'low',
@@ -222,7 +226,8 @@ export const DEBUG_LOG_README = [
     "What 'session' means for those figures: the CURRENT conversation under this session key (a host-supplied per-project id, or the element id + header title when the host supplies none) — which is not necessarily everything in `timeline`. It is re-derived from the live transcript, so it spans page loads only when the chat is being remembered, and a Clear resets it to zero. `timeline` is append-only regardless: it keeps every page load and the pre-Clear conversation, with the session.cleared event as the boundary. So on a long-lived log, read these totals as the latest conversation's and the earlier sections as history — not as a total of the whole file.",
     '`timeline` is the entire session as one array, already sorted chronologically by `timestamp` (ISO 8601). Every entry has a `kind`.',
     'Timestamps are millisecond-resolution; entries that share the same millisecond are ordered by a fixed kind rank (event, then turn, then message), which is a heuristic and may not reflect exact causal order within that millisecond — e.g. a user message and the turn it triggered, or a final assistant message and its turn.end event, can appear in either order depending on whether they landed in the same millisecond. Read the logical structure of a turn rather than over-interpreting the micro-ordering of co-timestamped entries of different kinds.',
-    "kind:'message' — the conversation. `role` is user/assistant/tool/system-event/synthetic-user; `agentName` says which agent produced it; `toolCalls`/`toolResult`/`interaction` carry tool and widget activity; `inputTokens`/`outputTokens`/`cost` are per-message LLM usage, where `inputTokens` is the WHOLE prompt for that request and `cacheReadTokens`/`cacheWriteTokens` BREAK IT DOWN rather than add to it — uncached input is `inputTokens` minus those two, and adding the cache fields to `inputTokens` counts the prompt twice. The cache fields are absent on providers that report no cache split (Gemini reports reads only, since implicit caching bills no write) and on messages persisted before they existed, so read them as 0 when missing. Each bucket bills at a different rate — cache reads a fraction of uncached input, cache writes a premium, output highest — so a large token count at a small cost means the prompt was mostly cache hits. `externalCostUsd` is any non-LLM cost a widget reported for its own external service calls (folded into the session cost total alongside `cost`). On model-produced assistant messages, `model` is the concrete model id that generated it (e.g. 'gemini-2.5-flash-lite') and `providerName` is the registry slot it resolved under (e.g. a tier name like 'high'/'low', or the default); together they attribute the message — and any tool calls it carries — to an exact model even across a mid-session vendor/tier switch, where one slot name can map to different models before and after the switch. Both are undefined on any entry that is NOT an LLM response: non-assistant roles (user/tool/system-event) and 'synthetic-user' echoes; assistant interaction/widget entries (empty content carrying an `interaction` — a rendered widget, not a model turn); driver-authored assistant fallbacks (the timeout, repeated-malformed-call, and empty-response apology messages); and messages restored from a session persisted before these fields existed. One partial case: on a genuine model turn whose provider exposes no `getStatus` (or reports no model), `providerName` is still set but `model` alone is undefined. A 'synthetic-user' message is a display-only echo of an interaction outcome (e.g. the answer a widget reported): it renders on the user's side of the chat and `agentName` is the agent that created it, but it is never sent to the LLM — so it has no matching 'turn' and the model learns the outcome only from the corresponding tool result.",
+    "kind:'message' — the conversation. `role` is user/assistant/tool/system-event/synthetic-user; `agentName` says which agent produced it; `toolCalls`/`toolResult`/`interaction` carry tool and widget activity; `inputTokens`/`outputTokens`/`cost` are per-message LLM usage, where `inputTokens` is the WHOLE prompt for that request and `cacheReadTokens`/`cacheWriteTokens` BREAK IT DOWN rather than add to it — uncached input is `inputTokens` minus those two, and adding the cache fields to `inputTokens` counts the prompt twice. The cache fields are absent on providers that report no cache split (Gemini reports reads only, since implicit caching bills no write) and on messages persisted before they existed, so read them as 0 when missing. Each bucket bills at a different rate — cache reads a fraction of uncached input, cache writes a premium, output highest — so a large token count at a small cost means the prompt was mostly cache hits. `externalCostUsd` is any non-LLM cost a widget reported for its own external service calls (folded into the session cost total alongside `cost`). On model-produced assistant messages, `model` is the concrete model id that generated it (e.g. 'gemini-2.5-flash-lite') and `providerName` is the registry slot it resolved under (e.g. a tier name like 'high'/'low', or the default); together they attribute the message — and any tool calls it carries — to an exact model even across a mid-session vendor/tier switch, where one slot name can map to different models before and after the switch. Both are undefined on any entry that is NOT an LLM response: non-assistant roles (user/tool/system-event) and 'synthetic-user' echoes; assistant interaction/widget entries (empty content carrying an `interaction` — a rendered widget, not a model turn); driver-authored assistant fallbacks (the timeout, repeated-malformed-call, and empty-response apology messages); and messages restored from a session persisted before these fields existed. One partial case: on a genuine model turn whose provider exposes no `getStatus` (or reports no model), `providerName` is still set but `model` alone is undefined. A 'synthetic-user' message is a display-only echo of an interaction outcome (e.g. the answer a widget reported): it renders on the user's side of the chat and `agentName` is the agent that created it, but it is never sent to the LLM — so it has no matching 'turn' and the model learns the outcome only from the corresponding tool result. An echo of an answer an interceptor (such as an autopilot) gave is NOT synthetic-user: see the delegated-messages paragraph.",
+    "Delegated messages (GENC-1660): a message with a `delegate` field was written or sent ON THE USER'S BEHALF by a driver decorator, and `delegate` names it (e.g. autopilot). The platform stamps it; nothing else can. It renders as the assistant whatever its role. A delegated `user` message was NOT typed by the user: it is an answer given on their behalf, and the model read it with `delegateFraming` in brackets in front of the content (the stored `content` is the bare text). A delegated `assistant` message is display-only (`excludeFromProvider`): the decorator's narration, or the echo of a widget answer it gave, which takes the place of a synthetic-user echo. To tell what the person decided from what was decided for them, read `interaction.answeredBy` and these fields, never the role alone.",
     "Sub-agent messages appear inline. When a tool delegates to a sub-agent (via `requestSubAgent`), the sub-agent's whole conversation — its own assistant/tool messages, each with their own `content`/`thinking`/`toolCalls`/`toolResult` and per-message `model`/`providerName`/`inputTokens`/`outputTokens`/`cacheReadTokens`/`cacheWriteTokens`/`cost` — is hoisted into the timeline as ordinary kind:'message' entries, interleaved by timestamp right after the tool call that spawned them (so you read the delegation top-to-bottom). A hoisted entry is marked: `subAgentDepth` is its delegation depth (1 for a sub-agent, 2 for a sub-agent's sub-agent, …), `subAgentOf` is the id of the parent tool call that spawned it (correlates it back even when two sub-agents run in one parent turn), `subAgentName` is the sub-agent's own name, and `agentName` is rewritten to a `\"<parent> › <sub-agent>\"` breadcrumb (composing when nested, e.g. `\"UI Builder › Planner › Grounding\"`). The sub-agent's per-LLM-call snapshots also surface as kind:'turn' entries with an N-M `turnIndex`, and subagent.started/completed (or subagent.failed) events bracket the run. Per-message `cost` on hoisted entries is already part of the session total (it is summed from the un-flattened history), so summing the top-level timeline does NOT double-count.",
     "kind:'turn' — one LLM call. `turnIndex` is a string: a top-level turn is the bare counter ('0', '1', …); a sub-agent's turns are numbered under the parent turn that activated them ('3-1', '3-2', …, and a nested sub-agent contributes '3-2-1', …), and `agentName` names the agent that ran the turn. `systemPrompt` and `toolNames` are what the model saw. A systemPrompt of '<repeated — identical to turn N>' was byte-identical to turn N and de-duplicated; the full prompt is shown whenever it changes (often because a stateful agent advanced), so prompt evolution is visible.",
     "kind:'turn'.`model`/`providerName`/`provider` — which model ran that call: the concrete model id, the registry slot it resolved under (a tier name like 'high'/'low', or the default), and the vendor. Recorded per CALL, so an agent whose `provider` selector varies by state — a flow that plans on a high tier and executes on a low one — has every step attributed, including calls that produced no message. `model` is the SERVING model where the provider reports one, so a turn answered by a server-side fallback names the model that answered rather than the one requested; it always matches the `model` on the message that call produced. Absent when the provider exposes no `getStatus` and the transport stamped nothing.",
@@ -230,7 +235,7 @@ export const DEBUG_LOG_README = [
     "kind:'turn'.`agentSnapshot` — the active agent's own view of its internal state, captured at that turn. An agent opts into this by exposing a `getDebugSnapshot()` that returns JSON-serializable per-state info; stateful/flow agents wire it automatically, so you can watch a flow advance turn-by-turn (e.g. current step, cursor, collected fields, pending changes). Absent for agents that don't expose one.",
     "kind:'event' — a meta/lifecycle event. `type` names it (see below); `detail` carries structured data. `detail.placement` is the emitting UI instance: 'bubble' (collapsed), 'panel' (popped-out), or 'standalone'.",
     "Each 'event' also has an `importance`: 'high' (failures/limits — turn.error, tool.failed, subagent.failed, file.read-failed, suggestions.failed, context.threshold-crossed), 'normal' (session flow — connects, turns, retries, handoffs, agent/provider changes, interactions, sub-agent start/complete), or 'low' (skippable UI/bookkeeping noise — panel.toggled, attachment.added, driver.wired/unwired, context.updated, context.condensed). To skim, ignore importance:'low'; to triage a failure, filter to importance:'high' then read the nearby messages and turns. A 'high' turn.error is often preceded by one or more 'normal' turn.retry events for the same reason — read them together to see how many attempts were made before bailing. 'message' and 'turn' entries carry no importance — they are the substance, always read them.",
-    'Event types: assistant.connected/disconnected (mount + placement + whether the session was created or restored), assistant.popout/popin (window placement), driver.created/wired/unwired (which driver is live and why it stops/starts responding across a popout), state.changed (idle↔loading), turn.start/turn.end (turn boundary; turn.end carries durationMs), turn.retry (a recoverable in-turn retry — detail.reason plus attempt/maxAttempts; for malformed calls also finishMessage; for empty responses also the provider finishReason + thoughtsTokens + parts breakdown), turn.error (a turn failed or hit a guardrail — detail.reason is one of exception/malformed-function-call/empty-response/unknown-tool-limit/max-iterations/response-truncated/refusal/budget-exhausted/provider-refused/context-exhausted/ai-service-error, plus reason-specific diagnostics: attempts (for empty-response also finishReason + thoughtsTokens + a parts breakdown, distinguishing a thinking-only STOP from a truly empty turn), finishMessage, for response-truncated the model + maxTokens + outputTokens + tools, unknownTools (split into staleTools — real earlier this activation but retired by the current state or hidden behind an open exclusive fold — and hallucinatedTools — never advertised) + availableTools, iterations + limit, for budget-exhausted the budgetUsd + spentUsd figures reported by the proxy plus the resolved vendor, for provider-refused the kind (spend|auth) plus the upstream status and error type — the vendor refusing the ACCOUNT rather than us refusing to spend, so the remedy is a top-up or a key rotation rather than a raised cap, and the kind is the only place that distinction survives because the user-facing copy is deliberately cause-free, for context-exhausted the estimated contextTokens against the guard that stopped the turn plus the iterations reached — the driver ending a runaway tool loop at the edge of the context window rather than issuing a request the provider would reject, so the transcript survives intact and can still be compacted, for ai-service-error the code (one of AI_SERVICE_ERROR_CODES, e.g. NO_API_KEY) and the status the AI service answered with — its own text goes to the browser console only, or name + message for exceptions), tool.failed (a tool threw), tool.unresolved (the model called a tool that could not be dispatched — detail.kind is folded/fold-hidden/stale/unknown, plus tool + agent and, for the counted kinds, the consecutive streak; the recurring lead-up to an unknown-tool-limit turn.error), subagent.started/completed/failed (the lifecycle of a `requestSubAgent` delegation — detail.agent names the sub-agent; these bracket the sub-agent turns that appear as kind:turn entries with an N-M `turnIndex`; subagent.failed also carries detail.reason, one of max_iterations/malformed_tool_call/empty_response/unknown_tool_limit/timeout/response_truncated/refusal/budget_exhausted/provider_refused/context_exhausted/ai_service_error; budget_exhausted and provider_refused are terminal for the PARENT turn too, and so is ai_service_error when the refusal is about the service rather than the request and came from the vendor the parent calls — the parent stops rather than calling the model again into the same wall; after context_exhausted the parent goes on, but its own next call is likely to stop on the same guard), agent.handoff (routing; from=null is the initial activation), agent.pinned/unpinned (forced routing), routing.decided (ONE PER ROUTING DECISION — see its own paragraph below), provider.selected (the resolved provider for the upcoming turns — detail.provider is the registry SLOT/tier name, detail.model the concrete model behind it and detail.vendor its vendor; emitted only when the slot CHANGES, so read the per-turn `model` for the model of any given call rather than assuming the nearest event still applies), interaction.requested/resolved (blocking user widgets — explain quiet gaps; note that when a sub-agent opens a widget, detail.agent — and the agentName on the interaction message — is the HOST agent that owns the widget, NOT the sub-agent that asked, because widgets render and resolve on the host driver), context.updated/threshold-crossed (token + cost), context.condensed (a stale tool payload was collapsed out of the model-bound history by a `condenseWhen` declaration on the tool — detail.tool + toolCallId, target args|response, trigger (superseded:<key> or age:<n>), stubLen, and an estimated tokensSaved; stored history and this log keep the FULL payload, so the model-visible slice at any point is the full history minus the condensations recorded up to then), panel.toggled, attachment.added, file.read-failed, suggestions.failed.',
+    'Event types: assistant.connected/disconnected (mount + placement + whether the session was created or restored), assistant.popout/popin (window placement), driver.created/wired/unwired (which driver is live and why it stops/starts responding across a popout), state.changed (idle↔loading), turn.start/turn.end (turn boundary; turn.end carries durationMs), turn.retry (a recoverable in-turn retry — detail.reason plus attempt/maxAttempts; for malformed calls also finishMessage; for empty responses also the provider finishReason + thoughtsTokens + parts breakdown), turn.error (a turn failed or hit a guardrail — detail.reason is one of exception/malformed-function-call/empty-response/unknown-tool-limit/max-iterations/response-truncated/refusal/budget-exhausted/provider-refused/context-exhausted/ai-service-error, plus reason-specific diagnostics: attempts (for empty-response also finishReason + thoughtsTokens + a parts breakdown, distinguishing a thinking-only STOP from a truly empty turn), finishMessage, for response-truncated the model + maxTokens + outputTokens + tools, unknownTools (split into staleTools — real earlier this activation but retired by the current state or hidden behind an open exclusive fold — and hallucinatedTools — never advertised) + availableTools, iterations + limit, for budget-exhausted the budgetUsd + spentUsd figures reported by the proxy plus the resolved vendor, for provider-refused the kind (spend|auth) plus the upstream status and error type — the vendor refusing the ACCOUNT rather than us refusing to spend, so the remedy is a top-up or a key rotation rather than a raised cap, and the kind is the only place that distinction survives because the user-facing copy is deliberately cause-free, for context-exhausted the estimated contextTokens against the guard that stopped the turn plus the iterations reached — the driver ending a runaway tool loop at the edge of the context window rather than issuing a request the provider would reject, so the transcript survives intact and can still be compacted, for ai-service-error the code (one of AI_SERVICE_ERROR_CODES, e.g. NO_API_KEY) and the status the AI service answered with — its own text goes to the browser console only, or name + message for exceptions), tool.failed (a tool threw), tool.unresolved (the model called a tool that could not be dispatched — detail.kind is folded/fold-hidden/stale/unknown, plus tool + agent and, for the counted kinds, the consecutive streak; the recurring lead-up to an unknown-tool-limit turn.error), subagent.started/completed/failed (the lifecycle of a `requestSubAgent` delegation — detail.agent names the sub-agent; these bracket the sub-agent turns that appear as kind:turn entries with an N-M `turnIndex`; subagent.failed also carries detail.reason, one of max_iterations/malformed_tool_call/empty_response/unknown_tool_limit/timeout/response_truncated/refusal/budget_exhausted/provider_refused/context_exhausted/ai_service_error; budget_exhausted and provider_refused are terminal for the PARENT turn too, and so is ai_service_error when the refusal is about the service rather than the request and came from the vendor the parent calls — the parent stops rather than calling the model again into the same wall; after context_exhausted the parent goes on, but its own next call is likely to stop on the same guard), agent.handoff (routing; from=null is the initial activation), agent.pinned/unpinned (forced routing), routing.decided (ONE PER ROUTING DECISION — see its own paragraph below), provider.selected (the resolved provider for the upcoming turns — detail.provider is the registry SLOT/tier name, detail.model the concrete model behind it and detail.vendor its vendor; emitted only when the slot CHANGES, so read the per-turn `model` for the model of any given call rather than assuming the nearest event still applies), interaction.requested/resolved (blocking user widgets — explain quiet gaps; note that when a sub-agent opens a widget, detail.agent — and the agentName on the interaction message — is the HOST agent that owns the widget, NOT the sub-agent that asked, because widgets render and resolve on the host driver; detail.ownerPath names the agents that actually asked, outermost first, the last being the one whose tool requested it, and detail.heldBy says who held it when it opened: user, or the id of the interceptor that claimed it, such as autopilot; on interaction.resolved, detail.answeredBy is who answered — the claimant id when it settled through its own hold, user for any other answer (a click counts as the person even on a widget a claimant held) — absent when it closed unanswered (a timeout or a stop); the same value is stamped on the interaction message as answeredBy, and when it is not user the tool result that interaction returned carries a decidedOnUsersBehalf record, so the model was told the choice was not made by the person), interaction.held (a claimant moved a pending interaction to the person or back to itself — detail.heldBy is the new holder, detail.claimant the interceptor; a widget held by anything but user was not answered by the person), interaction.claim-refused (a claim on a userOnly interaction, which stays with the person — detail.claimant + reason), context.updated/threshold-crossed (token + cost), context.condensed (a stale tool payload was collapsed out of the model-bound history by a `condenseWhen` declaration on the tool — detail.tool + toolCallId, target args|response, trigger (superseded:<key> or age:<n>), stubLen, and an estimated tokensSaved; stored history and this log keep the FULL payload, so the model-visible slice at any point is the full history minus the condensations recorded up to then), panel.toggled, attachment.added, file.read-failed, suggestions.failed.',
     'Sub-agent meta events: a sub-agent\'s own turn.retry/turn.error/tool.failed/tool.unresolved events are merged into this same timeline, tagged with `detail.subAgent` — a `"<parent> › <sub-agent>"` breadcrumb that composes when nested (e.g. `"UI Builder › Planner › Grounding"`) — and interleaved by their original timestamps within the subagent.started→completed/failed bracket. These are the per-attempt/per-failure signals that do NOT appear among the sub-agent\'s (hoisted) messages: a malformed/empty attempt that gets retried produces no message, and the stale-vs-hallucinated split and streak counts live only on the event. A sub-agent\'s high-volume, message-derivable events (turn.start/turn.end, provider.selected, context.updated) are intentionally NOT merged — read its hoisted messages for model/tokens/cost and turn-by-turn activity, and the bracketing subagent.* events for the run\'s span.',
     "`meta` holds context captured at export time: agentSummary (full agent configs), context (active model, contextTokens/contextLimit/contextUsagePercent for the last call, and the session totals — sessionCostUsd, sessionTokensConsumed, and the four-bucket sessionUsage lifted to the top of this log), activeDebugSnapshot (the active agent's `getDebugSnapshot()` taken fresh at export — reflects state NOW, which may have advanced beyond the last turn's agentSnapshot), debug (optional host-supplied debug state), host, and the export timestamp.",
     'Note the two different scopes in `meta.context`: `contextTokens` is the prompt size of the LAST call (against `contextLimit`, the model context window), while `sessionUsage`/`sessionTokensConsumed` are cumulative BILLED throughput. Every turn resends the conversation, so the cumulative figure counts each turn’s prompt again in the next turn’s and is expected to dwarf the context size — that is not double-counting.',

package/dist/esm/state/interaction-context.js

@@ -12,8 +12,12 @@ export function createInteractionContext(interactionId) {
     const listeners = new Set();
     const disposers = new Set();
     let disposed = false;
+    let heldBy = 'user';
     const context = {
         interactionId,
+        get heldBy() {
+            return heldBy;
+        },
         state,
         once(key, factory) {
             if (onceCache.has(key))
@@ -78,5 +82,12 @@ export function createInteractionContext(interactionId) {
             // themselves are closed via their `onDispose`, but drop the references too.
             onceCache.clear();
         },
+        setHeldBy(holder) {
+            if (disposed || holder === heldBy)
+                return false;
+            heldBy = holder;
+            context.notify();
+            return true;
+        },
     };
 }

package/dist/esm/state/persistence/session-persister.js

@@ -1,5 +1,4 @@
 import { __awaiter } from "tslib";
-import { asOrchestrator } from '../../components/orchestrating-driver/orchestrating-driver';
 import { flattenSubAgentMessages } from '../../utils/flatten-sub-agent-messages';
 import { logger } from '../../utils/logger';
 import { isSessionNoticeMarker, SESSION_RESTORE_FAILED_LABEL, SESSION_RESTORED_LABEL, SESSION_RESUMED_LABEL, } from '../../utils/message-partition';
@@ -699,11 +698,11 @@ export class SessionPersister {
                 // (flow-owned but unpinned) — `resolvePinnedAgent` reads `flowOwnerAgentName ??
                 // pinnedAgentName`, so restoring both resumes the flow without re-classifying, and the
                 // driver's routing agrees with the restored (picker-locked) store state.
-                const orchestrator = asOrchestrator(driver);
-                if (orchestrator) {
-                    orchestrator.setPinnedAgent((_g = snapshot.pinnedAgentName) !== null && _g !== void 0 ? _g : null);
-                    orchestrator.setFlowOwner((_h = snapshot.flowOwnerAgentName) !== null && _h !== void 0 ? _h : null);
-                }
+                //
+                // On the driver itself, not a narrowed orchestrator (GENC-1660): both members are on
+                // `AiDriver` and every decorator forwards them, so this reaches the routing whatever wraps it.
+                driver === null || driver === void 0 ? void 0 : driver.setPinnedAgent((_g = snapshot.pinnedAgentName) !== null && _g !== void 0 ? _g : null);
+                driver === null || driver === void 0 ? void 0 : driver.setFlowOwner((_h = snapshot.flowOwnerAgentName) !== null && _h !== void 0 ? _h : null);
                 if (flowOwner) {
                     this.logMeta('persistence.resume-planned', {
                         flowOwner,

package/dist/esm/suggestions/generate-suggestions.js

@@ -1,5 +1,6 @@
 import { __awaiter } from "tslib";
 import { reachesProvider } from '../utils/context-tokens';
+import { frameDelegatedContent } from '../utils/delegated-message';
 import { logger } from '../utils/logger';
 /** Turns of transcript given to the model when suggesting follow-ups. */
 const HISTORY_WINDOW = 8;
@@ -75,7 +76,13 @@ export function buildSuggestionsPrompt(ctx, history, prompt, count, allAgentInfo
             !!((_b = m.content) === null || _b === void 0 ? void 0 : _b.trim());
     })
         .slice(-HISTORY_WINDOW)
-        .map((m) => `${m.role === 'user' ? 'User' : 'Assistant'}: ${m.content}`)
+        // A delegated user message is read framed, as every other model call reads it (GENC-1660).
+        .map((m) => {
+        var _a;
+        return m.role === 'user'
+            ? `User: ${m.delegate ? frameDelegatedContent((_a = m.content) !== null && _a !== void 0 ? _a : '', m.delegateFraming) : m.content}`
+            : `Assistant: ${m.content}`;
+    })
         .join('\n');
     return (`<conversation_history>\n${conversationContext}\n</conversation_history>\n\n` +
         `The conversation above has ended. Do not continue it or respond as the assistant. ` +

package/dist/esm/types/handler-capability.js

@@ -0,0 +1 @@
+export {};

package/dist/esm/types/interaction-interceptor.js

@@ -0,0 +1 @@
+export {};

package/dist/esm/utils/delegated-message.js

@@ -0,0 +1,25 @@
+/**
+ * Whether `message` was written or sent on the user's behalf. A delegated message renders as the
+ * assistant, whatever its role.
+ *
+ * @beta
+ */
+export const isDelegated = (message) => !!message.delegate;
+/**
+ * How a delegated `user` message is framed for the model when its sender gives no phrase. Names no
+ * decorator, so the model has none to repeat.
+ *
+ * @beta
+ */
+export const DEFAULT_DELEGATE_FRAMING = "Sent on the user's behalf.";
+/**
+ * A delegated `user` message's content as the model reads it: its framing in brackets, then the
+ * text. The one place this string is built, so the first model call (which takes the message as
+ * its input) and every later call (which reads it from history) send the same bytes and the cache
+ * prefix holds.
+ *
+ * @internal
+ */
+export function frameDelegatedContent(content, framing) {
+    return `(${framing !== null && framing !== void 0 ? framing : DEFAULT_DELEGATE_FRAMING})\n\n${content}`;
+}

package/dist/esm/utils/history-transform.js

@@ -1,5 +1,6 @@
 import { __rest } from "tslib";
 import { COMPACTION_SUMMARY_TOKEN_ESTIMATE, estimateMessageTokens, projectCompaction, reachesProvider, } from './context-tokens';
+import { frameDelegatedContent } from './delegated-message';
 /**
  * Masks the tool-specific payload of a single message — clears tool call args
  * and replaces tool result content with a placeholder. Used when passing history
@@ -204,7 +205,11 @@ function renderMessageForSummary(m) {
         case 'compacted-summary':
             return `[Earlier summary] ${m.content}`;
         case 'user':
-            return m.content ? `User: ${m.content}` : '';
+            // A delegated message keeps its framing here too, or the summary would put words in the
+            // user's mouth that outlive the message itself (GENC-1660).
+            if (!m.content)
+                return '';
+            return `User: ${m.delegate ? frameDelegatedContent(m.content, m.delegateFraming) : m.content}`;
         case 'assistant': {
             // Reasoning ("Thinking") and narration ("Working") are display-only assistant splits
             // (GENC-1410) with no tool calls of their own — fold them into the summary too, labelled
@@ -265,6 +270,12 @@ export function buildCompactionSummaryPrompt(toCompact) {
  */
 export function normalizeForProvider(history) {
     return history.map((m) => {
+        var _a;
+        // A user message sent on the user's behalf (GENC-1660) is framed, so the model never reads
+        // it as something the person typed.
+        if (m.role === 'user' && m.delegate) {
+            return Object.assign(Object.assign({}, m), { content: frameDelegatedContent((_a = m.content) !== null && _a !== void 0 ? _a : '', m.delegateFraming) });
+        }
         if (m.role !== 'compacted-summary')
             return m;
         return Object.assign(Object.assign({}, m), { role: 'user', content: `<conversation_summary>\n${m.content}\n</conversation_summary>\n\n` +

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@genesislcap/ai-assistant",
   "description": "Genesis AI Assistant micro-frontend",
-  "version": "15.58.1",
+  "version": "15.59.0",
   "license": "SEE LICENSE IN license.txt",
   "main": "dist/esm/index.js",
   "types": "dist/ai-assistant.d.ts",
@@ -92,31 +92,31 @@
     }
   },
   "devDependencies": {
-    "@genesislcap/foundation-comms": "15.58.1",
-    "@genesislcap/foundation-testing": "15.58.1",
-    "@genesislcap/genx": "15.58.1",
-    "@genesislcap/ts-builder": "15.58.1",
-    "@genesislcap/uvu-playwright-builder": "15.58.1",
-    "@genesislcap/vite-builder": "15.58.1",
-    "@genesislcap/webpack-builder": "15.58.1",
+    "@genesislcap/foundation-comms": "15.59.0",
+    "@genesislcap/foundation-testing": "15.59.0",
+    "@genesislcap/genx": "15.59.0",
+    "@genesislcap/ts-builder": "15.59.0",
+    "@genesislcap/uvu-playwright-builder": "15.59.0",
+    "@genesislcap/vite-builder": "15.59.0",
+    "@genesislcap/webpack-builder": "15.59.0",
     "@types/dompurify": "^3.0.5",
     "@types/marked": "^5.0.2",
     "esbuild": "0.25.12"
   },
   "dependencies": {
-    "@genesislcap/foundation-ai": "15.58.1",
-    "@genesislcap/foundation-logger": "15.58.1",
-    "@genesislcap/foundation-notifications": "15.58.1",
-    "@genesislcap/foundation-redux": "15.58.1",
-    "@genesislcap/foundation-ui": "15.58.1",
-    "@genesislcap/foundation-utils": "15.58.1",
-    "@genesislcap/rapid-design-system": "15.58.1",
-    "@genesislcap/web-core": "15.58.1",
+    "@genesislcap/foundation-ai": "15.59.0",
+    "@genesislcap/foundation-logger": "15.59.0",
+    "@genesislcap/foundation-notifications": "15.59.0",
+    "@genesislcap/foundation-redux": "15.59.0",
+    "@genesislcap/foundation-ui": "15.59.0",
+    "@genesislcap/foundation-utils": "15.59.0",
+    "@genesislcap/rapid-design-system": "15.59.0",
+    "@genesislcap/web-core": "15.59.0",
     "dompurify": "^3.3.1",
     "marked": "^17.0.3"
   },
   "peerDependencies": {
-    "@genesislcap/foundation-comms": "^15.58.1"
+    "@genesislcap/foundation-comms": "^15.59.0"
   },
   "peerDependenciesMeta": {
     "@genesislcap/foundation-comms": {