/*
 * Specisoft platform stylesheet — entry point.
 *
 * Cascade layers exist here for exactly one reason: MudBlazor ships ~600 KB of UNLAYERED CSS,
 * and unlayered rules outrank every layered rule no matter their specificity. Importing it
 * into `mud` puts the whole component library beneath everything this folder authors, which
 * is what lets the rest of these files restyle component chrome with plain selectors instead
 * of the !important pile this replaced.
 *
 * The consequence to respect: for `!important` declarations layer order REVERSES, so a
 * MudBlazor utility class (`pa-4`, `d-flex`, `mb-2`, …) still wins. That is intended — those
 * classes are applied deliberately in markup. Never try to answer one with `!important` from
 * here, because it cannot win. Change the markup instead.
 *
 * The <link> order in App.razor must match the layer order declared below; a layer's position
 * is fixed by this statement, but a file still has to be present for its rules to exist.
 */
@layer mud, spec.tokens, spec.base, spec.chrome, spec.components, spec.utilities;

/* Relative rather than root-relative so a sub-path deployment resolves it the same way. */
@import url("../_content/MudBlazor/MudBlazor.min.css") layer(mud);