import type { AskDisplayProps } from "./types";
/**
 * `ASK` segment — the assistant asking WHICH reading of an ambiguous question it
 * should answer, as a card of numbered options instead of prose bullets
 * (Figma 1:13775).
 *
 * Picking a row sends its `label` verbatim as the user's next message: the
 * backend's guide classifier resolves that reply against the labels it offered,
 * so the row text IS the protocol.
 *
 * Without `onSelect` the card renders LOCKED — dimmed under a veil, rows
 * `disabled`, not-allowed cursor. That is the normal end state: `ChatMessageList`
 * withholds the handler as soon as any user message follows the card, because
 * the question it asked has been answered and re-clicking it would send a stale
 * label into a conversation that moved on. Same state on observer surfaces,
 * where a click would post into someone else's dialog.
 *
 * A run of consecutive `ask` segments is one card with a pager ("1 of 2"), so a
 * turn that asks twice reads as a single block. With one card the pager is
 * absent entirely — there is nothing to page through.
 */
declare const AskDisplay: import("react").ForwardRefExoticComponent<AskDisplayProps & import("react").RefAttributes<HTMLDivElement>>;
export { AskDisplay };
//# sourceMappingURL=ask-display.d.ts.map