/*
 * TEMP workaround (Nuxt 4 + Vuetify 4):
 * Declare cascade layer order early in <head> before Vuetify's auto-injected
 * styles. Without this, layered rules may be evaluated in an unexpected order.
 *
 * Keep vuetify-utilities.helpers after vuetify-utilities.typography so helper
 * classes such as .font-weight-bold win consistently in production builds.
 *
 * uno-typography is placed BEFORE vuetify-core on purpose: explicit utilities
 * and behavioral overrides (the `overrides` layer — e.g. the heading-anchor `#`)
 * must win over the prose preset. This is safe because Vuetify 4 ships NO bare
 * element rules for a/p/ul/ol/li/code/blockquote/etc. (only html/body/inputs),
 * so reset/base have nothing that can clobber prose typography — including the
 * inline-code chip, which the typography preset now owns (prose/Code.vue renders
 * a plain <code>; the chip styling lives in nuxt.config's presetTypography).
 *
 * Refs:
 * https://github.com/vuetifyjs/vuetify/issues/22656
 * https://github.com/vuetifyjs/vuetify/issues/22752
 */
@layer uno-base, uno-theme, uno-typography, vuetify-core.reset, vuetify-core.base, vuetify-components, vuetify-overrides, overrides, vuetify-utilities, uno-shortcuts, uno-default, utilities, vuetify-final;

@layer vuetify-utilities {
  @layer theme-base, typography, helpers, theme-background, theme-foreground;
}
