/**
 * The two built-in hero themes — HeroUI's default light/dark palettes mapped
 * onto the shared `ColorToken` contract and registered into
 * `@sigx/lynx-zero`'s theme registry at module load.
 *
 * Token mapping from upstream HeroUI semantics (the pilot's validation of the
 * contract — see signalxjs/lynx#219):
 *
 *   danger          → error
 *   default         → neutral
 *   background      → base-100
 *   content2/3      → base-200 / base-300
 *   foreground      → base-content
 *   accent / info   → no upstream equivalent; hero ships its cyan + blue-400
 *
 * Both are marked `staticCss`: `scripts/gen-theme-css.mjs` turns this same data
 * into `.hero-<name>` stylesheet rules (plus their
 * `@media (prefers-color-scheme: …)` twins) at build time, so the CSS engine
 * resolves a built-in palette and `<ThemeProvider>` declares nothing inline for
 * it (#985). Runtime-registered themes keep the inline path (#116).
 *
 * HeroUI's default roundness is larger than daisy's — expressed via the
 * theme-level `radius` overrides (the engine emits them with the palette).
 */
import { type Theme } from '@sigx/lynx-zero/registry';
/**
 * Theme class applied to the provider's host view. The two built-ins get
 * autocomplete; arbitrary strings are accepted for custom registered themes.
 */
export type HeroTheme = 'hero-light' | 'hero-dark' | (string & {});
export declare const HERO_BUILTIN_THEMES: readonly Theme[];
//# sourceMappingURL=builtins.d.ts.map