/* Hand-written overrides for this migration — client-aandgirrigation.
 *
 * DELIBERATELY OUTSIDE site/public/styles/ (gotcha 49): tools/port-css.mjs owns that
 * directory and clears its own hashed outputs on every run, so a hand-written sheet
 * placed there is deleted by the next port with no error anywhere — on one site that
 * silently removed the sheet that hides the inactive device bands, and all three
 * headers then rendered at every width.
 *
 * EVERY NUMBER BELOW MUST BE CENSUSED ON THIS SITE. That sentence is here because this
 * file has now arrived describing the wrong repo TWICE in this chain — once from two
 * generations back, whose structural section described the CLASSIC Duda template
 * (StandardLayoutMultiD / Hamburger / mobileHamburgerLayout) on a site that is FLEX, and
 * again into this repo carrying the previous FLEX site's own measurements. A number in a
 * hand-written sheet is exactly the residue gotcha 63 says survives a copy still looking
 * correct, so every figure below is re-derived here rather than inherited.
 * The RULES were sound and are kept; every measurement around them is re-taken.
 *
 * Population, DERIVED and not typed: pages.txt holds 59 paths — 44 static plus the 15
 * blog posts generated/blog.rss declares as <item>s — so 177 captures (59 pages x 3
 * bands) plus all 59 raw served documents. Re-derive from those two files rather than
 * from this line; a count copied out of a comment is what produced every wrong number
 * this header is about.
 *
 * Keep this file minimal. Anything that can come from the ported cascade should.
 */

/* The honeypot. Positioned off-screen rather than display:none — bots skip obviously
 * hidden fields, and taking it out of flow means it costs no layout, which the pixel
 * gate would otherwise measure. Live has NO honeypot on either of this site's two
 * forms, so this is ours and must cost nothing.
 *
 * /migration phase 8 specifies exactly this and one fleet repo shipped the spec
 * unimplemented — its honeypot rendered as an ordinary 40px text field and read as a
 * 46px layout defect. */
.mg-hp {
  position: absolute !important;
  left: -9999px !important;
  top: auto !important;
  width: 1px !important;
  height: 1px !important;
  overflow: hidden !important;
}

/* SPECIFICITY NOTE — read before editing any rule below.
 *
 * Duda emits a per-widget rule for EVERY widget on the site, shaped
 *
 *     #dm .dmBody div.u_1213107879 { display: block !important }
 *
 * That is (1,2,1) and it is `!important`. A hide written as a plain
 * `.mg-only-t { display:none !important }` is (0,1,0), so with `!important` on both
 * sides SPECIFICITY decides and Duda's rule wins — the element stays visible and
 * nothing in the console says so.
 *
 * So every gate below repeats its class three times behind `#dm`, giving (1,3,0),
 * which outranks (1,2,1) on class count without relying on source order. Do not
 * "tidy" the repetition away.
 */

/* ---------------------------------------------------------------------------
 * BLOG PAGINATION — ONE REAL CONTROL, ON ONE PAGE.
 *
 * Censused on the raw served html of all 38 pages (the pages.txt population) and
 * confirmed by driving live's own control. The blog-widget record count is DERIVED,
 * not typed: generated/blog-widgets.json covers /blog plus the 15 posts
 * generated/blog.rss declares — 20 blog-list pages x 3 bands = 60 records:
 *
 *   /blog             declared 19, visible 10   NUMBERED PAGER, REPLACES
 *                     <nav class="pagination-nav"> x1,
 *                     more-posts-text-container x0 (zero on all 38 pages).
 *                     data-paginate-total-elements=19, page size 10; its links carry
 *                     data-page and data-action="paginate" and SWAP the visible set
 *                     rather than appending to it. It is the only page on which the
 *                     live driver finds a control at all, which is that run's own
 *                     positive control.
 *
 *   19 blog posts     declared 18, visible 15   NO CONTROL AT ALL
 *                     pagination-nav x0, more-posts-text-container x0. LIVE ITSELF
 *                     strands the other three — recorded per post in
 *                     blog-widgets.json as shape "none", steps [15]. So there is
 *                     nothing to reveal there and nothing to hide; the rule below
 *                     has no subject on those 19 pages.
 *
 * The numbered pagination-nav IS this site's shape and it is on /blog alone; the
 * "show more / appends" shape the inherited file described has no instance here.
 *
 * blog.rss independently declares 19 items, which is the cross-check that makes a
 * truncated /blog fail rather than ship quietly, and the alias set driven out of
 * /blog equals it exactly in both directions — 19 = 19, empty each way.
 *
 * A static build has no Duda backend, so every card ships and the ones past the
 * first page are stamped mg-blog-hidden with data-mg-blog-page; runtime.js reveals
 * them in live's own page size of 10, replacing the visible set rather than
 * appending to it. This rule is what hides them initially — 19 declared minus the 10
 * page one shows = 9 cards, on the one page that has a control.
 * ------------------------------------------------------------------------- */
