@genesislcap/ai-assistant 15.19.0 → 15.19.1

package/src/main/main.types.ts

@@ -1,225 +0,0 @@
-/**
- * State of the AI assistant component.
- *
- * `cancelling` is a refinement of `loading`: a stop was requested but the turn
- * is still winding down (e.g. a tool mid-execution finishing). It is "busy"
- * like `loading` — use the host's `busy` getter for "is a turn active" gates.
- *
- * @beta
- */
-export type AiAssistantState = 'idle' | 'loading' | 'cancelling' | 'error';
-
-/**
- * Controls the pop-out button shown in the assistant header.
- * - `"expand"` — assistant is embedded in the bubble dialog; button expands it to a layout panel.
- * - `"collapse"` — assistant is in a layout panel; button collapses it back to the bubble.
- *
- * @beta
- */
-export type PopoutMode = 'expand' | 'collapse';
-
-export type { AgentPickerMode } from '@genesislcap/foundation-ai';
-
-/**
- * Result returned by {@link FoundationAiAssistant.submitMessage}.
- *
- * `ok` is `false` when the assistant is busy, the message is empty, or any
- * supplied file failed validation — in which case no send was dispatched and
- * `errors` lists the reasons.
- *
- * @beta
- */
-export interface SubmitMessageResult {
-  ok: boolean;
-  errors: string[];
-}
-
-/**
- * `detail` of the `AiAssistantEvent.SessionCleared` event. Captured *before*
- * teardown so a host can tidy up whatever the active agent was working on
- * (generated files, server-side scratch, …). `agentSnapshot` is the agent's
- * `serialize()` output (a state-machine image for machine-backed agents).
- *
- * @beta
- */
-export interface SessionClearedDetail {
-  sessionKey: string | undefined;
-  agentName: string | undefined;
-  agentSnapshot: unknown;
-}
-
-/**
- * `detail` of the `AiAssistantEvent.ChatHeaderMouseDown` event.
- *
- * @beta
- */
-export interface ChatHeaderMouseDownDetail {
-  clientX: number;
-  clientY: number;
-}
-
-/**
- * DOM events the `<foundation-ai-assistant>` element dispatches to its host.
- * All bubble and are `composed` (they cross the shadow boundary), so a host can
- * listen on the element — or any ancestor — to react. Use these constants to
- * wire listeners instead of hand-typing event-name strings.
- *
- * An `as const` map (not a TS `enum` — this package ships none), so it serves as
- * both the listener-name value and, via the same-named type below, a union.
- *
- * @example
- * ```ts
- * import { AiAssistantEvent, type SessionClearedDetail } from '@genesislcap/ai-assistant';
- *
- * el.addEventListener(AiAssistantEvent.SessionCleared, (e) => {
- *   const { agentName, agentSnapshot } = (e as CustomEvent<SessionClearedDetail>).detail;
- *   // …clean up external state the agent was working on…
- * });
- * ```
- *
- * @beta
- */
-export const AiAssistantEvent = {
-  /** Session wiped via the lifecycle menu's Clear. `detail`: `SessionClearedDetail`. */
-  SessionCleared: 'session-cleared',
-  /** Header pressed in `popout-mode="expand"` (drag-to-popout hosts). `detail`: `ChatHeaderMouseDownDetail`. */
-  ChatHeaderMouseDown: 'chat-header-mousedown',
-} as const;
-
-/**
- * One of the `AiAssistantEvent` event-name values.
- *
- * @beta
- */
-export type AiAssistantEvent = (typeof AiAssistantEvent)[keyof typeof AiAssistantEvent];
-
-/**
- * One rendered row of the settings-modal budget meter (GENC-1464) — a vendor
- * that currently has budget figures, pre-formatted so the template stays a pure
- * binding layer (and so tests can pin the exact text a user reads).
- *
- * @beta
- */
-export interface SettingsBudgetRow {
-  /** The vendor the row describes (an `AIProviderType` member). */
-  vendor: string;
-  /** Display name from `VENDOR_LABELS`, e.g. `Anthropic`. */
-  label: string;
-  /**
-   * The real figures — `$45.00 / $50.00 (90%)`. The percentage is NOT clamped:
-   * spend can genuinely overshoot the cap (the last allowed call may cross it),
-   * and the text tells the truth about it.
-   */
-  figures: string;
-  /**
-   * The bar's value, clamped to `0..100` — a progress bar past its end renders
-   * nonsense, so only the bar clamps (mirroring the context-usage indicator's
-   * `Math.min(100, …)`).
-   */
-  barValue: number;
-}
-
-/**
- * State of the chat suggestions feature.
- *
- * @beta
- */
-export type SuggestionsState =
-  | { status: 'idle' }
-  | { status: 'loading' }
-  | { status: 'loaded'; suggestions: string[] }
-  | { status: 'error'; message: string };
-
-/**
- * Metadata describing a UI animation in the assistant.
- *
- * @beta
- */
-export interface AiAssistantAnimationDef {
-  /** Display label shown in the settings multiselect. */
-  label: string;
-  /** Short description shown beneath the label in the categorized multiselect. */
-  description: string;
-  /** Group heading the option is listed under in the settings multiselect. */
-  category: string;
-}
-
-/**
- * Registry of all available animations with their display metadata.
- * Adding an entry here automatically extends the {@link AiAssistantAnimation} type.
- *
- * @remarks
- * `loading` (dots), `waves`, `flowingWaves` and `plasma` are interchangeable
- * styles of the same "is the assistant working" indicator and are therefore
- * grouped under the same {@link AiAssistantAnimationDef.category}. They are
- * mutually exclusive — see `LOADING_STYLE_ANIMATIONS`.
- *
- * @beta
- */
-export const ANIMATION_DEFS = {
-  loading: {
-    label: 'Dots',
-    description: 'Shows pulsing dots while the assistant is generating a response.',
-    category: 'Loading style',
-  },
-  waves: {
-    label: 'Waves',
-    description:
-      'Shows glowing sine waves inside a circle while the assistant is generating a response.',
-    category: 'Loading style',
-  },
-  flowingWaves: {
-    label: 'Flowing waves',
-    description:
-      'Shows coloured waves rising and settling from a line while the assistant is generating a response.',
-    category: 'Loading style',
-  },
-  plasma: {
-    label: 'Plasma orb',
-    description:
-      'Shows a glowing plasma sphere with drifting energy while the assistant is generating a response.',
-    category: 'Loading style',
-  },
-  halo: {
-    label: 'Halo',
-    description:
-      'Displays a glowing halo around the assistant avatar while a response is streaming.',
-    category: 'Effects',
-  },
-} satisfies Record<string, AiAssistantAnimationDef>;
-
-/**
- * Union of all available animation names, derived from {@link ANIMATION_DEFS}.
- *
- * @beta
- */
-export type AiAssistantAnimation = keyof typeof ANIMATION_DEFS;
-
-/**
- * All available animation names, derived from the registry.
- *
- * @internal
- */
-export const ALL_ANIMATIONS = Object.keys(ANIMATION_DEFS) as AiAssistantAnimation[];
-
-/**
- * The interchangeable "assistant is working" loading-indicator styles. At most
- * one of these may be enabled at a time — enabling one disables the other.
- *
- * @internal
- */
-export const LOADING_STYLE_ANIMATIONS = [
-  'loading',
-  'waves',
-  'flowingWaves',
-  'plasma',
-] as const satisfies readonly AiAssistantAnimation[];
-
-/**
- * Animations enabled by default when a consumer opts into the animations
- * feature without specifying an explicit `enabled` list. Keeps the dots loading
- * style (the long-standing default); the waves style is opt-in.
- *
- * @internal
- */
-export const DEFAULT_ANIMATIONS: AiAssistantAnimation[] = ['loading', 'halo'];

