/* 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 /blog-search (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.
 *   /blog-search   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-menu ("Services"). runtime.js drawer() opens and closes it
 * from the label or the 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. */
#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;
}
/* Closed, the caret points down whatever :hover says. */
#hamburger-drawer#hamburger-drawer li.gy-sub.gy-sub-closed > a .icon::before {
  transform: none !important;
}
#hamburger-drawer .hamburgerButton {
  position: relative;
  z-index: 5;
}

/* 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: 40px 40px 80px;
  box-sizing: border-box;
}
#dm .gy-legal-row h2 {
  margin: 36px 0 12px;
}
#dm .gy-legal-row p,
#dm .gy-legal-row li {
  line-height: 1.6;
}
#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: 24px 16px 60px;
  }
}

/* Footer "Privacy Policy | Terms & Conditions" (tools/build-legal-pages.mjs): the
 * copyright line above it is 13px, and 10px on phones. */
@media (max-width: 767px) {
  #dm .dmFooterContainer .gy-legal-links {
    font-size: 10px !important;
  }
}

/* /contact-us form legal line (tools/build-legal-pages.mjs). It is the last child of
 * the form step's flex column, whose row-gap (10px desktop and tablet, 24px phone)
 * plus the SEND group's own padding left the text 31px under the button (45px on
 * phones). Brought to ~15px, on one line, in the labels' ink. */
#dm#dm .gy-legal-links--form {
  padding-top: 0 !important;
  margin-top: -2px;
  white-space: nowrap;
}
#dm#dm .gy-legal-links--form a {
  color: inherit !important;
  text-decoration: underline !important;
}
@media (max-width: 767px) {
  #dm#dm .gy-legal-links--form {
    margin-top: -16px;
  }
}

/* /gallery name pill linked to the home page (tools/review-fixes.py): the pill keeps
 * its own white-on-black label look; body-copy link styling does not apply to it. */
#dm#dm a.gy-pill-link {
  color: inherit !important;
  font-weight: inherit !important;
  text-decoration: none !important;
}

/* "REQUEST AN ESTIMATE" under the /gallery photos (tools/review-fixes.py). The site
 * button's measured look, restated, because a copied Duda button is styled only by
 * per-page id rules: the black pill the site uses on white ("VIEW GALLERY",
 * "CALL (706) 681-3582") — 257x50, rgb(12,12,12), radius 100px, Poppins 700 16px
 * (14px on phones), white label; hover turns white with rgb(45,46,50) ink over 0.2s,
 * as theirs do. The border is kept visible on hover so the button does not vanish
 * into the white page. order:99 because the column places its children by order. */
#dm .gy-cta {
  order: 99;
  align-self: center;
  width: 100%;
  margin-top: 30px;
  text-align: center;
}
#dm#dm a.gy-cta-btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  box-sizing: border-box;
  width: 257px;
  max-width: 100%;
  height: 50px;
  padding: 10px 0;
  background-color: rgb(12, 12, 12);
  border: 2px solid rgb(12, 12, 12);
  border-radius: 100px;
  color: rgb(255, 255, 255) !important;
  font-family: Poppins, "Poppins Fallback", sans-serif;
  font-size: 16px;
  font-weight: 700;
  line-height: normal;
  text-decoration: none !important;
  white-space: nowrap;
  transition: background-color .2s, border-color .2s, color .2s;
}
#dm#dm a.gy-cta-btn:hover,
#dm#dm a.gy-cta-btn:focus-visible {
  background-color: rgb(255, 255, 255);
  border-color: rgb(65, 67, 69);
  color: rgb(45, 46, 50) !important;
}
@media (max-width: 767px) {
  #dm .gy-cta {
    margin-bottom: 25px;
  }
  #dm#dm a.gy-cta-btn {
    font-size: 14px;
  }
}

/* The scrolling "Full Tree Services and Landscaping" band (7 pages) is rotated
 * -1.5deg, so its corners reach 1px past both edges of the screen and the whole page
 * could be dragged 1px sideways at every width (55px on live's phone document). The
 * band's own parent clips it horizontally; `clip` makes no scroll container, so
 * nothing vertical and nothing sticky is affected. */
#dm *:has(> [id="95e68dd3"]) {
  overflow-x: clip;
}

/* The 404 page (review 2026-10-01). 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, restated: 120px above,
 * centred, a 130px "4 04" with the first 4 leaning 15deg, a 22px line with 45px
 * around it, and a 184x37 grey button.
 * AND THE HEADER: on live and here the header of this page is white, with the white
 * logo and white menu on it — an invisible header. It takes the black the header
 * turns to on every other page once scrolled. */
body[data-page-alias="dmPageNotFound"] #flex-header {
  background-color: rgb(0, 0, 0) !important;
}
#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: normal;
  color: rgb(45, 46, 50);
}
#dm #error-container .four-o-four .lean {
  display: inline-block;
  transform: rotate(15deg);
}
#dm #error-container .description {
  margin: 45px 0;
  font-size: 22px;
  line-height: normal;
  color: rgb(45, 46, 50);
}
#dm #error-container a.back-button {
  display: inline-block;
  box-sizing: border-box;
  min-width: 184px;
  height: 37px;
  margin: 0 0 20px;
  padding: 0 20px;
  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);
}

