/* * @file aimeat-daisyui-bridge.css * @author Jouni Miikki * SPDX-License-Identifier: MIT * @description Theme-compat layer so the bundled cortex UI libraries cohere with daisyUI. * (0) Pulls in the AIMEAT daisyUI theme (aimeat-theme.css) so any app already loading this * bridge gets the house palette — coral primary, the designed dark surface ramp and * correct `-content` pairs — without editing the app. Before this, `--color-primary` was * daisyUI's indigo and every branded app hardcoded `#E8564A` by hand. * (1) Maps AIMEAT theme.css variable NAMES to daisyUI 5 theme variables so libs that read * --text / --bg-card / --accent / … follow a daisyUI app's `data-theme` automatically. * (2) Dark-mode polish: a few cortex components hardcode LIGHT colors (no var) — alerts, * badges, table zebra — so the var-mapping can't reach them. We override those with * theme-aware tints (`:root .aui-*` wins on specificity). No changes to the libraries. * Load this AFTER the daisyUI stylesheet. Hardcoded fallbacks keep it working if daisyUI * vars are absent. * * NOTE on daisyUI's OWN components: they are not overridden here. With the theme loaded they * are already theme-correct, and daisyUI 5 ships the quiet variants an app usually wants — * `badge-soft`, `alert-soft`, `btn-soft`, `card-border`. Reach for those instead of a solid * `badge-warning`, which is a loud block of amber on a dark page even when it is legible. * @usage * * @version-history * v1.4.0 — 2026-09-13 — The hidden attribute hides again. daisyUI's component classes (.card, * .stats and the rest) set `display`, which beats the browser's own [hidden] rule, so an element * carrying `hidden` stayed on screen. Tailwind's preflight brings the fix, but only after the JIT * has compiled, and never on a page that loads daisyUI without the JIT. The bridge now carries * preflight's rule itself, so it holds from first paint. Measured in Chromium: a hidden .card * computed `display: flex` before and `none` after (appdev pitfall * daisyui-component-defeats-hidden-attribute). * v1.3.0 — 2026-07-25 — FIX the --border collision: the bridge mapped --border to a COLOUR at * :root for the aui-* cortex components, while daisyUI 5 uses the same name as a border WIDTH * inside calc() on nearly every component — the invalid calc collapsed badge/input paddings to * 0 and toggles to slivers on every bridge-loading page since v1.0.0. The colour mapping is now * scoped to aui-* elements, with a --border-w restore for daisyUI components nested inside. * v1.2.0 — 2026-07-25 — @import the AIMEAT daisyUI theme, so the house palette reaches every * app that already loads the bridge. Contrast + surface ramp verified by * `pnpm check:theme` (tools/theme-contrast.ts). * v1.1.0 — 2026-06-26 — Map --bg-surface-dim (table zebra) + theme-aware alert/badge tints. * v1.0.0 — 2026-06-26 — Initial bridge (cortex libs follow daisyUI theme). */ /* MUST be the first rule: @import is only valid ahead of ordinary rules. Same-origin, cached alongside this file, and a no-op duplicate when the app also links the theme directly. */ @import url('/lib/aimeat-theme.css'); /* ── HIDDEN MEANS HIDDEN. Every daisyUI component class sets its own `display`, and an author rule with a display beats the browser's [hidden] rule, so `