import { FC } from 'react';
/**
 * The header's secondary surface — everything that CONFIGURES the assistant.
 *
 * ★ `+` supplies content, `⋯` configures. Keeping those two meanings apart is
 * the point: the header carried seven controls, and three of them
 * (auto-read, the voice picker, export) render null under conditions the user
 * cannot see — no speech support, fewer than two voices, an empty conversation —
 * so the row silently changed width between devices and between the first and
 * second message of the same session.
 *
 * Now four primary controls, always present, and one menu that absorbs the
 * conditional ones. A menu ROW may still hide itself; a menu that keeps its
 * position while its contents vary is a much smaller surprise than a toolbar
 * that reflows.
 *
 * ★ Export is FLATTENED into this menu rather than nested inside it. It was
 * itself a dropdown, and a dropdown inside a dropdown is two Escape presses and
 * two outside-click regions for two menu items.
 *
 * ★ The voice picker keeps its native `<select>`. It is deliberate — see that
 * component — and a custom listbox would look tidier in a screenshot while being
 * worse on the phones this product is used on. Because the select lives inside
 * the menu's own subtree, the outside-click handler ignores clicks on it.
 *
 * Not included, deliberately: Live captions and Assistant settings have nothing
 * behind them yet, and a Transcript entry needs a product decision first (the
 * voice transcript is session-scoped, while the chat thread is always visible —
 * one menu label cannot honestly mean both).
 */
export declare const AssistantMoreMenu: FC;
//# sourceMappingURL=AssistantMoreMenu.d.ts.map