@genesislcap/ai-assistant 15.19.0 → 15.19.1

package/dist/tsconfig.tsbuildinfo

@@ -1 +0,0 @@
-{"root":["../src/chat-driver-node.ts","../src/index.ts","../src/channel/ai-activity-bus.ts","../src/channel/ai-activity-channel.ts","../src/components/flowing-waves-indicator.ts","../src/components/halo-overlay.ts","../src/components/plasma-orb-indicator.ts","../src/components/waves-indicator.ts","../src/components/activity-halo/activity-halo.ts","../src/components/agent-picker/agent-picker.constants.ts","../src/components/agent-picker/agent-picker.styles.ts","../src/components/agent-picker/agent-picker.template.ts","../src/components/agent-picker/agent-picker.ts","../src/components/agent-picker/index.ts","../src/components/ai-driver/ai-driver.ts","../src/components/ai-driver/index.ts","../src/components/chat-bubble/chat-bubble.styles.ts","../src/components/chat-bubble/chat-bubble.template.ts","../src/components/chat-bubble/chat-bubble.ts","../src/components/chat-bubble/index.ts","../src/components/chat-driver/align-event-globals.ts","../src/components/chat-driver/chat-driver.compact.test.ts","../src/components/chat-driver/chat-driver.invocation-scope.test.ts","../src/components/chat-driver/chat-driver.test.ts","../src/components/chat-driver/chat-driver.thinking-policy.test.ts","../src/components/chat-driver/chat-driver.trace-capture.test.ts","../src/components/chat-driver/chat-driver.ts","../src/components/chat-driver/chat-driver.turn-usage.test.ts","../src/components/chat-driver/index.ts","../src/components/chat-interaction-wrapper/chat-interaction-wrapper.styles.ts","../src/components/chat-interaction-wrapper/chat-interaction-wrapper.template.ts","../src/components/chat-interaction-wrapper/chat-interaction-wrapper.test.ts","../src/components/chat-interaction-wrapper/chat-interaction-wrapper.ts","../src/components/chat-interaction-wrapper/index.ts","../src/components/chat-markdown/chat-markdown.ts","../src/components/chat-markdown/index.ts","../src/components/orchestrating-driver/index.ts","../src/components/orchestrating-driver/orchestrating-driver.budget.test.ts","../src/components/orchestrating-driver/orchestrating-driver.cost.test.ts","../src/components/orchestrating-driver/orchestrating-driver.pin.test.ts","../src/components/orchestrating-driver/orchestrating-driver.ts","../src/components/popout-manager/index.ts","../src/components/popout-manager/popout-manager.ts","../src/components/settings-modal/index.ts","../src/components/settings-modal/settings-modal.styles.test.ts","../src/components/settings-modal/settings-modal.styles.ts","../src/components/settings-modal/settings-modal.template.test.ts","../src/components/settings-modal/settings-modal.template.ts","../src/config/config.ts","../src/config/define-stateful-agent.test.ts","../src/config/define-stateful-agent.ts","../src/config/fallback-agents.ts","../src/config/index.ts","../src/config/validate-providers.test.ts","../src/config/validate-providers.ts","../src/main/blocked-state.test.ts","../src/main/budget-meter.test.ts","../src/main/cost-session-banking.test.ts","../src/main/file-attachments.test.ts","../src/main/index.ts","../src/main/interaction-cost.test.ts","../src/main/main.styles.test.ts","../src/main/main.styles.ts","../src/main/main.template.ts","../src/main/main.ts","../src/main/main.types.ts","../src/main/persistence-broken-sources.test.ts","../src/main/popout-interaction-gate.test.ts","../src/provider/ai-provider-switcher.ts","../src/provider/assistant-app-settings.ts","../src/state/ai-assistant-slice.test.ts","../src/state/ai-assistant-slice.ts","../src/state/debug-event-log.test.ts","../src/state/debug-event-log.ts","../src/state/driver-registry.test.ts","../src/state/driver-registry.ts","../src/state/interaction-context.test.ts","../src/state/interaction-context.ts","../src/state/session-store.ts","../src/state/persistence/build-timeline-entries.ts","../src/state/persistence/diagnostics-cursors.test.ts","../src/state/persistence/diagnostics-cursors.ts","../src/state/persistence/diagnostics.test.ts","../src/state/persistence/diagnostics.ts","../src/state/persistence/index.ts","../src/state/persistence/persister-registry.ts","../src/state/persistence/session-persistence-provider.test.ts","../src/state/persistence/session-persistence-provider.ts","../src/state/persistence/session-persistence.integration.test.ts","../src/state/persistence/session-persister.test.ts","../src/state/persistence/session-persister.ts","../src/state/persistence/session-snapshot.test.ts","../src/state/persistence/session-snapshot.ts","../src/state/persistence/stateful-restore.e2e.test.ts","../src/styles/ai-colours.ts","../src/styles/menu.ts","../src/styles/settings-section.ts","../src/suggestions/chat-suggestions.ts","../src/tags/index.ts","../src/types/ai-chat-widget.ts","../src/types/interaction-context.ts","../src/utils/animated-panel-toggle.ts","../src/utils/animation-exclusivity.test.ts","../src/utils/animation-exclusivity.ts","../src/utils/banked-usage-baselines.ts","../src/utils/collect-session-models.test.ts","../src/utils/collect-session-models.ts","../src/utils/condense-history.test.ts","../src/utils/condense-history.ts","../src/utils/cost-session-history.test.ts","../src/utils/cost-session-history.ts","../src/utils/derive-cost-session-title.test.ts","../src/utils/derive-cost-session-title.ts","../src/utils/flatten-sub-agent-messages.test.ts","../src/utils/flatten-sub-agent-messages.ts","../src/utils/format-usd.ts","../src/utils/history-transform.test.ts","../src/utils/history-transform.ts","../src/utils/index.ts","../src/utils/logger.ts","../src/utils/message-partition.test.ts","../src/utils/message-partition.ts","../src/utils/resolve-cost-history-config.test.ts","../src/utils/resolve-cost-history-config.ts","../src/utils/resolve-preference-baseline.test.ts","../src/utils/resolve-preference-baseline.ts","../src/utils/strip-agent-handlers.test.ts","../src/utils/strip-agent-handlers.ts","../src/utils/sum-costs.test.ts","../src/utils/sum-costs.ts","../src/utils/sum-tokens.test.ts","../src/utils/sum-tokens.ts","../src/utils/sum-usage.test.ts","../src/utils/sum-usage.ts","../src/utils/tool-fold.ts","../src/utils/usage-rows.test.ts","../src/utils/usage-rows.ts","../src/utils/with-timeout.ts"],"version":"5.9.2"}

