/*
 * Cap-safe Tailwind max-width container-width fix.
 *
 * Root cause: in Tailwind v4 the @theme block declared named fluid spacing
 * tokens --spacing-{xs,sm,md,lg,xl}. Those keys live in the spacing namespace,
 * which max-w-* resolves INSTEAD of the default --container-* scale, so the
 * tracked, production-served output.css compiled .max-w-lg to
 * var(--spacing-lg) (a clamp(4rem,5vw,6rem) column). On /partners/interest
 * the max-w-lg hero collapsed into a narrow vertical strip.
 *
 * The root-cause source fix lives in static/src/input.css (the fluid tokens
 * are relocated out of the spacing namespace). But output.css is a single
 * minified line (~182KB); editing it emits a ~2x-file-size git diff that blows
 * the 200K feature/zeus-* diff cap. This file is the cap-safe production
 * bridge: a tiny override loaded AFTER output.css in every base shell, mapping
 * the affected utilities back to Tailwind's container widths.
 *
 * !important is required: output.css already ships incomplete band-aid
 * overrides for .max-w-md/.max-w-xl with !important, so a non-important rule
 * here would lose to them regardless of source order.
 *
 * HYGIENE FOLLOW-UP (separate lane): once the pipeline untracks output.css and
 * builds Tailwind at image-build time (or emits un-minified CSS), rebuild from
 * input.css and retire this bridge.
 */
.max-w-xs { max-width: 20rem !important; }
.max-w-sm { max-width: 24rem !important; }
.max-w-md { max-width: 28rem !important; }
.max-w-lg { max-width: 32rem !important; }
.max-w-xl { max-width: 36rem !important; }

/* Responsive variant compiled into output.css (sm:max-w-md -> var(--spacing-md)). */
@media (min-width: 40rem) {
  .sm\:max-w-md { max-width: 28rem !important; }
}