/* CARRIED-OVER COMMENTS, 2026-09-28. This file came with the migration toolkit, and some
 * of its comments were written against EARLIER clients' sites in that lineage. Every other
 * client's page path, name and domain was removed from them on 2026-09-28 (shown as
 * "another client's page" and similar). Censuses, counts and widget ids in the comments
 * below were NOT re-measured on this site: do not cite one as a fact about this site
 * without measuring it here. The code is unchanged by that clean-up. */
/* Hand-written overrides for this migration.
 *
 * NO PREVIOUS CLIENT IS NAMED IN THIS FILE, DELIBERATELY: it is copied verbatim into
 * dist, so a prior client's name here would be PUBLISHED on this client's domain and
 * would make a residue sweep report a correct file dirty. Provenance lives in
 * MIGRATION-NOTES, which does not ship.
 *
 * 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.
 *
 * EVERY NUMBER BELOW WAS CENSUSED ON THIS SITE ON 2026-09-08. This file arrived carrying
 * the populations of TWO earlier repos (53 pages/31 posts and 59 pages/15 posts) in prose
 * that read as measurement — gotcha 64. The RULES were sound and are kept; every
 * measurement around them is re-taken. Population, DERIVED and not typed: pages.txt holds
 * 32 paths — 18 static pages (the export's 18 page directories, all still 200 on live)
 * plus the 13 blog posts generated/blog.rss declares as <item>s (one of which the sitemap
 * omits) plus /(another client's page) (declared only in a widget attribute) — so 96 captures
 * (32 x 3 bands) plus 96 served documents (32 x 3 device UAs).
 *
 * 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 this site's one form
 * (/contact — generated/form-pages.json, 1 of 32 pages) and no reCAPTCHA in its served
 * markup either; reCAPTCHA is mounted at runtime and is removed here (gotcha 17: its keys
 * are Duda's own and domain-restricted). So this is ours, must cost nothing, and is the
 * ONLY spam protection. /migration phase 8 specifies exactly this. */
.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 (gotcha 70).
 */

/* ---------------------------------------------------------------------------
 * BLOG PAGINATION — ONE REAL CONTROL, ON ONE PAGE, AND IT IS THE SHOW-MORE SHAPE.
 *
 * Censused on the raw served html of all 32 pages and confirmed by driving live's own
 * control (generated/blog-widgets.json, 6 of 6 records, tools/capture-blog-widgets.mjs):
 *
 *   /(another client's page)     visible-items="9", data-paginate-total-elements="13",
 *                  more-posts-text-container x1  ("Show More" APPENDS): driven 9 -> 13
 *                  on d, t and m.  pagination-nav x0.
 *   /(another client's page)   visible-items="20", total 13, NO control — all 13 render at once.
 *   13 blog posts  NO blog-list widget of any kind (internal_blog_list is on exactly the
 *                  two pages above), so nothing here has a subject on any post.
 *
 * generated/blog.rss independently declares 13 items — counted from the file, never
 * typed — and /(another client's page)'s own total agrees at 13, which is the cross-check that makes a
 * truncated index fail rather than ship quietly (gotcha 83).
 *
 * A static build has no Duda backend, so every card ships and the 4 past the first batch
 * are stamped mg-blog-hidden with data-mg-blog-page; runtime.js reveals them in live's own
 * batch when "Show More" is clicked. This rule is what hides them initially — 13 declared
 * minus the 9 the first render shows = 4 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, while in our build it is followed by hidden
 * siblings, so it stops matching and GAINS that padding. 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. `!important` because Duda's rule here can outrank
 * this one on attribute count and carries none of its own.
 *
 * SUBJECT ON THIS SITE: the 9th card on /(another client's page) and nothing else. Whether Duda's rule
 * is ARMED on this site's cascade is decided by the gate, not asserted here: gate 1 scored
 * /(another client's page) 0.000% at 375, 768 and 1440 with this rule in place. */
#dm .postArticle:not(.mg-blog-hidden):has(+ .postArticle.mg-blog-hidden) {
  padding-bottom: 0 !important;
}