/* /blog-search: "Search Results" became the page's <h1> (tools/review-fixes.py). The
 * site's h1 rule is uppercase, 36px on tablet and a fixed line-height; the title
 * keeps the look it had as an <h2> — measured 32 / 30 / 26px, mixed case, normal
 * line-height at 1440 / 768 / 390. */
body[data-page-alias="blog-search"] #dm .dmNewParagraph h1 {
  text-transform: none !important;
  line-height: normal !important;
}
body[data-page-alias="blog-search"] #dm .dmNewParagraph h1,
body[data-page-alias="blog-search"] #dm .dmNewParagraph h1 span {
  font-size: 32px !important;
}
@media (max-width: 1024px) {
  body[data-page-alias="blog-search"] #dm .dmNewParagraph h1,
  body[data-page-alias="blog-search"] #dm .dmNewParagraph h1 span {
    font-size: 30px !important;
  }
}
@media (max-width: 767px) {
  body[data-page-alias="blog-search"] #dm .dmNewParagraph h1,
  body[data-page-alias="blog-search"] #dm .dmNewParagraph h1 span {
    font-size: 26px !important;
  }
}

/* Desktop header and footer between 1025 and 1199px wide (review 2026-10-01). The
 * six menu labels need 638px on one row (398px of labels + 12 x 20px padding) and
 * the phone pill about 175px; below 1200 their columns are narrower than that, so on
 * live and here "CONTACT US" dropped to a second menu row and the pill wrapped to
 * "(706) 681- / 3582" (and the footer's "CONTACT US TODAY!" to two lines). The
 * pills keep their label on one line, the menus stay on one row, and the link
 * padding gives up the difference (8px at 1025, back to the full 20px at 1200).
 * 1200 and wider are untouched. */
@media (min-width: 1025px) and (max-width: 1199px) {
  /* the pills size to their label, and their columns to the pill */
  #dm#dm [id="5286ad74"],
  #dm#dm [id="81352f97"],
  #dm#dm *:has(> [id="5286ad74"]),
  #dm#dm *:has(> [id="81352f97"]) {
    flex: 0 0 auto !important;
    width: auto !important;
    min-width: 0 !important;
    max-width: none !important;
    grid-template-columns: auto !important;
  }
  #dm#dm a[id="1540576542"],
  #dm#dm a[id="1720354909"] {
    width: auto !important;
    padding-left: 22px !important;
    padding-right: 22px !important;
  }
  #dm#dm a[id="1540576542"] .text,
  #dm#dm a[id="1720354909"] .text {
    white-space: nowrap;
  }
  /* the menu column takes what is left */
  #dm#dm *:has(> * > nav[id="1198691314"]),
  #dm#dm *:has(> * > nav[id="1933256672"]) {
    flex: 1 1 0 !important;
    width: auto !important;
    min-width: 0 !important;
  }
  #dm#dm nav[id="1198691314"] > ul,
  #dm#dm nav[id="1933256672"] > 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,
  #dm#dm#dm .dmInner nav[id="1933256672"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item {
    padding-left: clamp(8px, 6.857vw - 62.3px, 20px) !important;
    padding-right: clamp(8px, 6.857vw - 62.3px, 20px) !important;
    white-space: nowrap;
  }
  /* the footer row also holds a 238px logo, so its menu and pill give up a little more */
  #dm#dm#dm .dmInner nav[id="1933256672"].main-navigation.unifiednav .unifiednav__container:not([data-depth]) > .unifiednav__item-wrap > .unifiednav__item {
    padding-left: clamp(4px, 9.143vw - 89.7px, 20px) !important;
    padding-right: clamp(4px, 9.143vw - 89.7px, 20px) !important;
  }
  #dm#dm a[id="1720354909"] {
    padding-left: 14px !important;
    padding-right: 14px !important;
  }
}

/* The contact form's "sent" and "not sent" panels (runtime.js forms). Their drawing
 * sat in a 100x246 box (59x240 on phones) at the panel's left edge, cropped to a
 * sliver by object-fit:cover. It is a square drawing: shown whole, 160px, centred
 * over the heading it belongs to. */
#dm#dm form [data-mg-success-step] .widget-wrapper:has(> .imageWidget),
#dm#dm form [data-error-step] .widget-wrapper:has(> .imageWidget) {
  width: 160px !important;
  height: 160px !important;
  min-height: 0 !important;
  align-self: center !important;
  margin-left: auto !important;
  margin-right: auto !important;
}
#dm#dm form [data-mg-success-step] .imageWidget,
#dm#dm form [data-error-step] .imageWidget {
  width: 100% !important;
  height: 100% !important;
}
#dm#dm form [data-mg-success-step] .imageWidget img,
#dm#dm form [data-error-step] .imageWidget img {
  width: 100% !important;
  height: 100% !important;
  object-fit: contain !important;
}