package/license.txt

@@ -1,46 +0,0 @@
-Developer License Agreement
-
-This Developer License Agreement (the “Agreement”) is entered into by and between Genesis, Global FinTech Inc.(“Genesis”) and you and/or the entity on whose behalf you are downloading the Software (as defined below) (“you”). This Agreement forms a legally binding contract between you and Genesis in relation to your use of the software libraries, reference implementations, and other related demonstration code (collectively, the “Genesis Software”). [a]
-
-To use the Software, you must first agree to this Agreement. You may not use the Software if you do not agree to be bound by the terms of this Agreement. Accordingly, you and Genesis acknowledge and agree as follows:
-
-1. LIMITED LICENSE.
-Subject to your complete and ongoing compliance with all the terms and conditions set forth in this Agreement, including without limitation all license limitations and restrictions set forth herein, Genesis grants you the following limited, non-exclusive, non-transferable, non-sublicensable, revocable licenses to use, and (where applicable) authorize your employees to use, the Software internally solely in connection with building, developing and testing your own applications that interoperate with or incorporate the Software (“Applications”) for the purposes of evaluation.
-
-2. RESTRICTIONS.
-A. By accessing or using the Software, you represent, warrant, and covenant that (a) you are a person or business entity engaged in the development of software applications, and (b) in the case of a business entity, you have the full power and authority to bind such entity to the terms of this Agreement.
-B. You acknowledge that the foregoing license does not include any right to:
-(i) redistribute, sell, lease, license, modify or otherwise create any derivative works of any portion of the Software, or;
-(ii) distribute, deploy, or otherwise utilize Applications on a public, production, commercial, or other similar purpose other than internal use for evaluation and the development of non-public, experimental Applications (any other public, production, commercial, or similar use requires a separate agreement with Genesis), or
-(iii) use or implement any undocumented feature or API or use any documented feature or API other than in accordance with applicable documentation. You agree to not to do any of the foregoing.
-C. Except as expressly provided herein, you may not:
-(a) reproduce, distribute, publicly display, or publicly perform any part of the Software;
-(b) decompile, reverse engineer, or otherwise access or attempt to access the source code for the Software not made available to you in source code form;
-(c) make or attempt to make any modification to, or otherwise create derivative works of the Software; or
-(d) remove, obscure, interfere with or circumvent any feature of the Software, including without limitation any copyright or other intellectual property notices, security, or access control mechanism;
-(f) use the Software to do anything illegal, including facilitating, promoting, or otherwise encouraging any illegal activities.
-
-3. RESERVATION OF RIGHTS.
-A. The Software is owned by Genesis and licensed, not sold, to you. The Software, content, visual interfaces, interactive features, information, graphics, design, compilation, computer code, products, services, and all other elements of the Software and related documentation (the “Materials“), are protected by copyright, trade dress, patent, and trademark laws of the United States and other jurisdictions, international conventions, and all other relevant intellectual property and proprietary rights, and applicable laws (collectively, the “Intellectual Property Rights“).
-B. You agree that Genesis or its subsidiaries or affiliated companies and/or its third-party licensors own all legal right, title and interest in and to the Software and Materials, including any and all Intellectual Property Rights. Genesis reserves all rights not expressly granted in this Agreement. You do not acquire any right, interest or title to the Materials, whether by implication, estoppel, or otherwise, except for the limited rights set forth in this Agreement.
-C. You agree that the form and nature of the Software that Genesis provides may change without prior notice to you and that future versions of the Software may be incompatible with applications developed on previous of the Software. You agree that Genesis may stop (permanently or temporarily) providing the Software (or any features within the Software) to you or to users generally at Genesis’s sole discretion, without prior notice to you. Nothing in this Agreement gives you a right to use any of Genesis’s trade names, trademarks, service marks, logos, domain names, or other distinctive brand features.
-
-4. TERMINATION.
-At Genesis’s sole discretion, Genesis may terminate your Developer License and cease provision of the Genesis Software with or without notice, effective immediately, for any reason or no reason at all. Upon the expiration or termination of this Agreement all rights and licenses granted under this Agreement will immediately terminate.
-
-5. THIRD PARTY SOFTWARE.
-The Software consists of a package of components and may include references to certain third-party software (“Third Party Software”) that are provided by their authors under separate license terms (the “Third Party Terms”). Your use of any such Third-Party Software in conjunction with the Software in a manner consistent with this Agreement is permitted, however, you may have broader rights and/or restrictions under the applicable Third-Party Terms. Genesis cannot accept any responsibility for the Third-Party Software or your use thereof.
-
-6. DISCLAIMER OF WARRANTIES.
-YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SOFTWARE IS AT YOUR SOLE RISK AND THAT THE SOFTWARE IS PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTY OF ANY KIND FROM GENESIS. YOUR USE OF THE SOFTWARE AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SOFTWARE IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. GENESIS FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. GENESIS EXPRESSLY DISCLAIMS ANY WARRANTIES OF ANY KIND WITH RESPECT TO THE ACCURACY OR FUNCTIONALITY OF THE SOFTWARE, AND WITH RESPECT TO THE ACCURACY, VALIDITY, OR COMPLETENESS OF ANY INFORMATION OR FEATURES AVAILABLE THROUGH THE SOFTWARE, OR THE QUALITY OR CONSISTENCY OF THE SOFTWARE OR RESULTS OBTAINED THROUGH ITS USE.
-
-7. INDEMNIFICATION. To the maximum extent permitted by law, you agree to defend, indemnify, and hold harmless Genesis, its affiliates, and their respective directors, officers, employees, and agents, from and against any and all third-party claims, actions, suits, or proceedings, as well as any and all losses, liabilities, damages, costs, and expenses (including reasonable attorneys’ fees) arising out of or accruing from (a) your breach of this Developer License; (b) your use or misuse of the Genesis Software; (c) your negligence or willful misconduct; and/or (d) your use of the Genesis Software that actually or allegedly infringes any Intellectual Property Rights or privacy rights of any third party in any jurisdiction.
-
-8. MISCELLANEOUS.
-(a) If you are agreeing to be bound by this Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to this Agreement. If you do not have the requisite authority, you may not accept this Agreement on behalf of your employer or other entity.
-(b) This Developer License shall be governed by, and construed in accordance with, the laws of the State of New York without regard to conflict of law principles. For all purposes of this Developer License, the parties’ consent to exclusive jurisdiction and venue in the state and federal courts located in New York County, New York.
-(c) Nothing in this Agreement, or in the nature of your access and use of the Genesis Software, shall create or is intended to create a joint-venture, partnership, or agency relationship between you and Genesis.
-(d) You may not assign or transfer this Agreement or any of your rights or obligations hereunder, absent the prior written consent of Genesis.
-(e) You agree that if Genesis does not exercise or enforce any legal right or remedy contained in this Agreement, this will not be taken to be a formal waiver of Genesis’s rights and that those rights or remedies will still be available to Genesis.
-(f) This Agreement constitutes the complete understanding between you and Genesis with respect to the subject matter contained herein, and supersedes all prior written or oral communications, understandings, and agreements.
-(g) If any provision of this Agreement is deemed to be illegal, invalid, or unenforceable, then that provision shall be removed, and the remaining terms will continue to be valid and enforceable.

