/* ============================================================
   MMH Theme Child — override stylesheet
   Loaded after the parent's mmh-main handle, so these rules win.
   ============================================================

   V20 (v2.29.0) — THE CREAM HERO OVERRIDES ARE GONE. Read this before
   putting anything colour-related back in here.

   Until now this file forced the V14 hero and page-hero scrims with
   `!important`:

       .hero-scrim      { background: <cream gradients> !important }
       .page-hero-band .scrim { background: <cream gradients> !important }
       .hero-grain      { opacity:.12 !important }

   They existed for one reason: to carry the V14 overlay reduction on a
   parent older than v2.8.2, which had not yet baked it in. Every parent
   since v2.8.2 has, so they have been redundant for eleven releases.

   Redundant stopped being harmless at V20. The parent now washes its
   heroes toward #101820 so white headlines stay legible on the black
   site; three `!important` cream gradients loaded after it would have
   put a cream veil back over every hero on the site and taken the
   headlines with them. This is the same failure mode as the stale
   child site-footer.php that masked every parent footer fix — a child
   override that outlived the thing it was written to fix.

   RULE: this child theme carries no colour. If a colour needs changing,
   change it in the parent's assets/css/mmh.css, where the tokens are.
   ============================================================ */

/* Intentionally empty. The file stays so the enqueue in functions.php
   keeps its handle and any future site-specific override has somewhere
   to live that is not the parent. */