import type { VendoTheme } from "../core/apps/index.js";
import { type VendoAppRef, type VendoApprovalRef } from "../core/index.js";
import { type DynamicToolUIPart, type ToolUIPart, type UIDataTypes, type UIMessagePart, type UITools } from "ai";
/**
 * Existing-agents contract — prop shapes for the three embeds a BYO chat
 * surface renders from `vendo_*` tool outputs. The components behind them are
 * built on the existing slot / build-beat / approval-card machinery, on the
 * defaults a `VendoProvider` overrides when the host mounts one.
 * Frozen by this file's exported shape and its tests.
 *
 * `theme` is the one addition since the freeze (approved 2026-08-23): an
 * OPTIONAL per-surface override, never a required prop and never a second way
 * to say what the provider already says.
 */
/** Inline generated app: build-beat while the build streams, then the live
 *  app. In-app interactions go over the wire, not through the host loop. */
export interface VendoAppEmbedProps {
    refValue: VendoAppRef;
    /**
     * This embed's own brand tokens, merged group by group over the provider's
     * resolved theme — the same merge `VendoProvider` does over
     * `defaultVendoTheme`, so a bare embed merges over the defaults. The approval
     * modal a press inside the app parks on carries them too.
     *
     * FRAME ONLY: it styles Vendo's own chrome — the app card's bar, the beats,
     * the failure notice. The mounted generated view keeps the PROVIDER theme,
     * whether it is iframe-served (themed over the app transport) or rendered
     * natively: the tree surface restates the provider tokens on its own root,
     * so the local ones do not cascade in.
     */
    theme?: Partial<VendoTheme>;
}
/** Where an approval embed can be, in the order it gets there. The wire owns
 *  the state; the embed only renders it — resolving in place to the executed
 *  outcome, "declined", or "expired" (the existing failed/expired vocabulary,
 *  never a silent blank). */
export type VendoApprovalEmbedState = "pending" | "executed" | "declined" | "expired";
/** Approve/deny for a parked guarded call. */
export interface VendoApprovalEmbedProps {
    refValue: VendoApprovalRef;
    /**
     * This embed's own brand tokens, merged group by group over the provider's
     * resolved theme — the same merge `VendoProvider` does over
     * `defaultVendoTheme`, so a bare embed merges over the defaults.
     *
     * FRAME ONLY: it styles Vendo's own chrome. A mounted generated view keeps
     * the PROVIDER theme, whether it is iframe-served (themed over the app
     * transport) or rendered natively: the tree surface restates the provider
     * tokens on its own root, so the local ones do not cascade in.
     */
    theme?: Partial<VendoTheme>;
}
/** The dispatcher: give it any `vendo_*` tool output and it renders the right
 *  embed by `parseVendoToolEnvelope`, or nothing for plain data. */
export interface VendoToolResultProps {
    output: unknown;
    /**
     * Passed straight through to whichever embed the envelope dispatches to:
     * this surface's own brand tokens, merged group by group over the provider's
     * resolved theme — the same merge `VendoProvider` does over
     * `defaultVendoTheme`, so a bare embed merges over the defaults.
     *
     * FRAME ONLY: it styles Vendo's own chrome. A mounted generated view keeps
     * the PROVIDER theme, whether it is iframe-served (themed over the app
     * transport) or rendered natively: the tree surface restates the provider
     * tokens on its own root, so the local ones do not cascade in.
     */
    theme?: Partial<VendoTheme>;
}
/**
 * Is this message part Vendo's? True for a tool part — `dynamic-tool` and
 * `tool-<name>` alike — whose tool name carries the prefix every pack tool is
 * namespaced under. It narrows, so `part.output` and `part.state` read after it
 * with no cast.
 *
 * ```tsx
 * if (isVendoToolPart(part)) return <VendoToolResult output={part.output} />;
 * // your own parts fall through to your own rendering
 * ```
 *
 * It answers "is this Vendo's", never "is it finished": a part still streaming
 * carries no output and `<VendoToolResult>` renders nothing for it, so
 * `part.state === "output-available"` stays your own visible check, for
 * wherever you want to show a running one.
 *
 * Order it against your own tools however you like — it matches on the tool
 * NAME, so a host's own `dynamic-tool` part is never mistaken for one of ours.
 */
export declare function isVendoToolPart<TOOLS extends UITools>(part: UIMessagePart<UIDataTypes, TOOLS>): part is ToolUIPart<TOOLS> | DynamicToolUIPart;