package/sandbox/tsconfig.json

@@ -1,8 +0,0 @@
-{
-  "extends": "../../../../../tsconfig.json",
-  "compilerOptions": {
-    "noEmit": true,
-    "types": ["vite/client"]
-  },
-  "include": ["**/*.ts", "**/*.mts"]
-}

package/src/channel/ai-activity-bus.ts

@@ -1,209 +0,0 @@
-import type { AgenticActivityEvents } from './ai-activity-channel';
-
-/**
- * Configuration for {@link AgenticActivityBus}.
- *
- * @beta
- */
-export interface AgenticActivityBusConfig {
-  /** Events that should also be forwarded via BroadcastChannel to other tabs. */
-  crossTabEvents?: (keyof AgenticActivityEvents)[];
-  /** BroadcastChannel name. Only used when crossTabEvents is non-empty. */
-  channelName?: string;
-  /**
-   * Lazy alternative to {@link AgenticActivityBusConfig.channelName}: called the first
-   * time a cross-tab channel is actually needed, in a browser only. Deferring the name
-   * computation keeps side effects (e.g. `sessionStorage` reads) out of module-eval and
-   * off the non-browser path. Ignored if `channelName` is also set.
-   */
-  channelNameFactory?: () => string;
-}
-
-type AnyHandler = (detail: any) => void;
-
-/**
- * Minimal activity-bus surface the drivers depend on. `ChatDriver`/`OrchestratingDriver`
- * only ever *publish* — accepting this narrow interface (rather than importing the module
- * singleton) lets a headless/server or unit-test host omit the bus entirely, so no live
- * `BroadcastChannel` is ever opened on that path. See {@link NOOP_ACTIVITY_BUS}.
- *
- * @beta
- */
-export interface ActivityBus {
-  publish<K extends keyof AgenticActivityEvents>(type: K, detail: AgenticActivityEvents[K]): void;
-}
-
-/**
- * No-op {@link ActivityBus}. The default when no bus is injected (Node, tests, headless
- * server use) — publishing goes nowhere and nothing is left open to tear down.
- *
- * @beta
- */
-export const NOOP_ACTIVITY_BUS: ActivityBus = { publish: () => {} };
-
-/**
- * Typed in-process event bus for AI assistant activity events.
- *
- * Dispatches events synchronously to all local subscribers in the same JS module instance
- * (i.e. the same browser tab). Events listed in `crossTabEvents` are additionally forwarded
- * via a shared `BroadcastChannel` so that other tabs on the same origin receive them.
- *
- * @remarks
- * The pre-instantiated {@link agenticActivityBus} singleton covers all platform use cases.
- * App developers can extend the event map using TypeScript declaration merging on
- * {@link AgenticActivityEvents} and subscribe/publish custom events without any platform changes.
- *
- * @beta
- */
-export class AgenticActivityBus {
-  private readonly subscribers = new Map<string, Set<AnyHandler>>();
-  private readonly crossTabEvents: Set<string>;
-  private readonly channelNameFactory?: () => string;
-  private channel?: BroadcastChannel;
-  private channelInitialised = false;
-
-  /**
-   * @param config - Optional configuration. Omit to create an in-memory-only bus.
-   * @beta
-   */
-  constructor(config?: AgenticActivityBusConfig) {
-    this.crossTabEvents = new Set(config?.crossTabEvents ?? []);
-    this.channelNameFactory =
-      config?.channelName != null ? () => config.channelName! : config?.channelNameFactory;
-  }
-
-  /**
-   * Lazily open the cross-tab `BroadcastChannel` on first use. Deferred (rather than
-   * created in the constructor) so that importing this module, or constructing the bus
-   * off-browser (Node, tests, headless server), never opens a live channel or reads
-   * `sessionStorage` — both would keep a Node event loop alive and hang the process.
-   * Cross-tab forwarding is inherently browser-only, so channel creation is gated on a
-   * browser environment; elsewhere the bus stays purely in-process.
-   */
-  private ensureChannel(): void {
-    if (this.channelInitialised) return;
-    this.channelInitialised = true;
-    const inBrowser = typeof window !== 'undefined' && typeof BroadcastChannel !== 'undefined';
-    if (this.crossTabEvents.size === 0 || !this.channelNameFactory || !inBrowser) return;
-    this.channel = new BroadcastChannel(this.channelNameFactory());
-    this.channel.onmessage = (ev) => {
-      const { type, detail } = (ev.data ?? {}) as { type?: string; detail?: unknown };
-      if (type) this.notifyLocal(type, detail);
-    };
-  }
-
-  /**
-   * Subscribe to an event. Returns an unsubscribe function — call it in
-   * `disconnectedCallback` to avoid memory leaks.
-   *
-   * @beta
-   */
-  subscribe<K extends keyof AgenticActivityEvents>(
-    type: K,
-    handler: (detail: AgenticActivityEvents[K]) => void,
-  ): () => void {
-    // Open the cross-tab channel (browser only) so this subscriber receives events
-    // forwarded from other tabs; no-op off-browser.
-    this.ensureChannel();
-    let handlers = this.subscribers.get(type as string);
-    if (!handlers) {
-      handlers = new Set();
-      this.subscribers.set(type as string, handlers);
-    }
-    const h = handler as AnyHandler;
-    handlers.add(h);
-    return () => handlers!.delete(h);
-  }
-
-  /**
-   * Publish an event to all local subscribers and, if configured, to other tabs
-   * via BroadcastChannel.
-   *
-   * @beta
-   */
-  publish<K extends keyof AgenticActivityEvents>(type: K, detail: AgenticActivityEvents[K]): void {
-    this.notifyLocal(type as string, detail);
-    if (this.crossTabEvents.has(type as string)) {
-      this.ensureChannel();
-      this.channel?.postMessage({ type, detail });
-    }
-  }
-
-  /**
-   * Add an event type to the cross-tab forwarding set at runtime.
-   * Must be called before the first {@link AgenticActivityBus.publish} of that event type.
-   *
-   * @beta
-   */
-  addCrossTabEvent(type: keyof AgenticActivityEvents): void {
-    this.crossTabEvents.add(type as string);
-  }
-
-  /**
-   * Close the underlying BroadcastChannel. Call once on application teardown if needed.
-   *
-   * @beta
-   */
-  close(): void {
-    this.channel?.close();
-    this.channel = undefined;
-  }
-
-  private notifyLocal(type: string, detail: unknown): void {
-    this.subscribers.get(type)?.forEach((handler) => handler(detail));
-  }
-}
-
-/**
- * Returns a `BroadcastChannel` name that is scoped to the current tab and any popout windows
- * it opens, while remaining isolated from unrelated tabs on the same origin.
- *
- * **How it works:**
- * A UUID is generated once and stored in `sessionStorage`. `sessionStorage` persists across
- * page refreshes (so the channel name stays stable after an F5), but is cleared when the tab
- * is closed. Crucially, when a page opens a child window via `window.open()`, the browser
- * initialises the new window's `sessionStorage` as a copy of the opener's — so the child
- * inherits the same UUID and therefore the same channel name.
- *
- * Result:
- * - **Same tab + its `window.open()` popouts** share one channel → events flow as intended.
- * - **Independent tabs** (opened from the address bar, bookmarks, or links) each get a fresh
- *   `sessionStorage` and therefore a distinct channel → no cross-talk between unrelated app
- *   instances on the same origin.
- */
-function getTabScopedChannelName(base: string): string {
-  // Belt-and-braces: this only runs in a browser (see `ensureChannel`), but guard anyway
-  // so a direct call off-browser never throws a `sessionStorage is not defined` ReferenceError.
-  if (typeof sessionStorage === 'undefined') return `${base}-nostorage`;
-  const key = `${base}-tab-id`;
-  let id = sessionStorage.getItem(key);
-  if (!id) {
-    id = crypto.randomUUID();
-    sessionStorage.setItem(key, id);
-  }
-  return `${base}-${id}`;
-}
-
-/**
- * Pre-instantiated singleton event bus for AI assistant activity.
- *
- * - `halo-start` / `halo-stop` are forwarded via a tab-scoped `BroadcastChannel` so that
- *   popout windows opened from this tab show halo animations, while remaining isolated from
- *   unrelated tabs on the same origin (tab-scoped channel name).
- * - `tool-loop-start` / `tool-loop-end` are cross-tab for the same reason: they describe the
- *   assistant's lifecycle (a turn beginning / ending), and the most common subscribers
- *   (workspace transitions, post-turn deferred recomputation, UI gates tied to the assistant
- *   being idle) need the event regardless of whether the user is interacting with the chat
- *   in the main tab or a popout window. Tab-local-only telemetry can subscribe and filter.
- * - `chat-popout` / `chat-popin` are in-memory only — they must only affect the tab where the
- *   user clicked.
- *
- * @beta
- */
-export const agenticActivityBus = new AgenticActivityBus({
-  crossTabEvents: ['halo-start', 'halo-stop', 'tool-loop-start', 'tool-loop-end'],
-  // Lazy: the tab-scoped name (and its `sessionStorage` read) is computed on first
-  // cross-tab use in a browser, not at module-eval — so importing this module is
-  // side-effect-free and Node/test-safe.
-  channelNameFactory: () => getTabScopedChannelName('foundation-ai-activity'),
-});