/* ---------------------------------------------------------------------------
 * PER-DEVICE CONTENT FORKS.
 *
 * THIS SITE IS DUDA **FLEX**, AND ON FLEX THE CHROME DOES NOT FORK — GOTCHA 5 IS
 * INVERTED. Measured over generated/served-by-device (96 documents, 32 paths x 3
 * device UAs, all 200):
 *
 *   dmtemplateid    FlexHeader on ALL THREE BANDS, all 32 pages
 *   <body> class    `dmRoot fix-mobile-scrolling flex-site dmResellerSite`,
 *                   BYTE-IDENTICAL on all three bands, all 32 pages
 *   data-flex-site  present on all three bands, all 32 pages
 *
 * `fix-mobile-scrolling` in that class list is LOAD-BEARING (gotcha 35): Duda's
 * body{overflow:hidden} is undone only by it.
 *
 * THE CONTENT FORK IS THREE-WAY, measured on the served BYTES (tools/measure-served-fork.mjs,
 * generated/served-fork.json): desktop == tablet on 0 of 32, desktop == mobile on 0 of 32,
 * each disagreement re-sampled. So each band's body is emitted whole and the two inactive
 * copies are PRUNED pre-paint by the boot script (band_prune). The mg-only-* gates below
 * are the CSS backstop for the interval between parse and prune, and for any element the
 * builder stamps per band rather than per body.
 *
 * THE THREE BANDS DECLARE THREE DIFFERENT VIEWPORTS (32/32 on each band):
 *   desktop  initial-scale=1, minimum-scale=1, maximum-scale=5, viewport-fit=cover
 *   tablet   width=960px                 <- gotcha 3's 960 canvas DOES apply, measured
 *   mobile   width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=5,
 *            viewport-fit=cover
 *
 * THE BAND BOUNDARIES ARE DUDA'S OWN: the ported cascade's media queries are
 * max-width:767px / min-width:768px / max-width:1024px / min-width:1025px, so 1025 is the
 * desktop edge on Duda's own declarations. Only the INACTIVE bands are hidden, inside the
 * media queries; the active band keeps whatever `display` the ported cascade gives it.
 * ------------------------------------------------------------------------- */
@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: NONE ON THIS SITE. ssrimageslider 0 of 96 served documents, .flexslider 0
 * (served AND post-JS), data-gallery-bg 0, .bgGallerySlide 0, <video> 0. No rule, no
 * gate exclusion on rotation grounds, and that is a measurement rather than an omission
 * (positive control on the same corpus: ssraccordion 22/32, mapextension 6/32).
 * ------------------------------------------------------------------------- */

/* ---------------------------------------------------------------------------
 * ACCORDION OPEN STATE — recovering a rule the live CSS read cannot see.
 *
 * THIS SITE, from generated/accordion-config.json (derived from live's own
 * initiateWidget({"type":"SSR_ACCORDION"}) payloads) and corroborated against an
 * `ssraccordion` census of the raw served html:
 *
 *     22 of 32 served documents carry an accordion — ONE widget per page, 22 distinct ids
 *     5 items each, except /faq with 10
 *     EVERY widget: firstExpanded FALSE, closeOthers TRUE, LAYOUT_1
 *     live reveal MEASURED per widget (tools/measure-accordion-reveal.mjs): 0 of 22 auto-open
 *
 * So every accordion ships CLOSED, exactly as live serves it, and there is no
 * expandFirstItem height to reproduce. The per-widget stamp is still used, because a
 * site-wide rule that is right today is the shape that ships unnoticed the day one widget
 * differs.
 *
 * 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; the CLOSED rule (max-height:0)
 * is served once per instance and NO open-state rule is served anywhere, because Duda
 * mints one per distinct pixel height at runtime. runtime.js sets an inline max-height from
 * each panel's own scrollHeight; this rule is the ceiling that lets the transition run.
 * ------------------------------------------------------------------------- */
#dm .mg-acc-open.mg-acc-open.mg-acc-open {
  max-height: 2000px;
}

/* NO POPUP HOST RULES. The FLEX click-popup hosts (#flex-popup-overlay,
 * #flex-runtime-popup-container) that a sibling repo had to hand-write have no subject
 * here: link_type="popup" 0, popup_target 0, flex-runtime-popup 0, #dmPopup 0 on all 96
 * served documents. runtime.js's flexPopup() returns on zero triggers, so the rules are
 * omitted rather than shipped inert. */

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

/* Tablet/phone drawer sub-menus. Live ships both groups flat and expanded
 * (data-show-vertical-sub-items="SHOW"); house standard is that every group starts
 * closed and its caret opens it (runtime.js drawer()). The closed state collapses
 * height, padding, border and opacity together — max-height alone clips only the
 * content box — and takes the panel out of the tab order. */
#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;
}
/* The caret is drawn pointing up (the ::before is rotated 180deg, its open look).
 * Closed, it points down. The .icon itself keeps its own scale(1.3). */