#dm .mg-blog-hidden.mg-blog-hidden.mg-blog-hidden {
  display: none !important;
}

/* display:none DOES NOT CHANGE CHILD INDICES, so shipping the withheld cards
 * silently moves which card is :last-child — gotcha 69.
 *
 * Duda's own rule is `.postArticle:not(:last-child){padding-bottom:Npx}`. On live the
 * last VISIBLE card is genuinely :last-child and takes none of it. In our build it is
 * followed by hidden siblings, so it stops matching and GAINS that padding, pushing
 * the control and the whole footer down by a constant amount — the signature of one
 * shared element rather than a per-page fault.
 *
 * *** MEASURED ON THIS SITE, AND IT IS ARMED HERE — 30px, ON EXACTLY ONE CARD. ***
 * The comment this file arrived with said the rule was "currently inert here" because
 * every `:not(:last-child)` padding rule in THAT site's cascade was scoped
 * `[list-layout=recent_posts]` and its layouts did not match. That was a true
 * measurement of a previous client and is false here, which is exactly why an
 * inherited "this does not apply" is worth re-measuring: the matching rule on this
 * site is
 *
 *   #dm [blog-posts-feature-flag=true][list-layout=recent_posts][posts-padding="15"]
 *       .postArticle:not(:last-child){padding-bottom:30px}
 *
 * Every blog POST carries TWO related-posts widgets. Measured per widget with
 * EFFECTIVE visibility (tools/probe-blog-padding2.mjs — a per-element display test is
 * not enough, because a card can be display:block inside a display:none band copy):
 *
 *   live  widget0  5 cards  pad [30,30,30,30, 0]  sum 120
 *   build widget0  5 shown  pad [30,30,30,30,30]  sum 150   <- +30, the whole defect
 *   both  widget1 10 cards  pad [0 x10]           sum   0   (no padding rule matches)
 *
 * That +30 is the gate's dH on all 15 posts at 375 and 768, to the pixel.
 *
 * *** AND THE OVERRIDE BELOW WAS ALREADY PRESENT AND ALREADY MATCHING — IT LOST THE
 * SPECIFICITY FIGHT, WHICH IS THE FAILURE THAT LOOKS LIKE THE RULE NOT BEING THERE.
 * The selector matched (the last visible card's nextElementSibling really is
 * `.postArticle.mg-blog-hidden`), and the card still computed 30px. Counting:
 *
 *   ours   #dm + .postArticle + :not(.mg-blog-hidden) + :has(.postArticle.mg-blog-hidden)
 *          = (1,4,0)   — :has() takes the specificity of its most specific argument
 *   Duda's #dm + 3 attribute selectors + .postArticle + :not(:last-child)
 *          = (1,5,0)   — and it carries NO !important
 *
 * (1,5,0) beats (1,4,0), so the override was outranked and silently did nothing.
 * `!important` is what settles it, because Duda's rule here is not !important — this
 * is gotcha 70's specificity trap and the "a pixel count identical across runs means
 * the fix never took effect" rule arriving together.
 *
 * Keyed on `:has(+ .mg-blog-hidden)` rather than on a stamped class, because that
 * tracks the SEQUENCE as batches are revealed instead of pinning the initial state;
 * runtime.js does not have to re-stamp anything. */