package/src/channel/ai-activity-channel.ts

@@ -1,146 +0,0 @@
-import type { AIProviderType, TurnFailureReason } from '@genesislcap/foundation-ai';
-
-/**
- * Event map for the AI activity bus.
- *
- * Declare-merge this interface to add your own event types:
- * ```ts
- * declare module '@genesislcap/ai-assistant' {
- *   interface AgenticActivityEvents {
- *     'grid-flash-rows': { gridId: string; rowIds: string[] };
- *   }
- * }
- * ```
- *
- * @beta
- */
-export interface AgenticActivityEvents {
-  /** Fired when the assistant begins a tool call. Contains the names of all active tools. */
-  'halo-start': { toolNames: string[] };
-  /** Fired when the assistant finishes all tool processing and returns to idle. */
-  'halo-stop': undefined;
-  /** Fired when the user clicks the expand button — moves assistant from bubble into layout. State lives in the session store, not in this event. */
-  'chat-popout': undefined;
-  /** Fired when the user clicks the collapse button — moves assistant from layout back to bubble. State lives in the session store, not in this event. */
-  'chat-popin': undefined;
-  /**
-   * Fired immediately before the tool loop begins running for the current turn — after the busy
-   * flag is set and the user message (if any) has been appended, but before the first
-   * provider call. Pairs with {@link AgenticActivityEvents.'tool-loop-end'}.
-   *
-   * Boundary: this is the moment the assistant takes control from the user on the **main chat
-   * prompt** to begin a turn. It is **not** fired when a tool handler temporarily hands a
-   * widget to the user mid-loop (e.g. `requestInteraction` pausing a handler while a planning
-   * widget is rendered) — those widget pauses happen inside the loop and the assistant is
-   * still considered to own the turn.
-   *
-   * Fires from each `ChatDriver`'s `sendMessage` and `continueFromHistory`, so during a
-   * multi-agent handoff orchestrated by `OrchestratingDriver` it fires once per agent
-   * the orchestrator hands off to.
-   *
-   * Distinct from {@link AgenticActivityEvents.'halo-start'} — the halo event is keyed to
-   * tool-call messages arriving in the stream (UI animation concern), not to the loop boundary
-   * itself. Use this event for hooks tied to a turn beginning (telemetry, transient UI gates).
-   */
-  'tool-loop-start': undefined;
-  /**
-   * 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).
-   *
-   * 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.
-   *
-   * Emitted from the finally block of each `ChatDriver`'s `sendMessage` and
-   * `continueFromHistory`, so a multi-agent handoff fires this event once per agent.
-   *
-   * 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).
-   *
-   * 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.
-   *
-   * A `'budget-exhausted'` failure additionally carries `vendor` — the concrete
-   * vendor the walled turn resolved to (GENC-1464), which is NOT the same thing as
-   * the registry alias recorded on the debug-log entry. Optional and additive: a
-   * subscriber reading only `failureReason` is unaffected, and every other
-   * failure still emits the historical `{ failureReason }` with no `vendor` key.
-   * It exists so a later per-vendor budget model is an additive change rather
-   * than a retrofit — the vendor is known at the transport and at the driver, and
-   * was previously discarded between them.
-   *
-   * Note this topic is forwarded on the tab-scoped channel, so a wall hit in a
-   * popped-out window reaches the main window's subscribers too — which is why
-   * the assistant's blocked latch fires there as well. Correct for a shared spend
-   * cap; see `docs/migration-GENC-1464.md` §Scope.
-   */
-  'tool-loop-end':
-    | {
-        failureReason?: TurnFailureReason;
-        vendor?: AIProviderType;
-        /**
-         * Proxy-reported spend figures, present only on `budget-exhausted`. Carried
-         * here because this event — not the driver's return value — is what latches
-         * the blocked state for a wall hit INSIDE the tool loop (the common case):
-         * the publish happens in `sendMessage`'s `finally`, so it lands before the
-         * return-value seam and wins the latch. Without these the banner would fall
-         * back to the generic copy in exactly the path the figures were added for.
-         * Plain numbers + string keep the detail structured-cloneable for the
-         * cross-tab hop.
-         */
-        budget?: {
-          budgetUsd?: number;
-          spentUsd?: number;
-          vendorLabel: string;
-          /**
-           * The refusing vendor as a typed value: normalised from `vendorLabel`
-           * where a vendor claims that label, otherwise from the proxy's own
-           * `vendor` field on the 402 — so it can disagree with `vendorLabel`,
-           * which is what keeps attribution working behind a white-labelled or
-           * multiplexing gateway.
-           *
-           * Distinct from the detail's top-level `vendor` (the driver's
-           * last-resolved provider): this one comes from the transport that was
-           * actually refused, so it is the one a per-vendor latch trusts first.
-           */
-          vendor?: AIProviderType;
-          /**
-           * The proxy's verdict on whether any OTHER vendor it meters still has
-           * headroom. The one fact here a subscriber cannot work out for itself:
-           * the registry says which vendors EXIST, never which still have
-           * budget. A `false` is what stops the banner advising a switch to a
-           * vendor that is equally spent.
-           */
-          otherVendorAvailable?: boolean;
-        };
-      }
-    | 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
-   * in flight. Pairs with {@link AgenticActivityEvents.'interaction-resolved'}.
-   *
-   * This is the inverse boundary to {@link AgenticActivityEvents.'tool-loop-start'}: the
-   * loop is running (still inside `tool-loop-start`/`tool-loop-end`) but is momentarily idle,
-   * waiting on the user. Use it for hooks that are unsafe *while computing* but safe *while
-   * parked* — e.g. enabling a control that must not change mid-request but is fine to change
-   * during a long journey step. Tab-local (not forwarded cross-tab): the widget and its
-   * waiting state belong to the tab that opened it.
-   */
-  'interaction-requested': undefined;
-  /**
-   * Fired when a parked widget interaction ends — by user completion, timeout, or
-   * cancellation — just before the suspended tool handler resumes and the loop continues.
-   * Pairs with {@link AgenticActivityEvents.'interaction-requested'}. After this the turn is
-   * computing again (until `tool-loop-end`). Tab-local.
-   */
-  'interaction-resolved': undefined;
-}