#hamburger-drawer#hamburger-drawer li.gy-sub > a .icon::before {
  transition: transform .2s ease;
}
#hamburger-drawer#hamburger-drawer li.gy-sub.gy-sub-closed > a .icon::before {
  transform: none !important;
}
#hamburger-drawer .hamburgerButton {
  position: relative;
  z-index: 5;
}

/* "Privacy Policy | Terms & Conditions" under each form (tools/review-fixes.py).
 * The line's ink is set from the form's own labels (runtime.js legalLineAlign);
 * the links take that ink rather than the page's link colour. */
#dm .gy-legal-links--form {
  white-space: nowrap;
  color: inherit;
}
#dm .gy-legal-links--form a {
  color: inherit !important;
  font-weight: inherit;
  text-decoration: underline !important;
}

/* Desktop header between 1025 and 1365px (review 2026-10-01). The nav needs 787px
 * on one row (577px of labels + 7 x 30px padding) and the "CONTACT US" pill 172px;
 * below 1366 the row is narrower than that, so on live and here "BLOG" dropped to
 * a second row on its own and the pill wrapped to "CONTACT / US" at 70px tall —
 * at 1280, the most common laptop width. The pill keeps its 1440 width, the nav
 * stays on one row, and the link padding (then, under 1200, the label size) gives
 * up the difference. 1366 and wider are untouched. */
@media (min-width: 1025px) and (max-width: 1365px) {
  #dm [id="5286ad74"] {
    width: 172px !important;
    min-width: 172px !important;
    flex: 0 0 auto !important;
  }
  #dm [id="1540576542"] .text {
    white-space: nowrap;
  }
  #dm nav[id="2602618729"] > ul {
    flex-wrap: nowrap !important;
  }
  #dm nav[id="2602618729"] > ul > li > a.unifiednav__item {
    padding-left: clamp(4px, 6.91vw - 77.6px, 15px) !important;
    padding-right: clamp(4px, 6.91vw - 77.6px, 15px) !important;
    white-space: nowrap;
  }
}
@media (min-width: 1025px) and (max-width: 1199px) {
  #dm nav[id="2602618729"] > ul > li > a.unifiednav__item .nav-item-text {
    font-size: clamp(12.5px, 1.72vw - 4.7px, 16px) !important;
    letter-spacing: 0.2px !important;
  }
}

/* Home hero text on tablet and phone (manual review 2026-10-01). The group holding
 * "Paving Contractor in Loveland, CO / Turn to Harris Asphalt Paving Today / Contact
 * Us Now!" is Duda-pinned (#group_2va[data-pinned]: position:sticky; top:195px).
 * At desktop it sits beside the form and the pin is the design. At 1024 and below
 * the two stack, so the pinned text rode down the page over the form for 823px at
 * 768 and 964px at 390 — on live too. It stays in its own place there. It is the
 * only pinned group on the site with room to travel on those bands. */
@media (max-width: 1024px) {
  #dm #group_2va[data-pinned] {
    position: relative !important;
    top: auto !important;
  }
}

/* "Leave Us a Google Review" under the /testimonials cards (tools/review-fixes.py).
 * The site button's measured look, restated: a copied Duda button is styled only by
 * per-page id rules. Fill rgb(201,63,61), 2px border, 12px 25px, Roboto Slab 700
 * 16px (15px on phones), 1.6px tracking, uppercase; hover turns blue as theirs do. */
#dm .gy-review-cta {
  order: 99;
  align-self: center;
  width: 100%;
  margin-top: 16px;
  text-align: center;
}
#dm a.gy-review-btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  box-sizing: border-box;
  max-width: 100%;
  padding: 12px 25px;
  background-color: rgb(201, 63, 61);
  border: 2px solid rgb(201, 63, 61);
  border-radius: 0;
  color: rgb(255, 255, 255) !important;
  font-family: "Roboto Slab", "Roboto Slab Fallback", serif;
  font-size: 16px;
  font-weight: 700;
  letter-spacing: 1.6px;
  line-height: normal;
  text-transform: uppercase;
  text-decoration: none !important;
  white-space: nowrap;
  transition: background-color .2s, border-color .2s;
}
#dm a.gy-review-btn:hover,
#dm a.gy-review-btn:focus-visible {
  background-color: rgb(61, 88, 155);
  border-color: rgb(61, 88, 155);
  color: rgb(233, 233, 233) !important;
}
@media (max-width: 767px) {
  #dm a.gy-review-btn {
    font-size: 15px;
  }
}
@media (max-width: 359px) {
  #dm a.gy-review-btn {
    padding: 12px 14px;
    font-size: 13px;
    letter-spacing: 1px;
  }
}