import { FC } from 'react';
interface Props {
    /** How many spoken turns this conversation holds. Never rendered at 0. */
    count: number;
    onOpenTranscript: () => void;
}
/**
 * "You said things here that this thread is not showing you."
 *
 * ★ The assistant and the typed thread share ONE backend session, and the
 * client sends no history array — the model's memory IS that session. So a
 * spoken turn is in the model's context permanently, whether or not the chat
 * panel draws it. Hiding those turns without saying so produced the worst
 * possible combination: replies that open "as I mentioned about your urea dose"
 * with no such message anywhere on screen, and an Export button on a chat that
 * looks empty.
 *
 * The fix is not to hide harder. It is to stop the thread implying that what it
 * shows is everything it knows.
 *
 * ★ Deliberately NOT a message bubble. Putting spoken content back in the
 * timeline is the exact leak the split was built to stop; this is a pointer to
 * the other surface, and it carries a count rather than any spoken words.
 *
 * Renders above both the message list and the empty state, because the empty
 * state is where it matters most — a voice-only conversation otherwise reads as
 * "nothing here" while holding a full exchange.
 */
export declare const AssistantSpokenTurnsNotice: FC<Props>;
export {};
//# sourceMappingURL=AssistantSpokenTurnsNotice.d.ts.map