#dm .postArticle:not(.mg-blog-hidden):has(+ .postArticle.mg-blog-hidden) {
  padding-bottom: 0 !important;
}

/* ---------------------------------------------------------------------------
 * PER-DEVICE WIDGET FORKS.
 *
 * THIS SITE IS DUDA **FLEX**, AND ON FLEX THE CHROME DOES NOT FORK — GOTCHA 5 IS
 * INVERTED. Measured over generated/served-by-device (177 documents, 59 paths x 3
 * device UAs, all 200):
 *
 *   dmtemplateid    FlexHeader on ALL THREE BANDS, all 59 pages
 *   <body> class    `dmRoot fix-mobile-scrolling flex-site dmResellerSite`,
 *                   BYTE-IDENTICAL on all three bands, all 59 pages
 *   data-flex-site  present on all three bands, all 59 pages
 *
 * So dmtemplateid CANNOT discriminate the fork here, and gotcha 48/88's
 * dmDesktopBody / dmTabletBody / dmMobileBody classes DO NOT EXIST on this platform.
 * The inherited header asserted three distinct dmtemplateid values across the bands;
 * that is the classic template and it is false here.
 *
 * THE CONTENT FORK IS STILL THREE-WAY, and it is measured on the served BYTES rather
 * than inferred from the template: desktop == tablet on 0 of 59, desktop == mobile on
 * 0 of 59, tablet == mobile on 0 of 59. Tag counts differ across bands on 34 of the 59.
 * generated/served-fork.json inspected 177 of 177 subjects with 0 missing, and its own
 * overlap check found the two independent desktop fetches 59 of 59 byte-identical.
 *
 * THE TABLET DECLARES ITS OWN CANVAS. <meta name="viewport" content="width=960px"> on
 * 59 of 59 tablet captures, against device-width on desktop and mobile. So gotcha 3's
 * 960 canvas DOES apply here — measured, not carried: gotcha 62 exists because that
 * value is a common default and not a platform constant.
 *
 * THE `mg-only-t` GATE THEREFORE CARRIES A CONTENT FORK, NOT A CHROME FORK. The header,
 * drawer and overlay are one shape on every band (#dmFlexHeaderContainer, #flex-header,
 * one #hamburger-drawer, one #layout-drawer-overlay); what differs per band is the page
 * content. THE OCCURRENCE COUNT IS NOT QUOTED because it is not yet measurable —
 * site/src/pages is empty and no page has been built — and an inherited figure here
 * would be a count of another client's build.
 *
 * THE BAND BOUNDARIES ARE DUDA'S OWN, RE-COUNTED ON THIS SITE. The media queries the
 * captured cascade actually contains, over all 383 sheets in generated/live/css:
 *
 *     max-width: 767px   x157      min-width: 768px   x106
 *     max-width: 1024px  x15       min-width: 1025px  x54
 *     min-width: 0px     x29
 *
 * 1025 is therefore the desktop edge on Duda's own declarations rather than by assuming
 * 1024+1. (The inherited counts were 136/92/65/64 over 202 sheets — a different site.)
 *
 * NOT TAKEN ON THIS SITE, AND RECORDED AS MISSING RATHER THAN INHERITED: a live drawer
 * ratio sweep across many widths. The inherited copy carried a 12-width sweep from
 * a previous client (40vw for #hamburger-drawer, 85vw for #mobile-hamburger-drawer
 * at 375). NOT ONE of those numbers is this site's — that site forked two ways with no
 * 960 tablet canvas and used two DIFFERENT drawer elements, while this site has ONE
 * #hamburger-drawer on every band — so they are deleted rather than renumbered. Re-take
 * before quoting a behavioural edge, and mind the UA trap (gotcha 66): Duda picks its
 * document by USER-AGENT, so a desktop UA at a narrow viewport gets the DESKTOP document
 * and reads the wrong element.
 *
 * So, on (a) alone: mobile <=767, tablet 768-1024, desktop >=1025.
 *
 * These hide rather than remove, deliberately — the elements stay in the document so
 * the runtime can still address them, and display:none costs no layout.
 *
 * Only the INACTIVE bands are hidden, inside the media queries. The active band is
 * never touched, so it keeps whatever `display` the ported cascade gives it — hiding
 * all three and restoring one with `display: revert` reverts past the author cascade
 * to the UA default and replaces the widget's real display value with a plain block.
 * ------------------------------------------------------------------------- */
