/* Hand-written overrides for this migration (www.ckbusinessconsulting.com).
 *
 * 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.
 *
 * Copied forward with the toolkit. The RULES describe the build's own mechanisms and
 * transfer; any number inside a comment below was measured on the site it was written
 * on and is NOT a measurement of this one unless it says so. This site, 2026-10-01:
 * 37 paths in pages.txt (plus the 404), 111 desktop/tablet/mobile captures, no blog.
 */

/* 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 any
 * form, 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 <a page on another site> plus the 15 posts
 * generated/blog.rss declares — 20 blog-list pages x 3 bands = 60 records:
 *
 *   <a page on another site>             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 the site it was measured on's shape and it is on <a page on another site> 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 <a page on another site> fail rather than ship quietly, and the alias set driven out of
 * <a page on another site> 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 THE SITE IT WAS MEASURED ON, 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.
 *
 * THE SITE IT WAS MEASURED ON 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 THE SITE IT WAS MEASURED ON. 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 THE SITE IT WAS MEASURED ON, 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 the site it was measured on's — that site forked two ways with no
 * 960 tablet canvas and used two DIFFERENT drawer elements, while the site it was measured on 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 THE SITE IT WAS MEASURED ON, 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 the site it was measured on'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 the site it was measured on
 *       has ZERO. It will FATAL on an empty population. That refusal is honest about
 *       ITS subject and says nothing about the site it was measured on'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 THE SITE IT WAS MEASURED ON: 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,
 * <a page on another site> and /service-areas — none of which exist here. All of it is
 * a previous client's and is deleted rather than renumbered.
 *
 * THE SITE IT WAS MEASURED ON, 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 — /, <a page on another site>, <a page on another site>,
 *         <a page on another site>, <a page on another site>, <a page on another site>,
 *         <a page on another site>
 *       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; the site it was measured on'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-09-29 ------------------------------------------ */

/* Legal pages (tools/build-legal-pages.mjs). Duda's reset zeroes margin on p, ul
 * and h2, so the template text would otherwise render as one slab with every
 * heading pressed against the paragraph above it. */
#dm .gy-legal-row {
  max-width: 1200px;
  margin: 0 auto;
  padding: 60px 40px 80px;
  box-sizing: border-box;
}
#dm .gy-legal-row h2 {
  margin: 36px 0 12px;
}
#dm .gy-legal-row p {
  margin: 0 0 14px;
}
#dm .gy-legal-row ul {
  margin: 0 0 14px;
  padding-left: 1.4em;
  list-style: disc;
}
#dm .gy-legal-row li {
  margin: 0 0 4px;
}
@media (max-width: 767px) {
  #dm .gy-legal-row {
    padding: 40px 16px 60px;
  }
}

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

/* Desktop menu on one row, 1025-1259px (on live too). The nine labels need 1188px at
 * the menu's own 16px type and 15px side padding, and the menu column is 0.96 x the
 * window (984px at 1025, 1056 at 1100, 1152 at 1200), so "SERVICE AREAS" and "CONTACT"
 * dropped onto a second row until the column reached 1188px at about 1240. Inside that
 * range the labels step down in size and padding so the row fits its column; 1260 and
 * wider are untouched. */
@media (min-width: 1025px) and (max-width: 1099px) {
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item {
    padding-left: 7px !important;
    padding-right: 7px !important;
  }
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .nav-item-text {
    font-size: 14px !important;
  }
}
@media (min-width: 1100px) and (max-width: 1179px) {
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item {
    padding-left: 8px !important;
    padding-right: 8px !important;
  }
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .nav-item-text {
    font-size: 15px !important;
  }
}
@media (min-width: 1180px) and (max-width: 1259px) {
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item {
    padding-left: 10px !important;
    padding-right: 10px !important;
  }
}
@media (min-width: 1025px) and (max-width: 1259px) {
  #dm#dm#dm .dmInner nav[id="1198691314"].main-navigation.unifiednav > .unifiednav__container:not([data-depth]) {
    flex-wrap: nowrap !important;
  }
}

