/* ==========================================================================
   Datastruct Design System — vanilla CSS entry point (no build step)
   ==========================================================================
   There is no utility framework. Templates speak the semantic
   design-system language (ds-* console, mkt-* marketing, docs-* designsys)
   plus Cotton components and a small, frozen set of blessed helpers
   (helpers.css). Spacing/layout come from primitives (ds-row/ds-spread/
   ds-stack/ds-grid) and component molecules, not spacing utilities; a pure
   one-off goes inline via `style=`.

   Cascade-layer architecture. Later layers win, so the order below is the
   contract:

     theme       design tokens (custom properties only)
     base        reset + element defaults
     components  ds-* component classes, layout scaffolding, mkt-* marketing
     helpers     the blessed helper set (override components)
     overrides   cross-cutting guarantees (flatten-inside-cards, motion prefs)

   Notable consequences of the order:
   - helpers override component defaults (a `bg-white` / `text-ds-red`
     helper on an element wins over the component color), and
   - `overrides` beats everything: the flatten-inside-cards rule and the
     hover states of the swap helpers live there, so a static color helper
     on the same element can never pin them down.
   ========================================================================== */

@layer theme, base, components, helpers, overrides;

@import url("./ds/tokens.3f4675dfd7c0.css") layer(theme);
@import url("./ds/base.cdf4db7a3a2d.css") layer(base);
@import url("./ds/layout.2c0dbbe7b2fa.css") layer(components);
@import url("./ds/components.8d4d515cca8c.css") layer(components);
@import url("./ds/marketing.3885527576f7.css") layer(components);
@import url("./ds/content.8e8634ebe2ca.css") layer(components);
@import url("./ds/helpers.cdd2d94c5cc4.css") layer(helpers);
@import url("./ds/overrides.aa46ffcdcbb8.css") layer(overrides);