@media (max-width: 767px) {
  #dm .mg-only-d.mg-only-d.mg-only-d,
  #dm .mg-only-t.mg-only-t.mg-only-t {
    display: none !important;
  }
}

@media (min-width: 768px) and (max-width: 1024px) {
  #dm .mg-only-d.mg-only-d.mg-only-d,
  #dm .mg-only-m.mg-only-m.mg-only-m {
    display: none !important;
  }
}

@media (min-width: 1025px) {
  #dm .mg-only-t.mg-only-t.mg-only-t,
  #dm .mg-only-m.mg-only-m.mg-only-m {
    display: none !important;
  }
}

/* ---------------------------------------------------------------------------
 * SLIDERS: TWO WIDGETS ON ONE PAGE, AND THEY DO MOVE. NO RULE IS NEEDED HERE.
 *
 * RE-CENSUSED ON THIS SITE, and the inherited section described the opposite site.
 * That copy asserted 9 single-slide roots across 9 pages with isAutoPlay:false and
 * isFade:true — "nothing to advance to, no arrows to bind" — which is
 * a previous client's shape, not this one.
 *
 * Measured over the 59 served documents: `ssrimageslider` occurs on exactly ONE page,
 * the home page, 6 occurrences. tools/derive-slider-config.mjs reads each widget's own
 * declared autoPagination config and finds TWO widgets, both:
 *
 *     autoPlay=true   interval=7s   pauseOnHover=false   animation=slide
 *
 * So this site's sliders DO auto-advance, on a 7-second interval, and the interval is
 * read from each widget's own payload rather than from runtime.js's inherited constant
 * (gotcha 90: every widget parameter comes from that page's own config, never from the
 * site the driver was written against).
 *
 * TWO CONSEQUENCES FOR THE GATE, both of them the reason this is written down:
 *
 *   (a) An auto-advancing slider can never diff to zero — the two captures land on
 *       different slides — so the home page's slider region is a legitimate --hide
 *       candidate, and whatever is hidden needs a per-element check that asserts
 *       MOTION, because motion is exactly what hiding removes.
 *   (b) The shared check-slider.mjs asserts on `.flexslider` roots, of which this site
 *       has ZERO. It will FATAL on an empty population. That refusal is honest about
 *       ITS subject and says nothing about this site's sliders — "no FlexSlider" must
 *       not be written up as "no sliders".
 *
 * NOT YET VERIFIED ON THE SERVED BUILD — nothing has been built yet (site/src/pages is
 * empty). The population any such run must cover is DERIVED from the census above and
 * not typed: 2 roots on 1 page, x 3 widths.
 * ------------------------------------------------------------------------- */

