import { C as ConnectUIOptions, H as HostAdapter, S as SynapseUITheme } from '../detect-DVGaL2bH.cjs';
export { a as HostCapabilities, b as HostKind, c as HostUnsupportedError, d as SYNAPSE_DATA_ELEMENT_ID, e as SynapseUIClient, T as ToolCallError, f as adapterForKind, g as connectUI, h as detectHostKind, s as selectAdapter } from '../detect-DVGaL2bH.cjs';

/**
 * Inline / standalone fallback adapter.
 *
 * No live host bridge — used for SSR, previews, and a plain browser render. Data
 * comes only from the baked-in `<script type="application/json">` blob; there is
 * nothing to push, so `onData` never fires after `start()`. Theme follows the OS
 * color scheme and tracks `prefers-color-scheme` changes. `openLink` opens a new
 * tab; `sendPrompt`/`callTool` have no destination.
 */
declare function createInlineAdapter(win: Window & typeof globalThis, options: ConnectUIOptions): HostAdapter;

/**
 * MCP Apps standard (SEP-1865) adapter — the bridge for every framed host.
 * ChatGPT, Claude and NimbleBrain all implement the standard, so there is one.
 *
 * The View iframe is an MCP client speaking JSON-RPC 2.0 to `window.parent`:
 *
 *  1. posts `ui/initialize` and awaits the host context (theme, style variables);
 *  2. posts `ui/notifications/initialized`, then a `size-changed` — a host keeps
 *     the frame hidden until it has both the handshake and a size;
 *  3. receives data via `ui/notifications/tool-result` (`params` IS the
 *     `CallToolResult`, so data is at `params.structuredContent`) and theme via
 *     `ui/notifications/host-context-changed`.
 *
 * Actions go up as requests: `ui/open-link`, `ui/message` (follow-up), and
 * `tools/call` (pull).
 */
declare function createMcpAppsAdapter(win: Window & typeof globalThis, options: ConnectUIOptions): HostAdapter;

/**
 * Apply a resolved theme to the DOM for the cross-host client.
 *
 * Two conventions coexist across Synapse components, so the client drives both:
 *
 *  - `document.documentElement[data-theme="light"|"dark"]` — how self-contained
 *    HTML components (Bassethound's report) gate their `--var` palettes, and the
 *    lever a host's light/dark signal actually flips.
 *  - CSS custom properties via {@link applyTheme} — how the
 *    `@nimblebrain/synapse/ui` token components consume theme, backed by the
 *    SDK's neutral defaults so every referenced var resolves in both modes.
 *
 * Setting both means an app can use either convention (and a host that supplies
 * only a mode string still themes correctly). SSR-safe.
 *
 * Fonts travel separately, as the host's `@font-face` CSS: see
 * {@link injectHostFonts}.
 */
declare function applyHostTheme(theme: SynapseUITheme): void;
/** Read the OS-level color scheme as a sane default for hosts that don't push a
 *  theme until the handshake completes, or ever (standalone). */
declare function preferredMode(win: Window | undefined): "light" | "dark";
/** Coerce an arbitrary host-supplied theme signal to a mode. Accepts the string
 *  form (`"dark"`) both hosts use; anything else falls back. */
declare function coerceMode(value: unknown, fallback: "light" | "dark"): "light" | "dark";

export { ConnectUIOptions, HostAdapter, SynapseUITheme, applyHostTheme, coerceMode, createInlineAdapter, createMcpAppsAdapter, preferredMode };