package/src/chat-driver-node.ts

@@ -1,159 +0,0 @@
-/**
- * Node-safe headless entry point for the AI assistant driver stack (`@genesislcap/ai-assistant/chat-driver`).
- *
- * Re-exports ONLY the framework-agnostic pieces — {@link ChatDriver}, `OrchestratingDriver`, the
- * agent-config surface (`defineAgent`, `defineStatefulAgent`, and the config/input types), and the
- * activity-bus types/`NOOP_ACTIVITY_BUS` — WITHOUT the DOM/FAST component layer that the package's
- * main entry (`.`) pulls in via `main/main`. This lets a Node / CommonJS host (server, unit tests,
- * benches) construct and drive `ChatDriver` over `foundation-ai` providers with no jsdom and no
- * custom-element registration.
- *
- * Every module re-exported here is DOM-clean at import time (no `window`/`document`/`sessionStorage`
- * eval-time access, no `@genesislcap/web-core`). The activity bus is imported for its types and the
- * no-op default; its cross-tab `BroadcastChannel` is created lazily and only in a browser, so
- * pulling this entry into Node opens nothing.
- *
- * @packageDocumentation
- * @beta
- */
-export * from './components/chat-driver';
-export * from './components/orchestrating-driver';
-export * from './channel/ai-activity-channel';
-export * from './channel/ai-activity-bus';
-export * from './config/config';
-export * from './config/define-stateful-agent';
-export * from './config/fallback-agents';
-
-// Provider-construction surface, re-exported from `@genesislcap/foundation-ai` so a headless
-// consumer builds its registry from the SAME bundled foundation-ai instance the driver uses. That
-// shared identity matters: `ChatDriver`'s malformed/truncated handling does `instanceof` on the
-// transports' error classes, so a second foundation-ai copy (a separate dep) would silently break
-// those checks. NAMED re-exports only — `export *` would drag in the FAST-DI module
-// (`@microsoft/fast-foundation` → `fast-element` → `document` at eval); by naming just these,
-// esbuild tree-shakes the DI module out and the bundle stays Node-loadable.
-export {
-  AnthropicProvider,
-  AnthropicTransport,
-  GeminiProvider,
-  GeminiTransport,
-  MutableAIProviderRegistry,
-  // Supported-model allowlists — so a headless consumer validates a configured model id against
-  // foundation-ai's REAL list instead of maintaining a parallel hardcoded copy that silently drifts
-  // as the platform adds models (a valid new model would otherwise look like a misconfiguration).
-  // GENC-1461, create PR #1644 review.
-  SUPPORTED_ANTHROPIC_MODEL_IDS,
-  SUPPORTED_GEMINI_MODEL_IDS,
-  // The provider wall (GENC-1506). Re-exported for the same anti-drift reason as the model lists
-  // above, and it matters more here because the other end of this contract is in ANOTHER REPO:
-  // genesis-create's ai-service stamps `PROVIDER_REFUSED_CODE` onto its proxy responses and shows
-  // `DEFAULT_PROVIDER_REFUSED_MESSAGE` on its own generation surfaces. Hand-copying either would
-  // drift silently — a renamed code stops classifying, and a second copy of the sentence survives
-  // the first reword. `ProviderRefusedError` is here so a headless caller can `instanceof` it
-  // against the same bundled instance the driver throws from.
-  DEFAULT_PROVIDER_REFUSED_MESSAGE,
-  PROVIDER_REFUSED_CODE,
-  ProviderRefusedError,
-  isObservableAIProviderRegistry,
-  // Request pricing. Re-exported HERE, not left to a direct `@genesislcap/foundation-ai`
-  // import, for the same reason as everything above it: a headless host that adds its own
-  // foundation-ai dependency gets a second copy, and the driver's malformed/truncated
-  // handling does `instanceof` on the transports' error classes. Reaching the pricing
-  // should not cost a consumer that guarantee.
-  //
-  // These take RAW provider usage rather than a `ChatMessage` — see the foundation-ai
-  // module docs. They are for the path where nothing stamped a cost (a proxied or
-  // server-side call holding a usage block); when a message already carries `cost`, use
-  // it, because it was computed with the per-TTL cache split the message no longer has.
-  ANTHROPIC_CACHE_READ_MULTIPLIER,
-  ANTHROPIC_CACHE_WRITE_1H_MULTIPLIER,
-  ANTHROPIC_CACHE_WRITE_5M_MULTIPLIER,
-  anthropicRatesFor,
-  anthropicTokenCost,
-  GEMINI_CACHED_INPUT_MULTIPLIER,
-  GEMINI_LONG_CONTEXT_THRESHOLD,
-  geminiRatesFor,
-  geminiTokenCost,
-  // Resolves a model id to its vendor, so a caller holding only `message.model` can pick
-  // between the two cost functions above without maintaining its own model→vendor map.
-  vendorOfModel,
-} from '@genesislcap/foundation-ai';
-export type {
-  // Re-exported alongside `sumUsage` below — a consumer that can call the function but cannot NAME
-  // its return type has to restate the shape by hand, which is how the buckets get mis-summed.
-  AggregateUsage,
-  AIProvider,
-  AIProviderRegistry,
-  AnthropicModelId,
-  CachePolicy,
-  // The attachment union, so a headless caller can hand a screenshot to a model or return one
-  // from a tool handler without restating the shape — and, more to the point, without missing
-  // that the image arm's `kind` is REQUIRED and is the only thing the transports branch on.
-  ChatAttachment,
-  ChatFallback,
-  ChatImageAttachment,
-  ChatMessage,
-  ChatRequestOptions,
-  ChatTextAttachment,
-  ChatThinkingPolicy,
-  ChatToolChoice,
-  ChatToolDefinition,
-  ChatToolHandlers,
-  ChatToolResult,
-  GeminiModelId,
-  // Pricing input/output shapes, alongside the functions re-exported above — a caller that
-  // can invoke them but cannot name their argument or result has to restate the shape by
-  // hand, which is how the token buckets get mixed up between the two providers.
-  AnthropicUsageRecord,
-  GeminiUsageRecord,
-  TokenCost,
-  TokenCostBreakdown,
-  TokenRates,
-} from '@genesislcap/foundation-ai';
-
-// Usage/cost summation. A headless consumer attributing spend to a run has no other route to it:
-// the transports' `getLifetimeCost()` is per-instance and lifetime-scoped, so a shared registry
-// makes it unattributable, and re-deriving cost from token counts is wrong in the one direction
-// that matters (`inputTokens` is total prompt size INCLUDING the cached part, so re-pricing charges
-// every cached token at full rate). `sumUsage` reads the per-request cost the transports already
-// stamped, and recurses into `toolCalls[].subAgentTrace` — where the entire spend of a delegating
-// agent lives — and into `compaction.rolledUpUsage`, which is spend whose messages no longer exist.
-// Both are invisible when omitted: the total is merely too low, which reads as a cheap run.
-//
-// `addUsage`/`emptyUsage` are the composition primitives for a conversation that CONTINUES across
-// rounds — see the guidance on `sumUsage` itself. `totalTokens` exists because the four buckets of
-// an `AggregateUsage` are disjoint and safe to add, which the per-message fields are NOT.
-//
-// `messageUsage` is the single-message projection of the same arithmetic — what ONE request
-// cost, in the same four-bucket shape. It is what prices a turn snapshot (see
-// `TurnSnapshot.usage`), and the reason a consumer needs it separately is that the response
-// to a *failed* attempt never reaches history, so `sumUsage` over the transcript cannot see
-// that spend at all.
-export { addUsage, emptyUsage, messageUsage, sumUsage, totalTokens } from './utils/sum-usage';
-
-// Per-call projection, for the cases an aggregate cannot serve: usage rows for
-// per-project attribution, a cost dashboard, or auditing which turns came back
-// unpriced. `usageRows` is guaranteed to reconcile with `sumUsage` — including spend a
-// compaction banked, which has no message of its own and which a naive per-message walk
-// therefore drops while the total keeps it. Both take RAW history; `UsageRow` is
-// deliberately not a `ChatMessage`, so passing rows back into `sumUsage` (which recurses
-// itself, and would double-count) does not compile.
-export { usageRows } from './utils/usage-rows';
-export type { UsageRow } from './utils/usage-rows';
-
-// Debug-log harvesting (GENC-1461 unified diagnostics). A headless consumer collates its driver's
-// log — `buildTimelineEntries({ turnSnapshots: driver.getTurnSnapshots(), messages:
-// driver.getHistory(), metaEvents: getMetaEvents(sessionKey) })` → `DiagnosticEntry[]` — ships it to
-// the client, which folds it into the assistant's debug log via `InteractionResult.diagnostics`
-// (see `ChatDriver.getExternalDiagnostics`). `clearSession(sessionKey)` drops the per-request
-// meta-event bucket so the long-lived server process's module registry doesn't grow unbounded.
-// All three modules are DOM-clean, so the node entry stays Node-loadable.
-export { clearSession, getMetaEvents } from './state/debug-event-log';
-export type { MetaEvent } from './state/debug-event-log';
-export { buildTimelineEntries } from './state/persistence/build-timeline-entries';
-export type { TurnSnapshotLike } from './state/persistence/build-timeline-entries';
-// `withFreshMetaSnapshot` matters to a headless consumer that stitches a STORED stream: the
-// newest stored `meta-snapshot` is frozen at the last config-signature change, so its context
-// and cost figures are as old as that. Pass a fresh snapshot of your own through this before
-// `assembleDebugLog`, or state in your own output that the totals are historical.
-export { assembleDebugLog, withFreshMetaSnapshot } from './state/persistence/diagnostics';
-export type { DebugLog, DiagnosticEntry } from './state/persistence/diagnostics';