package/src/main/persistence-broken-sources.test.ts

@@ -1,219 +0,0 @@
-import { assert, createLogicSuite } from '@genesislcap/foundation-testing';
-import { DOM } from '@genesislcap/web-core';
-import { FoundationAiAssistant } from './main';
-
-// Hold a reference so the custom-element registration isn't tree-shaken.
-FoundationAiAssistant;
-
-// GENC-1511 — the blocking "not saving" modal has MORE THAN ONE reporter: this element's own
-// session persister (`sessions/<key>`), and a host reporting its own keyspaces through the public
-// API (Create's `projects/<id>.json`, which holds the app rather than the transcript).
-//
-// It was first built on a single `persistenceBroken` boolean, and review caught what that costs:
-// whichever reporter recovered FIRST closed the modal for both, and the host's own re-entry guard
-// then kept it from ever being raised again. This suite pins the per-source behaviour so that
-// collision cannot come back.
-//
-// Like `blocked-state.test.ts`, this exercises the METHODS the template bindings read rather than
-// the rendered DOM: `document.createElement` upgrades the element (constructor) without connecting
-// it, so `connectedCallback` never runs and nothing subscribes to `agenticActivityBus` — which
-// would otherwise hold the test runner's event loop open.
-const Suite = createLogicSuite('FoundationAiAssistant persistence-broken sources');
-
-/** A fresh, unconnected element. Nothing here needs a session store. */
-const element = (): FoundationAiAssistant =>
-  document.createElement('foundation-ai-assistant') as FoundationAiAssistant;
-
-/** The modal's visible copy, as the template bindings read it. */
-const copy = (el: FoundationAiAssistant) => ({
-  broken: el.persistenceBroken,
-  message: el.persistenceBrokenMessage,
-  detail: el.persistenceBrokenDetail,
-});
-
-const SESSION = 'session';
-const PROJECT = 'project';
-
-Suite('a single reporter raises and withdraws its own warning', () => {
-  const el = element();
-  assert.is(el.persistenceBroken, false);
-
-  el.reportPersistenceBroken({ detail: '2 messages have not been saved.', source: SESSION });
-  assert.is(el.persistenceBroken, true);
-  assert.is(el.persistenceBrokenDetail, '2 messages have not been saved.');
-
-  el.reportPersistenceRecovered(SESSION);
-  assert.is(el.persistenceBroken, false);
-  assert.is(el.persistenceBrokenMessage, undefined);
-  assert.is(el.persistenceBrokenDetail, undefined);
-});
-
-Suite('one source recovering does NOT withdraw another still-broken source', () => {
-  const el = element();
-  el.reportPersistenceBroken({ detail: 'session detail', source: SESSION });
-  el.reportPersistenceBroken({ message: 'project copy', source: PROJECT });
-
-  // The session's own save lands. Its warning goes; the project's must not.
-  el.reportPersistenceRecovered(SESSION);
-
-  assert.is(el.persistenceBroken, true, 'modal must stay up while the project store is failing');
-  assert.is(el.persistenceBrokenMessage, 'project copy', 'and must still describe THAT failure');
-
-  el.reportPersistenceRecovered(PROJECT);
-  assert.is(el.persistenceBroken, false, 'only once nothing is broken');
-});
-
-Suite('a later report does not overwrite an earlier source with its own copy', () => {
-  const el = element();
-  el.reportPersistenceBroken({
-    message: 'project copy',
-    detail: 'project detail',
-    source: PROJECT,
-  });
-
-  // The session reports with NO message override — it wants the template's session default.
-  // Before per-source tracking this assigned `undefined` over the project wording, so the modal
-  // claimed "this session has stopped saving" about a failed PROJECT write.
-  el.reportPersistenceBroken({ detail: 'session detail', source: SESSION });
-  assert.is(el.persistenceBrokenMessage, undefined, 'newest source wins while it is broken');
-  assert.is(el.persistenceBrokenDetail, 'session detail');
-
-  // ...and when the newest recovers, the copy falls BACK to the survivor rather than staying
-  // on the recovered source's wording (or reverting to the default).
-  el.reportPersistenceRecovered(SESSION);
-  assert.is(el.persistenceBrokenMessage, 'project copy');
-  assert.is(el.persistenceBrokenDetail, 'project detail');
-  assert.is(el.persistenceBroken, true);
-});
-
-Suite('recovering an unknown or already-recovered source is a no-op', () => {
-  const el = element();
-  el.reportPersistenceBroken({ message: 'project copy', source: PROJECT });
-
-  el.reportPersistenceRecovered(SESSION); // never reported
-  assert.equal(copy(el), { broken: true, message: 'project copy', detail: undefined });
-
-  el.reportPersistenceRecovered(PROJECT);
-  el.reportPersistenceRecovered(PROJECT); // twice
-  assert.equal(copy(el), { broken: false, message: undefined, detail: undefined });
-});
-
-Suite('re-reporting the same source refreshes its copy without duplicating it', () => {
-  const el = element();
-  el.reportPersistenceBroken({ detail: '2 messages have not been saved.', source: SESSION });
-  el.reportPersistenceBroken({ detail: '5 messages have not been saved.', source: SESSION });
-  assert.is(el.persistenceBrokenDetail, '5 messages have not been saved.');
-
-  // One recovery must clear it — a second entry for the same source would leave it stuck on.
-  el.reportPersistenceRecovered(SESSION);
-  assert.is(el.persistenceBroken, false);
-});
-
-Suite('a host that omits the source gets a default it can still recover', () => {
-  const el = element();
-  el.reportPersistenceBroken({ message: 'host copy' });
-  assert.is(el.persistenceBroken, true);
-
-  el.reportPersistenceRecovered();
-  assert.is(el.persistenceBroken, false);
-});
-
-Suite("a host's default source is independent of the session's", () => {
-  const el = element();
-  el.reportPersistenceBroken({ detail: 'session detail', source: SESSION });
-  el.reportPersistenceBroken({ message: 'host copy' });
-
-  el.reportPersistenceRecovered(); // the host's
-  assert.is(el.persistenceBroken, true, 'the session failure is still live');
-  assert.is(el.persistenceBrokenDetail, 'session detail');
-});
-
-// GENC-1511 (PR #2472 review) — the deferred show is a separate race from the source tracking.
-// `persistenceBrokenChanged` queues the show via `DOM.queueUpdate`, and the queued callback used
-// not to re-read the flag. A `true → false` inside the same batch runs the `!broken` branch against
-// a modal that was never shown (both statements no-op), and the callback then raised a blocking,
-// NON-DISMISSIBLE modal for a problem that had already fixed itself — with no further change event
-// left to close it, so the only way out was a reload nobody needed.
-//
-// Reachable because `maybeReportBroken` fires before `provider.save` in `persistSession`, so a
-// report and the write that withdraws it can share a tick.
-
-/** Minimal stand-in for the design-system modal, recording what the callback did to it. */
-function modalStub() {
-  const calls = { show: 0, close: 0 };
-  const dialog = document.createElement('dialog');
-  return {
-    calls,
-    modal: {
-      open: false,
-      mainElement: dialog,
-      show() {
-        calls.show += 1;
-        this.open = true;
-      },
-      close() {
-        calls.close += 1;
-        this.open = false;
-      },
-    },
-  };
-}
-
-/**
- * Drain the FAST update queue SYNCHRONOUSLY.
- *
- * `DOM.processUpdates()` and not an `await setTimeout(0)`: the queue lands on
- * `requestAnimationFrame`, which a zero-delay timer does not reliably cover. A timer-based flush
- * made these tests pass or fail on scheduling luck — the "does not show" assertion passed for the
- * wrong reason, and its positive control passed only because earlier tests had pumped the queue.
- */
-const flush = () => DOM.processUpdates();
-
-const withModal = (el: FoundationAiAssistant, modal: unknown) => {
-  (el as unknown as { persistenceModal: unknown }).persistenceModal = modal;
-};
-
-// POSITIVE CONTROL for the test below. Without it, a queue that never drains in this environment
-// would make the "does not show" assertion pass for entirely the wrong reason.
-Suite('the deferred show DOES raise the modal when the failure is still live', () => {
-  const el = element();
-  const { calls, modal } = modalStub();
-  withModal(el, modal);
-
-  el.reportPersistenceBroken({ detail: 'session detail', source: SESSION });
-  flush();
-
-  assert.is(calls.show, 1, 'precondition: the queued callback runs in this environment');
-  assert.is(modal.open, true);
-});
-
-Suite('a recovery inside the same batch cancels the deferred show', () => {
-  const el = element();
-  const { calls, modal } = modalStub();
-  withModal(el, modal);
-
-  el.reportPersistenceBroken({ detail: 'session detail', source: SESSION });
-  el.reportPersistenceRecovered(SESSION); // lands before the queue flushes
-  flush();
-
-  assert.is(el.persistenceBroken, false);
-  assert.is(calls.show, 0, 'must not raise a blocking modal for a resolved failure');
-  assert.is(modal.open, false);
-});
-
-Suite('a recovery of ONE source still shows for the source left broken', () => {
-  const el = element();
-  const { calls, modal } = modalStub();
-  withModal(el, modal);
-
-  el.reportPersistenceBroken({ detail: 'session detail', source: SESSION });
-  el.reportPersistenceBroken({ message: 'project copy', source: PROJECT });
-  el.reportPersistenceRecovered(SESSION);
-  flush();
-
-  assert.is(el.persistenceBroken, true);
-  assert.is(calls.show, 1, 'the project failure still warrants the modal');
-  assert.is(el.persistenceBrokenMessage, 'project copy');
-});
-
-Suite.run();

