/*
 * main.css
 *
 * This file previously redefined Tailwind utility class names as if they were
 * bespoke selectors:
 *
 *   .inset-0          { background-image: url("../images/DC-50-2048x1585.jpg") }
 *   .object-cover     { background-image: url("../images/images-3.jpg") }
 *   .bg-gradient-to-t { background-image: url("../images/images-2.jpg") }
 *   .from-neutral-950 { opacity: .07 }
 *   .from-neutral-900 { opacity: .62; filter: blur(2px) }
 *   .bg-cover         { background-image: url(...); opacity: 1 }
 *
 * Those are utility names used all over the templates, so the rules leaked
 * everywhere: stray photos rendered behind any element positioned with
 * inset-0, every object-cover image picked up a background, and the dark
 * gradient overlays were forced down to 7% opacity. Tailwind v4 emits its
 * utilities inside @layer utilities, and unlayered CSS outranks any layer,
 * so these overrode the real utilities regardless of source order.
 *
 * Intentionally left empty. Put genuine custom CSS in theme.css, which is the
 * Tailwind build input, and rebuild with `npm run build:css`.
 */