/* Footer buttons on phones (on live too): "CALL US" and "CONTACT US ONLINE TODAY!"
 * shared one row, 142px and 193px wide at 390, so the second label broke onto two
 * lines at every phone width. They stack, each the width of the column and 60px tall
 * (the height "CALL US" already had), 16px apart, and each label sits on one line. */
@media (max-width: 767px) {
  #dm#dm [id="273fb130"] {
    flex-direction: column !important;
    align-items: stretch !important;
    height: auto !important;
    row-gap: 16px !important;
  }
  #dm#dm [id="273fb130"] > [id="8d710b67"],
  #dm#dm [id="273fb130"] > [id="5989a474"] {
    width: 100% !important;
    max-width: 100% !important;
    height: 60px !important;
    min-height: 60px !important;
  }
  #dm#dm [id="273fb130"] a.dmButtonLink {
    width: 100% !important;
    height: 60px !important;
  }
  #dm#dm [id="273fb130"] a.dmButtonLink .text {
    white-space: nowrap !important;
  }
  /* The copyright line: "© 2026" was a 31px flex column of its own, so the year broke
   * under the symbol beside the rest of the line. It reads as one centred sentence. */
  #dm#dm .dmFooterContainer .widget-1f5975 .copyright {
    display: block !important;
    text-align: center;
  }
  #dm#dm .dmFooterContainer .widget-1f5975 .copyright > div,
  #dm#dm .dmFooterContainer .widget-1f5975 .copyright > div > p {
    display: inline !important;
  }
}

/* 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 with a default blue link. Live's measured look (1440, 1025 and 390): 120px
 * above, centred on white, a 130px "4 04" in Oswald (falling back to sans-serif, as on
 * live) in the site's navy rgb(14,26,54) with the first 4 rotated 15deg, a 22px line
 * with 45px above and below, and a 184x37 button, white on rgb(137,137,137). The
 * message line is the page's <h1> now (tools/review-fixes.py) and keeps that type.
 * The footer's contact card rises 80px over whatever precedes it, which on live covers
 * the button completely; the block ends 110px lower so the button is in the clear. */
#dm #error-container {
  padding: 120px 0 110px;
  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: normal;
  color: rgb(14, 26, 54);
}
#dm #error-container .four-o-four .lean {
  display: inline-block;
  transform: rotate(15deg);
}
#dm#dm #error-container h1.description {
  margin: 45px 0;
  padding: 0;
  font-family: 'Open Sans', 'Open Sans Fallback', sans-serif;
  font-size: 22px;
  font-weight: 400;
  font-style: normal;
  line-height: normal;
  letter-spacing: normal;
  text-transform: none;
  text-align: center;
  color: rgb(14, 26, 54);
}
#dm #error-container a.back-button {
  display: inline-block;
  box-sizing: border-box;
  min-width: 184px;
  height: 37px;
  margin: 0 0 20px;
  padding: 0 12px;
  background-color: rgb(137, 137, 137);
  color: rgb(255, 255, 255) !important;
  font-size: 16px;
  line-height: 37px;
  text-decoration: none !important;
}
/* The 404 page has no hero photo, so the header's white menu sat on the page's white
 * ground and could not be seen (on live too). At rest the labels and carets take the
 * site's navy; once the page scrolls the bar turns navy itself and they are white
 * again, as everywhere else. */
body[data-page-alias="dmPageNotFound"] #flex-header:not([data-scrolling]) nav[id="1198691314"] .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .nav-item-text,
body[data-page-alias="dmPageNotFound"] #flex-header:not([data-scrolling]) nav[id="1198691314"] .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item .icon {
  color: rgb(14, 26, 54) !important;
}
/* The closed menu drawer is parked off the right edge; on this page alone nothing
 * clipped it, so a 1025-1100px window scrolled sideways by its width (on live too). */
body[data-page-alias="dmPageNotFound"] {
  overflow-x: clip;
}
/* The same goes for the business name and tagline beside the logo: white on the 404
 * page's white ground (on live too), navy at rest here. */
body[data-page-alias="dmPageNotFound"] #flex-header:not([data-scrolling]) .dmNewParagraph,
body[data-page-alias="dmPageNotFound"] #flex-header:not([data-scrolling]) .dmNewParagraph * {
  color: rgb(14, 26, 54) !important;
}