package/src/main/popout-interaction-gate.test.ts

@@ -1,87 +0,0 @@
-import type { ChatMessage } from '@genesislcap/foundation-ai';
-import { assert, createLogicSuite } from '@genesislcap/foundation-testing';
-import { FoundationAiAssistant } from './main';
-
-// Hold a reference so the custom-element registration isn't tree-shaken.
-FoundationAiAssistant;
-
-// GENC-1351 §5.11 (PR review): the single-element popout refactor removed the
-// `claimSideEffect` first-writer latch, so the only thing preventing a pending
-// interaction widget from being re-instantiated (and re-firing its side effect) on a
-// dock/undock move is that the popout control is disabled while an interaction is
-// pending — the template binds `?disabled=${x.hasActivePendingInteraction}`
-// (`main.template.ts`). This suite pins the GATE LOGIC (`hasActivePendingInteraction`)
-// that binding depends on, so a change to when the gate opens/closes is caught.
-//
-// Note: this deliberately does NOT mount the assistant. Mounting runs `connectedCallback`,
-// which subscribes to `agenticActivityBus` — opening a cross-tab `BroadcastChannel` in a browser
-// env and leaving the runner's event loop open. A getter-level test needs no mount and stays fast
-// + reliable. `document.createElement` only upgrades the element (constructor) — it does not
-// connect — so nothing subscribes, and the bus opens its channel lazily on first use, so none is
-// ever created here (no teardown needed).
-
-const Suite = createLogicSuite('FoundationAiAssistant popout interaction gate');
-
-/** A fresh (unconnected) element with a fake session store wired in. */
-function elementWith(state: string, messages: ChatMessage[]): FoundationAiAssistant {
-  const el = document.createElement('foundation-ai-assistant') as FoundationAiAssistant;
-  (el as unknown as { _sessionRef: unknown })._sessionRef = {
-    store: { aiAssistant: { state, messages } },
-  };
-  return el;
-}
-
-const withInteraction = (resolved: boolean | { value: string }): ChatMessage[] => [
-  { role: 'user', content: 'hi' } as ChatMessage,
-  {
-    role: 'assistant',
-    content: resolved ? 'done' : '',
-    interaction: { interactionId: '1', componentName: 'x', data: {}, resolved },
-  } as unknown as ChatMessage,
-];
-
-Suite('is true only while a turn is running AND a pending interaction is the last message', () => {
-  // Gated: a turn is running and the last message is an unresolved interaction. This is
-  // the state during which the popout/dock control MUST be disabled.
-  assert.is(
-    elementWith('loading', withInteraction(false)).hasActivePendingInteraction,
-    true,
-    'busy + unresolved interaction → gated',
-  );
-  // `cancelling` counts as busy too (a stop was requested but the turn is winding down).
-  assert.is(
-    elementWith('cancelling', withInteraction(false)).hasActivePendingInteraction,
-    true,
-    'cancelling + unresolved interaction → gated',
-  );
-});
-
-Suite('is false when idle, when the interaction is resolved, or when there is none', () => {
-  // Not busy → never gated, even with an unresolved interaction present.
-  assert.is(
-    elementWith('idle', withInteraction(false)).hasActivePendingInteraction,
-    false,
-    'idle → not gated',
-  );
-  // Busy but the interaction has resolved → the widget is answered, nothing to strand.
-  assert.is(
-    elementWith('loading', withInteraction({ value: 'ok' })).hasActivePendingInteraction,
-    false,
-    'resolved interaction → not gated',
-  );
-  // Busy but the last message is not an interaction at all.
-  assert.is(
-    elementWith('loading', [{ role: 'assistant', content: 'thinking' } as ChatMessage])
-      .hasActivePendingInteraction,
-    false,
-    'no interaction → not gated',
-  );
-  // No session / empty transcript.
-  assert.is(
-    elementWith('loading', []).hasActivePendingInteraction,
-    false,
-    'empty transcript → not gated',
-  );
-});
-
-Suite.run();

