/**
* The one required-field marker every labelled form control in this library renders.
*
* Before this sheet existed the same three declarations were copy-pasted into fourteen component
* stylesheets (and hand-rolled a third way, as a literal `<span>` in three templates), which had
* already drifted: several controls that accept `required` and render a `form-control-label` part
* shipped no marker at all. Just as importantly, a hardcoded `content: ' *'` is a dead end for a
* consumer — a form that marks its *optional* fields instead, or a locale that prefers a word to a
* glyph, has nowhere to say so, and the colour cannot be retuned without also moving every other
* danger-coloured surface in the page.
*
* Three consumer-settable custom properties replace that, each consumed through an inline `var()`
* fallback so the default needs no `:host` declaration and no token registration:
*
* - `--lr-form-control-required-content` — the marker itself. Defaults to `' *'` (the leading space
*   is part of the glyph, so an unset offset still reads correctly). Set it to `''` to suppress the
*   marker entirely, or to any other quoted string (`' (required)'`, `' ٭'`, a localized word) to
*   replace it. Caller-supplied content, so it is never localized here.
* - `--lr-form-control-required-color` — the marker colour, defaulting to `--lr-color-danger` so an
*   unset control looks exactly as it did before. Independently themeable: retuning it does not
*   touch error text, invalid borders, or any other danger surface.
* - `--lr-form-control-required-offset` — inline space between the label text and the marker,
*   defaulting to `0` (the glyph's own leading space is the historical spacing).
*
* Two selectors, because the library has exactly two required-marker shapes:
*
* - `:host([required]) [part~='form-control-label']::after` — the standard labelled control, where
*   the whole host is the required field. `~=` rather than `=` because several components render
*   the part alongside a second token (`part="label form-control-label"`).
* - `[part='field'][data-required] [part='label']::after` — a composite form that renders many
*   fields inside one host (`<lr-tool-param-form>`), where "required" is per field and the host has
*   no `required` attribute of its own.
*
* Adopt it by interpolating this sheet into the component's own `css` template rather than by
* appending it to `static styles`: the marker belongs to the stylesheet that owns the label part,
* and keeping the composition there means a component's whole rendered surface stays readable in
* one file.
*/
export declare const formControlRequiredMarker:import("lit").CSSResult;
/**
* The one focus halo every field-shaped form control in this library can paint.
*
* `lr-input`, `lr-textarea`, `lr-select`, `lr-combobox`, `lr-locale-picker`, `lr-date-input`,
* `lr-file-input`, `lr-phone-input`, `lr-token-input` and `lr-time-input` each already answer focus
* with an outline or a brand border, and that stays: the outline is the accessibility contract
* (WCAG 2.4.7), not decoration, and nothing here replaces or removes it. What none of them had was
* a way to add the soft ring a design system usually draws *outside* that edge. Writing one meant a
* `::part()` rule per control, per state, and keeping ten of them in step by hand.
*
* `lr-otp-input` is the one field-shaped control deliberately left out, and the reason is mechanical
* rather than editorial: its focused segment already paints
* `box-shadow: 0 0 0 var(--lr-focus-ring-width) …` as its focus ring. `box-shadow` is a single
* property, so a declaration-only partial would REPLACE that ring rather than sit outside it.
* Haloing that control means composing both shadows into one value, which is a change to its focus
* treatment rather than an adoption of this one.
*
* `--lr-form-control-focus-shadow` is that one knob. It defaults to `none`, so an unset control
* renders exactly as it did before, and it sits in the same `--lr-form-control-*` family as the
* shared size ladder — the vocabulary a consumer already reaches for when retuning every field at
* once.
*
* Adoption is two lines, and the split between them is deliberate:
*
* 1. the adopting stylesheet resolves the public name into the private one on its own `:host`,
*    `--_lr-form-control-focus-shadow: var(--lr-form-control-focus-shadow, none);`
* 2. every rule that marks this control focused (or open) interpolates this sheet.
*
* Step 1 lives in the adopting component rather than here on purpose. Twenty-two components compose
* this file for the required marker, and a `var(--lr-form-control-focus-shadow…)` read in *this*
* file would make every one of them advertise the hook in `custom-elements.json` and in the editor
* data — including the twelve that never paint a field surface and would honour nothing. A hook is
* advertised where it works. The private property keeps the paint itself in one place, so the ten
* controls that do adopt it cannot drift apart.
*
* Declaring the private on `:host` also leaves the public name undeclared everywhere, which is what
* keeps it a real cascade point: one declaration on `:root`, or on any ancestor to scope it to a
* subtree, reaches every adopting control inside it.
*/
export declare const formControlFocusHalo:import("lit").CSSResult;