import { type ReactNode } from 'react';
/**
 * Peek's Field (2026-08-28): a label over a control, 8px apart, with a red
 * asterisk when required. The label is the `input-label` type token, merged
 * with `cn()` like every other class list here. On Base UI's `Field` since
 * stage 3 of the migration (2026-09-07).
 *
 * The label names its control. It did not once, and the control was a
 * *sibling* of the label with no `htmlFor`, so there was neither an explicit
 * nor an implicit association: a screen reader announced an unlabelled edit
 * box and clicking the label focused nothing (SHA-17). That fix used to be
 * ours — a context carrying a generated id, which every control had to opt
 * into by calling `useFieldControlId`. **Base UI does it now**, for its own
 * `Input`, `Checkbox`, `Select` and anything rendered through `Field.Control`,
 * so a new control is labelled by construction rather than by remembering.
 *
 * `helper` and `error` are the line under the control, which Ship built by
 * hand in two dialogs (`COMPONENTS-SHIP.md` F14) and Peek in four
 * (`COMPONENTS-PEEK.md` F14), always the same two class lists. **An error
 * replaces the helper rather than joining it** — that is what those callers
 * did (`pairError ?? 'Leave empty and…'`), and a field that says both at once
 * is asking the reader to work out which one is live.
 *
 * The line is announced: Base UI wires `aria-describedby` for the helper and
 * `aria-invalid` + the error's id for the error, which the hand-built spans
 * never did.
 *
 * `required` is announced too, since 2026-09-08. It drew the asterisk and
 * nothing else — measured, the control carried neither `required` nor
 * `aria-required`, so the one thing the mark means never reached anybody who
 * could not see it. Base UI's `Field` has no `required` of its own, so this
 * puts `aria-required` on the control itself.
 */
export interface FieldProps {
    label: string;
    /**
     * Draws the asterisk **and** marks the control `aria-required`, so the mark
     * means something to a reader who cannot see it. It reaches a single control
     * element; a `children` of several elements keeps the asterisk and owes its
     * own `aria-required`.
     */
    required?: boolean;
    /**
     * A hint under the control — what the format is, what happens if it is left
     * empty. `caption`, muted. Hidden while `error` is set.
     */
    helper?: string;
    /**
     * What is wrong, in the same place as the helper and in the error colour.
     * Setting it also marks the control invalid, so the caller no longer passes
     * `aria-invalid` itself.
     */
    error?: string;
    children: ReactNode;
}
export declare function Field({ label, required, helper, error, children }: FieldProps): import("react").JSX.Element;
/**
 * The line on its own — the same small line `Field` draws under a control,
 * for the places where there is no single control to draw it under.
 *
 * **Why it is not a `Field`.** Three surfaces in Peek put this line under a
 * *group*: the rename row (a field and two buttons), a Folder's action
 * controls, another app's action controls. Each already has a section heading
 * above it, and `Field` comes with a label of its own — so wrapping the group
 * in one would either say the heading twice or restyle it. Found at step 4 of
 * Peek's adoption (`ADOPTION.md` B24); until this existed, all three spelled
 * `text-xs text-error-default` by hand.
 *
 * **It announces itself**, which is the half the hand-written spans never had.
 * These lines appear *after* something was done — a rename that the relay
 * refused, an action that failed — so a reader who cannot see them is told:
 * `role="alert"` for an error, `role="status"` for the rest. That is `Banner`'s
 * rule (2026-09-02), kept here so the two agree.
 *
 * **`warning` is the tone `Field` has not got**, and deliberately: `Field`'s
 * `error` also marks its control invalid, and a warning is not invalid — the
 * rename went through, and something about it needs saying. A group has no
 * single control to mark, so the distinction is free here and would not be
 * there.
 *
 * When the line belongs to one control, it is `Field`'s `helper` or `error`:
 * those are wired to the control with `aria-describedby` and `aria-invalid`,
 * which this cannot be.
 */
export type FieldLineTone = 'helper' | 'warning' | 'error';
export interface FieldLineProps {
    /** `helper` (muted) is a hint; `warning` (amber) and `error` (red) are outcomes. Default `helper`. */
    tone?: FieldLineTone;
    children: ReactNode;
    className?: string;
}
export declare function FieldLine({ tone, children, className }: FieldLineProps): import("react").JSX.Element;
//# sourceMappingURL=Field.d.ts.map