package/src/provider/ai-provider-switcher.ts

@@ -1,40 +0,0 @@
-import { DI } from '@genesislcap/web-core';
-
-/**
- * Optional app-registered policy for which cloud vendor backs the tier-shaped
- * provider registry slots (`low` / `high` / …). Apps inject a concrete
- * implementation on this DI token at bootstrap; consumers include the
- * slotted `settings-model` component or a header vendor control.
- * The platform settings modal does not render vendor UI itself.
- *
- * @beta
- */
-export interface AIProviderSwitcher {
-  readonly vendor: string;
-  readonly vendors: readonly string[];
-  switchTo(vendor: string): void;
-  subscribe(listener: (vendor: string) => void): () => void;
-}
-
-class NoopAIProviderSwitcher implements AIProviderSwitcher {
-  readonly vendor = '';
-  readonly vendors: readonly string[] = [];
-  switchTo(): void {
-    /* no-op */
-  }
-  subscribe(): () => void {
-    return () => {
-      /* no-op */
-    };
-  }
-}
-
-/**
- * The DI token for the {@link (AIProviderSwitcher:interface)}. Resolves a noop until the app
- * registers one.
- *
- * @beta
- */
-export const AIProviderSwitcher = DI.createInterface<AIProviderSwitcher>((x) =>
-  x.singleton(NoopAIProviderSwitcher),
-);