/* ---------------------------------------------------------------------------
 * ACCORDION OPEN STATE — recovering a rule the live CSS read cannot see.
 *
 * RE-CENSUSED ON THIS SITE: 23 accordion widgets on 23 of 25 pages, exactly one per
 * page. The inherited section described 34 widgets on 33 of 38
 * pages from 15 distinct ids with a 19/15 firstExpanded split, and named /faq,
 * /request-a-quote and /service-areas — none of which exist here. All of it is
 * a previous client's and is deleted rather than renumbered.
 *
 * THIS SITE, from generated/accordion-config.json (derived from live's own
 * initiateWidget({"type":"SSR_ACCORDION"}) payloads, 0 failing to parse) and
 * corroborated against a `ssraccordion` census of the served html:
 *
 *     22 of 59 served documents carry an accordion
 *     8 DISTINCT widget ids
 *       7 unique per-page widgets — /, /bathrooms, /decks,
 *         /house-remodels-and-additions, /kitchens, /outdoor-spaces,
 *         /whole-house-renovations
 *       1 SHARED widget (1100007106) on all 15 blog posts
 *     EVERY widget: firstExpanded FALSE, closeOthers TRUE, 5 items
 *
 * BOTH FLAGS AGREE SITE-WIDE HERE, which is the opposite of the inherited site and is
 * worth stating rather than leaving implicit: a per-widget stamp is still used, because
 * a site-wide rule that happens to be right today is the shape that ships unnoticed the
 * day one widget differs.
 *
 * ONE PROPERTY DOES VARY, AND IT IS NOT BEHAVIOURAL. The shared blog widget declares
 * layout LAYOUT_1 on 12 posts and LAYOUT_5 on 3. That string is in each page's own
 * served markup, so the port reproduces the difference verbatim without any config
 * knowing about it — checked three ways: build-pages.py takes only closeOthers from the
 * config, runtime.js never reads a layout, and the LAYOUT_N token is present per page.
 *
 * THE REVEAL BEHAVIOUR IS NOT YET MEASURED HERE. The population to cover when it is
 * taken is the 22 pages above.
 *
 * THE CLOSED RULE IS IN THE PORT AND THE OPEN RULE IS NOT, AND THAT IS NOT A PORTING
 * MISTAKE. styled-components insert through the CSSOM, so a class exists in a
 * document's sheet only if that component actually RENDERED with it. Measured over all
 * 59 served documents: 24 <style data-styled> blocks, NONE empty, the CLOSED rule
 * served once per accordion instance, and NO open-state rule served anywhere — zero
 * non-zero max-height declarations in any of those blocks:
 *
 *     closed  .dygwmn  { overflow:hidden; transition:max-height .3s ease-out;
 *                        height:auto; max-height:0 }        served, x22
 *     open    minted per distinct pixel height at runtime   NOT SERVED, x0
 *
 * The inherited copy named three open classes and their heights (.eZPHSz 185px,
 * .eDGbXZ 211px, .crqarE 236px). Those were read off another site and are deleted
 * rather than renumbered; this site's open classes have not been read off live at all,
 * which is exactly why the rule below is keyed on OUR class.
 *
 * THE OPEN CLASS IS MINTED PER DISTINCT PIXEL HEIGHT, so items sharing a height share
 * a class. No open-state name can be hardcoded, and restoring the rule under OUR OWN
 * class is recovering a sheet the live read could not reach.
 * ------------------------------------------------------------------------- */
#dm .mg-acc-open.mg-acc-open.mg-acc-open {
  max-height: 2000px;
}

/* ---- Pre-launch review 2026-10-06 ------------------------------------------ */

/* Tablet/phone drawer sub-menus ("Our Services", "Areas We Serve"). runtime.js
 * drawer() opens and closes each from its label or caret; closed is the class
 * gy-sub-closed. The closed state collapses height, padding, border and opacity
 * together (max-height alone clips only the content box), takes the panel out of the
 * tab order, and is !important at doubled id specificity so it outranks the ported
 * cascade's own :hover opener, which a tap leaves stuck on a touch screen and which
 * would otherwise keep a closed group open. Adapted from client-kokesconstructs. */
#hamburger-drawer#hamburger-drawer li.gy-sub > .unifiednav__container_sub-nav {
  overflow: hidden;
  transition: max-height .3s ease, opacity .2s ease;
}
#hamburger-drawer#hamburger-drawer li.gy-sub.gy-sub-closed > .unifiednav__container_sub-nav {
  max-height: 0 !important;
  padding-top: 0 !important;
  padding-bottom: 0 !important;
  margin-top: 0 !important;
  margin-bottom: 0 !important;
  border-width: 0 !important;
  opacity: 0 !important;
  pointer-events: none !important;
  visibility: hidden;
}
#hamburger-drawer#hamburger-drawer li.gy-sub:not(.gy-sub-closed) > .unifiednav__container_sub-nav {
  opacity: 1 !important;
  pointer-events: auto !important;
}
/* Closed, the caret points down whatever :hover says. */
#hamburger-drawer#hamburger-drawer li.gy-sub.gy-sub-closed > a .icon::before {
  transform: none !important;
}
/* The close (X) follows the panel's scroll (runtime.js drawer()). Its row and the
 * menu's row can each be their own stacking context, and the later one — the menu —
 * would paint over the X once an open group scrolled up under it. */
