/* Core neutraliser — DECLARED differences from core, so the ported pages render on
 * the baseline ministrycatalysts.com was built on (WordPress + Divi 4.27), not on
 * core's Tailwind preflight and demo-theme body. Same mechanism as Andrea Bertoli
 * and SAPient (~/clients/andrea-bertoli/site/src/features/andrea-bertoli/css).
 *
 * 1. Tailwind preflight lives in @layer base; this rule sits in the same layer and
 *    rolls every property back past it with `revert-layer`. Unlayered CSS (10-wp.css,
 *    20-port.css) still wins; core blocks' utilities are untouched.
 * 2. Core's body colours/font and film grain, which the site never had.
 * `data-mc-chrome` is on the header, so none of this reaches /admin.
 */
@layer base {
  :root:has([data-mc-chrome]),
  :root:has([data-mc-chrome]) *,
  :root:has([data-mc-chrome]) ::before,
  :root:has([data-mc-chrome]) ::after,
  :root:has([data-mc-chrome]) ::marker,
  :root:has([data-mc-chrome]) ::placeholder,
  :root:has([data-mc-chrome]) ::backdrop,
  :root:has([data-mc-chrome]) ::file-selector-button {
    all: revert-layer;
  }
}

:where(:root:has([data-mc-chrome])) {
  --grain-opacity: 0;
  font-size: 100%;
}
:where(:root:has([data-mc-chrome])) .grain::after {
  content: none;
}
/* Divi's body: white page, #666 text (its own rules in 10-wp.css set the rest). */
:where(:root:has([data-mc-chrome])) body {
  background: #fff;
  color: #666;
}