/*
 * Phase 4O: kept, name unchanged, after evaluating whether it's still worth having now that
 * Bootstrap/Jobox/Feather/jQuery/Modernizr are all fully retired (Phases 4M/4N). Verdict:
 * yes - this file's actual job was never "contain vendor code" specifically, it's "contain
 * any unlayered CSS that would otherwise incorrectly beat Tailwind's layered utilities" (see
 * the cascade-layers mechanism explained below), and that job is still real: both remaining
 * imports (site.css, Font Awesome) are themselves unlayered files, so removing this wrapper
 * would silently reintroduce the exact bug this phase fixed, just against different files.
 * Renaming the file/layer was considered and declined - `layer(legacy)` still accurately
 * describes "everything that predates this project's own Tailwind-first layering
 * discipline" (both remaining files are pre-existing, not newly authored against this
 * layer model), and a rename would touch this file, its <link> in Pages/_Layout.cshtml, and
 * every doc/comment cross-reference for a purely cosmetic gain - the kind of low-value churn
 * this phase's own brief warns against. See docs/frontend-tailwind.md ("Final CSS
 * compatibility cleanup (Phase 4O)") for the full decision record.
 *
 * Phase 4F (original): wraps every transitional Bootstrap/Jobox/plugin stylesheet in a
 * single named CSS layer ("legacy"), without editing any of the vendored files themselves.
 * See docs/frontend-tailwind.md ("Legacy CSS layer containment (Phase 4F)") for the full
 * writeup - short version below.
 *
 * WHY THIS FILE EXISTS: Phase 4E's own live-browser verification found that Tailwind v4
 * wraps every utility it generates in `@layer properties, theme, base, components, utilities`
 * (confirmed: wwwroot/css/app.generated.css). None of the vendored legacy stylesheets
 * (Bootstrap x2, this project's own site.css, the Jobox theme, jQuery UI/nice-select/etc.)
 * use `@layer` at all - they're all "unlayered". Per the CSS Cascade Layers spec, for
 * normal-priority (non-!important) declarations, ANY unlayered rule beats ANY layered rule
 * REGARDLESS OF SELECTOR SPECIFICITY - so a bare, low-specificity legacy selector like
 * Jobox's `a { color: #05264E; }` was beating Tailwind's own `.text-brand-primary` class,
 * even on fully Tailwind-owned pages. Confirmed via a real browser test
 * (Blazor.UITests/SemanticColorRenderingTests.cs), not guessed.
 *
 * THE FIX: this file's `@import ... layer(legacy);` statements are the FIRST thing the
 * browser encounters in the whole document (this file's own <link> is loaded before
 * app.generated.css in Pages/_Layout.cshtml) - that establishes "legacy" as the lowest-
 * priority layer in the page's overall layer order BEFORE Tailwind's own
 * properties/theme/base/components/utilities layers are declared immediately afterward. Per
 * the same cascade spec, later-declared layers win over earlier ones for normal-priority
 * declarations - so every Tailwind layer now reliably outranks every legacy stylesheet,
 * with zero specificity escalation and zero changes to the vendored files' own contents.
 *
 * WHAT THIS DOES NOT CHANGE: the relative order/behavior of the legacy files AMONG
 * THEMSELVES is untouched (they're listed here in the exact same order they previously
 * appeared as separate <link> tags in _Layout.cshtml) - still-unmigrated, legacy-owned
 * pages keep rendering exactly as before, since nothing about how Bootstrap/site.css/Jobox/
 * the jQuery plugins cascade against EACH OTHER has changed, only how they compare against
 * Tailwind.
 *
 * Do not add a new vendored/legacy stylesheet as a plain <link> in _Layout.cshtml going
 * forward - add its @import here instead, in the same relative position it would have had
 * as a <link>, so it stays inside the "legacy" layer.
 *
 * Phase 4K: removed the imports for bootstrap/bootstrap.min.css (Bootstrap 5.1.0 - fully
 * superseded by the 5.3.0 copy below, confirmed a strict selector subset in Phase 4H/4J),
 * flaticon.css, animate.min.css, magnific-popup.min.css, owl.carousel.min.css, and
 * nice-select.min.css - Phase 4J's read-only audit confirmed zero live selector targets
 * for any of them anywhere in the app.
 *
 * Phase 4M: removed the imports for bootstrap.min.css (5.3.0), feather.min.css, and
 * style.css (the Jobox theme) - `Dashboard.razor`'s Phase 4L redesign removed the last
 * live class-name consumer of all three, confirmed via a repo-wide re-scan immediately
 * before deleting anything (not assumed from the Phase 4L report alone). The global
 * `box-sizing: border-box` reset (and a handful of other base-tag defaults) these two
 * files silently provided - Preflight is still deliberately disabled - now lives as an
 * explicit, narrow, first-party rule set in Styles/base.css instead. See
 * docs/frontend-tailwind.md, "Retiring Bootstrap/Jobox/Feather (Phase 4M)", for the full
 * evidence trail. The two remaining imports below are the only ones still confirmed live:
 * site.css (`#blazor-error-ui`/`.blazor-error-boundary`/`.invalid` - see that phase's
 * section on `site.css`'s remaining responsibilities) and all-fontawesome.min.css (every
 * Tailwind-owned page's icons, not just legacy pages - a permanent product dependency,
 * not legacy debt, see Phase 4H/4J).
 */

@import url("site.css") layer(legacy);
@import url("../assets/css/all-fontawesome.min.css") layer(legacy);
