/*
 * THE ONE ENTRY POINT — layer order, the tokens and the reset. It paints
 * nothing and carries no `@font-face`; each component ships its own stylesheet
 * beside it, so a component's CSS reaches the browser only if it is bundled.
 *
 * The two statements repeat in every kit sheet on purpose. Layer order is fixed
 * by FIRST APPEARANCE, and nothing constrains which of our files a bundler emits
 * first — an entry importing `@lotics/ui/button` above this file evaluates
 * `button.css` first. A statement naming layers that already exist is a no-op,
 * so repeating it makes that harmless; without it `lotics.components` would
 * register before `lotics.reset` and the reset's `margin: 0` would silently
 * outrank every component rule.
 *
 * `theme` and `base` sit BEFORE `lotics`, `components` and `utilities` after it,
 * so a Tailwind v4 consumer gets utilities on top by cascade order.
 */
@layer theme, base, lotics, components, utilities;
@layer lotics.tokens, lotics.reset, lotics.components;

@import "./tokens.css" layer(lotics.tokens);
@import "./reset.css" layer(lotics.reset);