#hamburger-drawer .hamburgerButton {
  position: relative;
  z-index: 5;
}
#hamburger-drawer div:has(> .hamburgerButton),
#hamburger-drawer div:has(.hamburgerButton) {
  z-index: 5;
}

/* The 404 page. Duda styles its "4 04" block from a platform sheet that is not part of
 * the port, so the page shipped as four lines of unstyled text pressed against the
 * left edge. Live's measured look (1440, 768 and 390, identical on all three),
 * restated: 120px above, centred on white, a 130px/130px Oswald "4 04" with the first
 * 4 leaning 15deg, a 22px/33px line with 45px around it, and a 184x37 grey button. */
#dm #error-container {
  padding: 120px 0 0;
  text-align: center;
  background-color: rgb(255, 255, 255);
}
#dm #error-container .four-o-four {
  font-family: Oswald, sans-serif;
  font-size: 130px;
  line-height: 130px;
  color: rgb(45, 46, 50);
}
#dm #error-container .four-o-four .lean {
  display: inline-block;
  transform: rotate(15deg) translate(-5px, -4px);
}
#dm #error-container .description {
  margin: 45px 0;
  font-size: 22px;
  line-height: 33px;
  color: rgb(45, 46, 50);
}
#dm #error-container a.back-button {
  display: inline-block;
  box-sizing: border-box;
  width: 184px;
  height: 37px;
  margin: 0 0 20px;
  padding: 0;
  border-radius: 2px;
  background-color: rgb(137, 137, 137);
  color: rgb(255, 255, 255) !important;
  font-size: 16px;
  line-height: 37px;
  text-decoration: none !important;
}
#dm #error-container a.back-button:hover,
#dm #error-container a.back-button:focus-visible {
  background-color: rgb(45, 46, 50);
}

/* RETAGGED HEADINGS (tools/review-content-fixes.py), pinned to the type each had
 * before, as measured at 1440 / 1100 / 1024 / 768 / 390 / 320, so nothing moves.
 *
 * /blog-search: "Search Results" is the page's <h1> now (it was an <h2>, and the page
 * had no h1): Montserrat 700, normal line-height, no margin, 32 / 27 / 26px.
 * Home: "Field Irrigation Contractor in Jerome, Idaho" is an <h2> now (the page had
 * two h1s; the hero's stays): Montserrat 700, 45 / 35 / 30px. */
#dm#dm .dmNewParagraph[id="1523391464"] h1.gy-h1,
#dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1 {
  font-family: Montserrat, "Montserrat Fallback";
  font-weight: 700;
  font-style: normal;
  line-height: normal;
  color: rgb(45, 46, 50);
  margin: 0;
  padding: 0;
  text-transform: none;
  letter-spacing: normal;
  text-decoration: none;
}
#dm#dm .dmNewParagraph[id="1523391464"] h1.gy-h1 { font-size: 32px; }
#dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1,
#dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1 span { font-size: 45px; }
@media (min-width: 768px) and (max-width: 1024px) {
  #dm#dm .dmNewParagraph[id="1523391464"] h1.gy-h1,
  #dm#dm .dmNewParagraph[id="1523391464"] h1.gy-h1 span { font-size: 27px !important; }
  #dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1,
  #dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1 span { font-size: 35px; }
}
@media (max-width: 767px) {
  #dm#dm .dmNewParagraph[id="1523391464"] h1.gy-h1 { font-size: 26px; }
  #dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1,
  #dm#dm .dmNewParagraph[id="3660874942"] h2.gy-h2-as-h1 span { font-size: 30px; }
}

