/*
 * Cascade layer order — MUST be the first stylesheet the browser parses.
 *
 * A layer's priority is fixed by where its name is FIRST declared, not by where its
 * rules land, so declaring the whole order here once makes every later sheet (Vuetify's
 * own layered CSS, Tailwind, the legacy Bootstrap 3 sheets) fall into place regardless
 * of load order. It lives in public/ rather than src/ so it is a plain <link> parsed
 * before anything Vite injects.
 *
 * Layered CSS always loses to UNLAYERED CSS, whatever the specificity. That is why the
 * legacy sheets are pulled into `legacy` (see legacy.css) instead of being left as bare
 * <link>s — unlayered Bootstrap 3 would beat all of Vuetify, including its form controls.
 *
 * Why `legacy` sits BETWEEN vuetify-core and vuetify-components:
 *   - above vuetify-core  -> Bootstrap's reset/base still wins on the pages that are not
 *     migrated yet (TrackingView, ManageView), so they look exactly as they did.
 *   - below vuetify-components -> .v-field, .v-btn, .v-table etc. beat Bootstrap's bare
 *     element selectors (input, button, table), so the migrated pages render correctly.
 */

@layer tailwind-theme;
@layer tailwind-reset;

@layer vuetify-core;

@layer vuetify-components;
@layer vuetify-overrides;
@layer vuetify-utilities;

@layer tailwind-utilities;

@layer vuetify-final;