/**
 * Tag rendering + authoring, shared across features. `TagChips` displays a list of
 * labels as escaped chips (server strings are arbitrary — React escapes every one,
 * never an HTML sink). `TagsInput` is the controlled add/remove editor.
 *
 * A tag is a `tai-chip tai-chip-static`: it reads, it is not a control. The
 * control beside it is the `tai-icon-btn` that removes it, which carries the
 * accessible name ("Remove tag <tag>") because its `CloseIcon` is decorative.
 *
 * These live in the SDK because more than one feature (presets, agents, and the
 * version-history panel's per-version tag editor) needs the same control; a single
 * canonical copy keeps the affordance identical everywhere.
 */
import { type ReactNode } from 'react';
export interface TagChipsProps {
    readonly tags: readonly string[];
}
/** Read-only chips for a list of tags. Renders nothing when there are none. */
export declare function TagChips({ tags }: TagChipsProps): ReactNode;
export interface TagsInputProps {
    readonly value: readonly string[];
    readonly onChange: (next: string[]) => void;
    readonly disabled?: boolean;
    /**
     * The draft input's accessible name when no enclosing `Field` supplies one.
     * Forwarded to the input as a native attribute — see the docblock below.
     */
    readonly 'aria-label'?: string;
    /**
     * The noun for the placeholder + the Add/Remove control names ("tag" by default).
     * Set it (e.g. "badge") so a second editor on the same surface reads and, above
     * all, has DISTINCT accessible control names — two "Add tag" buttons would be
     * ambiguous to a name-based query and a screen reader alike.
     */
    readonly itemNoun?: string;
}
/**
 * Controlled tag editor. The caller owns the `value` list; `onChange` receives the
 * next list on every add/remove. A blank or duplicate entry is ignored (never a
 * silent duplicate chip). Enter or comma commits the draft chip.
 *
 * The draft input is a NATIVE-ATTRIBUTE PASS-THROUGH (the family `inputs.tsx`
 * documents): inside a `Field` it renders the SDK's `TextInput`, which spreads
 * `useFieldControl()` and so claims the Field's control id, taking the Field's
 * visible label as its name; mounted OUTSIDE a `Field` it is named by a caller
 * `aria-label`, which the editor forwards to that same input. Without one a bare
 * editor is unnamed — the published component owns the naming route rather than
 * assuming a `Field` is always present. When a `Field` DOES name it, a caller
 * `aria-label` still has to CONTAIN that visible label (WCAG 2.5.3, Label in
 * Name); `components/field-group.test.ts` enforces that at every call site.
 */
export declare function TagsInput({ value, onChange, disabled, 'aria-label': ariaLabel, itemNoun, }: TagsInputProps): ReactNode;
//# sourceMappingURL=tags.d.ts.map