/**
 * Canonical CSS @layer priority order for the whole minCore stack.
 *
 * WHY this file exists (Menu-SSoT OFFEN-9, 2026-08-21):
 * Per the CSS Cascade Layers spec, a layer's priority is fixed by the FIRST
 * time its name is encountered in the document — a later `@layer name-list;`
 * statement does NOT reorder names that are already known, it only assigns a
 * position to names it sees for the first time. Content Block assets
 * (`<mincore:asset.css>` / `AssetPublisher`) are published and loaded while
 * content is rendered, i.e. BEFORE the mandant CSS bundle, which only
 * declares this same order statement inside its own `style.css` and loads
 * LAST in `<head>`. Each Content Block wraps its rules in `@layer components`
 * (or, for min_navmain, the CB-local `@layer min-navmain`) without ever
 * declaring the full order — so those two layer names get "first encountered"
 * at the bottom of the whole cascade, below even `reset`, and lose every
 * property collision against reset/base rules regardless of selector
 * specificity (verified via Chromium CSSOM introspection, see
 * A5-A7-report.md §Auflage 5).
 *
 * This file is loaded first (`page.includeCSS` + `forceOnTop = 1`, see
 * Configuration/Sets/MinCore/setup.typoscript) and does nothing except fix
 * the layer priority order once, for every page, before any Content Block or
 * mandant bundle CSS can claim a name for itself. It contains no selectors
 * and styles nothing on its own.
 *
 * `min-navmain` is included here (not merged into `components`) because
 * ContentBlocks/ContentElements/min_navmain/assets/frontend.css uses its own
 * layer name instead of `components` like all other 19 `@layer`-based
 * Content Blocks; renaming that CB's CSS would be a second, unrelated change
 * with its own blast radius, so the smallest clean fix is to give the
 * existing name an explicit, correct position instead. It sits directly
 * next to `components` (same "single Content Block" priority tier, verified
 * to have zero colliding class selectors against the other component-layer
 * Content Blocks) so it is protected against `reset`/`base`/`layout` the
 * same way every other Content Block already is.
 */
@layer reset, tokens, base, layout, components, min-navmain, modules, utilities, mandant;
