/* Hand-written overrides for this migration.
 *
 * 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.
 *
 * THIS FILE SHIPS VERBATIM INTO dist, so no previous client is named in it. A name in a
 * comment here publishes another company's name on this client's site, and it makes a
 * retarget sweep report this build dirty on a file that is correct.
 *
 * EVERY NUMBER BELOW WAS CENSUSED ON THIS SITE, AND THE ONES IT REPLACED WERE NOT. The
 * copy this was written from described a 59-page site with a NUMBERED blog pager and 19
 * posts that have no pagination control at all. None of that is true here — and it was
 * true of the site it was written on, which is exactly what makes an inherited comment
 * convincing. The RULES were sound and are kept; every measurement around them is
 * re-taken.
 *
 * Population, DERIVED and not typed: pages.txt holds 23 paths — 8 static plus the 15
 * blog posts generated/blog.rss declares as <item>s — so 69 captures (23 pages x 3
 * bands) plus 23 raw served documents, and a separately captured /404. 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 — A "SHOW MORE" CONTROL ON EVERY BLOG-BEARING PAGE.
 *
 * Censused on the raw served html of all 23 pages (the pages.txt population) and
 * confirmed by DRIVING LIVE'S OWN CONTROL. The record count is DERIVED, not typed:
 * generated/blog-widgets.json covers /blog plus the 15 posts generated/blog.rss
 * declares — 16 blog-bearing pages x 3 bands = 48 records, and every one reached its
 * own declared total.
 *
 *   /blog             declared 15, visible 9    SHOW MORE, APPENDS
 *                     more-posts-text-container x1,
 *                     <nav class="pagination-nav"> x0 (zero on all 23 pages).
 *                     data-paginate-total-elements=15, visible-items=9. Driving it
 *                     stepped [9, 15] and the control then retired.
 *
 *   15 blog posts     declared 14, visible 10   SHOW MORE, APPENDS
 *                     Each post's RELATED-POSTS widget declares 14 — the other 14
 *                     posts — and renders 10 behind the same control. Driving it
 *                     stepped [10, 14] on every one.
 *
 * THE INHERITED TEXT DESCRIBED THE OPPOSITE SHAPE ON BOTH COUNTS: a NUMBERED
 * pagination-nav that REPLACES the visible set on /blog, and posts with NO control at
 * all whose remainder live itself strands. Neither is true here — this site has zero
 * numbered pagers and every blog-bearing page reaches its full declared set — so a
 * build that trusted that comment would have shipped a truncated /blog and a truncated
 * related-posts row on all 15 posts, each looking exactly like the original.
 *
 * blog.rss independently declares 15 items, which is the cross-check that makes a
 * truncated /blog FAIL rather than ship quietly: the recovery is asserted against a
 * source that cannot agree with our own capture by construction.
 */
#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 23 pages
 *   <body> class    `dmRoot fix-mobile-scrolling flex-site dmResellerSite`,
 *                   BYTE-IDENTICAL on all three bands, all 23 pages
 *   data-flex-site  present on all three bands, all 23 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. 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;
}

/* ---- Website review fixes, 2026-09-26 ------------------------------------------ */

/* Drawer submenu caret follows the group's OPEN state, not the page's selected state.
 * The ported rule rotates it for any .dmNavItemSelected parent, which now includes
 * Areas Served on /houston-tx, so the caret pointed up on a closed group. */
#dm .hamburger-drawer li[data-sub-nav-menu] > a .icon::before { transform: none !important; transition: transform .3s ease; }
#dm .hamburger-drawer li[data-sub-nav-menu].unifiednav__item-wrap_open > a .icon::before { transform: rotate(180deg) !important; }

/* Mobile click-to-call (house standard: calling must not need the menu). Layout per
 * review 2026-09-26: call icon at the LEFT of the dark logo bar, wordmark centred,
 * menu alone in the orange box on the right exactly as live has it. The logo bar
 * gains 44px of left padding for the icon; its right padding grows to match so the
 * wordmark stays centred, and the wordmark steps down a little on narrow phones so
 * it keeps to one line (live keeps one line down to 344px). */
#dm #d1a9b054:has(> .gy-mobile-call) { position: relative; padding-left: 44px !important; padding-right: 44px !important; }
#dm .gy-mobile-call { position: absolute; left: 12px; top: 50%; transform: translateY(-50%); display: flex; align-items: center; justify-content: center; width: 30px; height: 44px; color: rgb(250, 128, 1); text-decoration: none; z-index: 2; }
#dm .gy-mobile-call svg { display: block; width: 22px; height: 22px; }
#dm .gy-mobile-call:active { opacity: .7; }
/* The bar is 83.16vw wide; less the 88px of padding, the wordmark measures ~7.7px
 * per px of font-size, so this keeps it on one line down to 320 and caps at live's 32px. */
@media (max-width: 767px) { #dm #d1a9b054:has(> .gy-mobile-call) #\31 258009384 a { font-size: min(32px, calc((83.16vw - 92px) / 8)) !important; } }
}

/* /blog-search results heading, matching live: centred, uppercase display face. */
#dm .mg-search-heading { display: block; width: 100%; grid-column: 1 / -1; text-align: center; text-transform: uppercase; font-family: 'Black Ops One', 'Black Ops One Fallback', sans-serif; font-size: 30px; line-height: 1.2; color: rgb(38, 38, 38); margin: 0 0 24px; }
@media (max-width: 767px) { #dm .mg-search-heading { font-size: 22px; } }

/* Footer GBP map: house maximum is 300px tall (was 350). */
#flex-footer iframe[src*="google.com/maps"] { height: 300px !important; max-height: 300px; display: block; }

/* Legal pages (/privacy-policy, /terms-and-conditions). Duda's reset zeroes margin on
 * p, ul and h2, so the rhythm is set explicitly. */
#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; } }

/* Drawer sub-menu ink. The per-page cascade paints "Houston, TX" black on the
 * rgb(29,29,29) drawer on 22 of 25 pages (white only on a few), so the opened
 * group looked empty. White like the top-level items; the current page in the
 * site's orange, like the top-level selected item. */
#dm#dm .hamburger-drawer .unifiednav__container_sub-nav a.unifiednav__item,
#dm#dm .hamburger-drawer .unifiednav__container_sub-nav a.unifiednav__item .nav-item-text { color: rgb(255, 255, 255) !important; }
#dm#dm .hamburger-drawer .unifiednav__container_sub-nav a.unifiednav__item.dmNavItemSelected,
#dm#dm .hamburger-drawer .unifiednav__container_sub-nav a.unifiednav__item.dmNavItemSelected .nav-item-text { color: rgb(250, 128, 1) !important; }

/* Home "Specialized Solutions": each card links to its page. An absolute overlay
 * anchor (not a wrapper) so Duda's flex sizing of the card is untouched. */
#dm #\36 673e9ba, #dm #f203c818, #dm #\36 59baf1c { position: relative; cursor: pointer; }
#dm .gy-card-link { position: absolute; inset: 0; z-index: 5; display: block; }

/* Blog "Show More": on desktop and tablet the button shrank to its text and wrapped
 * onto two lines ("Show / More"). One line, with side padding so it reads as a button. */
#dm .more-posts-text-container .morePosts { white-space: nowrap; padding-left: 40px !important; padding-right: 40px !important; }