import type { ReactNode } from "react";
import type { TabsPanelProps } from "./Tabs.tsx";
/**
 * The panel bar — every tab a `<button>`, every section a
 * `role="tabpanel"` this component renders and hides. See `Tabs`
 * for which of the two bars a screen wants.
 *
 * The composition is two hooks and one decision:
 *
 * ```ts
 * const selection = useSinglePicker({ selectedValue: initialKey })
 * const focus = useRovingFocus({ activeValue: initialKey })
 *
 * // `automatic` is this line, and `manual` is its absence.
 * if (activation === "automatic") selection.select(focus.activeValue)
 * ```
 *
 * ### Selection, not visibility — and the difference is not cosmetic
 *
 * M4 built this on `VisibilityGroup`, and the panels do end up
 * one-at-a-time either way, because the two cores are the same
 * shape. But the thing that **registers** here is the tab, not the
 * panel, and what a tab bar is asking is *which one did you pick*.
 * `SinglePicker` is the kind that answers that; the panel's
 * `hidden` is derived from the answer.
 *
 * Reading it the other way round cost something concrete: it made
 * `aria-selected` a report about a *panel's* visibility, so a
 * consumer wanting a tab bar with no panels at all — a segmented
 * filter, a view switcher that swaps a route — had to model its
 * choice as a group of visibilities it did not have. `Alert`'s
 * sibling `SegmentedControl` is exactly that consumer, and it now
 * shares this component's core rather than hand-rolling a fourth
 * one.
 * [Decision](../../../../docs/decisions/2026-07-30-tab-selection-is-a-single-picker.md).
 *
 * ### What it does not use, and why that is the right answer
 *
 * The plan expected `createLinkedIds` here as well. It does not
 * fit, and forcing it would have been the wrong call: that kind
 * exists for a **dynamic** trigger↔target pair — a `Popover` whose
 * panel mounts and unmounts, where the multiset is what stops
 * `aria-controls` pointing at a node React has already removed. A
 * tab bar's pairing is static and known at render, so the ids come
 * from one `useUniqueId` and cannot get out of step at all.
 *
 * ### Focus is moved deliberately, and only then
 *
 * `RovingFocus` is state; something still has to call `.focus()`.
 * That happens only while the tablist already contains the focused
 * element — otherwise mounting a tab bar, or any parent re-render
 * that moved `activeValue`, yanks the caret out of whatever the
 * user was actually doing.
 */
export declare const PanelTabs: ({ activation, activeKey, className, label, onChange, orientation, tabs, }: TabsPanelProps) => ReactNode;
//# sourceMappingURL=PanelTabs.d.ts.map