/* Desktop header between 1025 and 1439px wide (review 2026-10-06). The five menu
 * labels need about 720px on one row at their full size (16px type, 20px of padding
 * either side); below 1440 the menu's column is narrower than that, so on live and
 * here "CONTACT US" broke onto a second row under the rest (measured at 1025, 1100,
 * 1280 and 1366; one row at 1440). The row is kept whole and the padding gives up the
 * difference, linearly: 8px at 1025 back to the full 20px at 1440. 1440 and wider are
 * untouched. Adapted from client-kokesconstructs (same FlexHeader nav id). */
@media (min-width: 1025px) and (max-width: 1439px) {
  #dm#dm nav[id="1198691314"] > ul {
    flex-wrap: nowrap !important;
  }
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item {
    padding-left: clamp(8px, calc(8px + (100vw - 1025px) * 0.0289), 20px) !important;
    padding-right: clamp(8px, calc(8px + (100vw - 1025px) * 0.0289), 20px) !important;
    white-space: nowrap;
  }
}

/* THE MENU WAS INVISIBLE ON /blog-search AND THE 404 PAGE (on live too). Every other
 * page opens with a dark hero photo under the transparent header, which is what the
 * white menu labels and the white phone/tablet hamburger are drawn for. These two
 * pages have no hero, so both sat white on white: measured 1.00:1 at 1440, 768 and
 * 390. They take the site's body ink here, and the brand green on hover. */
body[data-page-alias="dmPageNotFound"] #dm#dm#dm .dmInner #flex-header nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .nav-item-text,
body[data-page-alias="blog-search"] #dm#dm#dm .dmInner #flex-header nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .nav-item-text,
body[data-page-alias="dmPageNotFound"] #dm#dm#dm .dmInner #flex-header nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .icon,
body[data-page-alias="blog-search"] #dm#dm#dm .dmInner #flex-header nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .icon {
  color: rgb(45, 46, 50) !important;
}
body[data-page-alias="dmPageNotFound"] #dm#dm#dm .dmInner #flex-header nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item:hover .nav-item-text,
body[data-page-alias="blog-search"] #dm#dm#dm .dmInner #flex-header nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item:hover .nav-item-text {
  color: rgb(0, 154, 73) !important;
}
body[data-page-alias="dmPageNotFound"] #dm#dm #flex-header > div .hamburgerButton svg,
body[data-page-alias="dmPageNotFound"] #dm#dm #flex-header > div .hamburgerButton svg path,
body[data-page-alias="blog-search"] #dm#dm #flex-header > div .hamburgerButton svg,
body[data-page-alias="blog-search"] #dm#dm #flex-header > div .hamburgerButton svg path {
  fill: rgb(45, 46, 50) !important;
}

/* /blog-search on a phone: the result heading ("Search results for ..." / "No results
 * found for ...") is written into the blog list, and the phone band hides an empty
 * list, so a search that matched nothing answered with a blank page. */
#dm#dm .mainBlog:has(> .mg-search-heading) {
  display: block !important;
}

/* THE END OF BOTH LEGAL PAGES WAS HIDDEN UNDER THE FOOTER ON PHONES (on live too).
 * Duda gives each legal widget's wrapper a fixed pixel height (3552px for the privacy
 * policy; 3505px, 3779px on phones, for the terms). On a narrow screen the text wraps
 * to more than that — 4069px at 390 and 4705px at 320 for the policy — and the
 * overflow ran on underneath the footer: "Changes to This Policy" and the whole
 * contact block could not be read at 320-430, nor the end of the terms at 320. The
 * fixed height becomes a minimum, so the page is unchanged wherever the text fits
 * (every width from 768 up, measured) and grows only where it did not. */
#dm#dm #afab7c3e {
  height: auto !important;
  min-height: 3552px;
}
#dm#dm #widget_b05 {
  height: auto !important;
  min-height: 3505px;
}
@media (max-width: 767px) {
  #dm#dm #widget_b05 {
    min-height: 3779px;
  }
  /* Where the text now sets the height, keep it clear of the footer's wave. Inside
   * the minimum (border-box), so nothing grows where the text already fitted. */
  #dm#dm #afab7c3e,
  #dm#dm #widget_b05 {
    box-sizing: border-box;
    padding-bottom: 32px;
  }
}