package/src/provider/assistant-app-settings.ts

@@ -1,84 +0,0 @@
-import { DI } from '@genesislcap/web-core';
-
-/**
- * One boolean toggle rendered in the platform settings modal app section.
- *
- * @beta
- */
-export interface AssistantAppSettingsToggle {
-  /** Stable id passed to {@link (AssistantAppSettingsProvider:interface).getValue} / `setValue`. */
-  id: string;
-  title: string;
-  description: string;
-  /** Optional `part` name for the toggle row (defaults to `app-toggle-${id}`). */
-  part?: string;
-  /** When provided and returns false, the toggle is hidden. */
-  visible?: () => boolean;
-  /** When provided and returns true, the switch is disabled. */
-  disabled?: () => boolean;
-  /** Optional footnote rendered below the row when the string is non-empty. */
-  hint?: () => string | undefined;
-}
-
-/**
- * Optional heading above a provider's toggle group.
- *
- * Entirely host-supplied — the assistant has no default title and no default icon, because the
- * section belongs to the host. Omit it and the toggles render bare, which is right when the
- * host's slotted content already titles them.
- *
- * @beta
- */
-export interface AssistantAppSettingsHeading {
-  readonly title: string;
-  /**
-   * Icon name for the design system's icon element (a Font Awesome free name, e.g.
-   * `'object-group'`). Omitted renders text only; an unknown name renders nothing at all, so
-   * check it against the installed Font Awesome set.
-   */
-  readonly icon?: string;
-}
-
-/**
- * App-supplied settings for the host's own section of the settings modal. Register a concrete
- * implementation on the DI token at app bootstrap; the assistant renders the toggles with the
- * same row layout as AI Chat Bot settings.
- *
- * The section itself is untitled by the assistant — no heading text and no icon — because only
- * the host knows what it is. Title it from the `settings-app` slot, which renders above these
- * toggles, and apply `assistantSettingsSectionTitleStyles` to match the built-in headings.
- *
- * @beta
- */
-export interface AssistantAppSettingsProvider {
-  readonly toggles: readonly AssistantAppSettingsToggle[];
-  /**
-   * Heading for the toggle group, for hosts that put other controls in the `settings-app` slot
-   * and need these distinguished from them. No default: absent means no heading.
-   */
-  readonly togglesHeading?: AssistantAppSettingsHeading;
-  getValue(id: string): boolean;
-  setValue(id: string, value: boolean): void;
-  /** Notify the assistant to re-read toggle values / visibility. */
-  subscribe?(listener: () => void): () => void;
-}
-
-class NoopAssistantAppSettingsProvider implements AssistantAppSettingsProvider {
-  readonly toggles: readonly AssistantAppSettingsToggle[] = [];
-  getValue(): boolean {
-    return false;
-  }
-  setValue(): void {
-    /* no-op */
-  }
-}
-
-/**
- * The DI token for the {@link (AssistantAppSettingsProvider:interface)}. Resolves a noop
- * until the host registers one.
- *
- * @beta
- */
-export const AssistantAppSettingsProvider = DI.createInterface<AssistantAppSettingsProvider>((x) =>
-  x.singleton(NoopAssistantAppSettingsProvider),
-);