/* ==========================================================================
   aad-migration.css — AAD content-migration stylesheet
   --------------------------------------------------------------------------
   Created 2026-08-19 (Phase R, Sullivan).

   PURPOSE
   All NEW styles introduced by the ddsdenver.com content migration live here.
   `aad-custom.css` (the original June build sheet) stays untouched so the
   client-approved rendering never shifts underneath us; Eric merges the two
   files at the end of the migration.

   LOAD ORDER
   Enqueued by the `aad-custom-css.php` mu-plugin immediately AFTER
   `aad-custom.css`, with the same filemtime cache-bust. Because it loads
   second, plain-specificity overrides win here without needing `!important`.

   RULES OF THE ROAD
   - Do NOT edit via WP Customizer → Additional CSS: the sanitizer HTML-encodes
     the `>` child combinator and silently breaks every rule that uses it.
   - Every `!important` is a smell — the base sheet already carries 219 of them;
     do not add more here without a comment explaining what it beats.
   - Layout/component CSS only. Design tokens stay in the Elementor Kit (post 6).

   SECTIONS
     1. HTML→native conversion bridges (Phase R)
   ========================================================================== */


/* --------------------------------------------------------------------------
   1. HTML→native conversion bridges (Phase R, 2026-08-19)
   --------------------------------------------------------------------------
   Six HTML widgets became native widgets. The original CSS in aad-custom.css
   targets the hand-written markup (`ul.aad-svc-bullets`, `.aad-pay-logos img`);
   these rules re-point that exact styling at Elementor's native markup so the
   rendering is byte-for-byte identical. No visual change is intended here.
   -------------------------------------------------------------------------- */

/* 1a. Service bullet lists: 4 × html <ul> → `icon-list` widgets.
   The widget keeps the ORIGINAL `aad-svc-bullets-wrap` class (the white bubble),
   so every bubble rule in aad-custom.css still applies untouched. What changed is
   the list markup inside it: `ul.aad-svc-bullets` → `ul.elementor-icon-list-items`,
   so the two-column list rules are re-declared against Elementor's own markup. */
.aad-svc-bullets-wrap ul.elementor-icon-list-items {
  list-style: none;
  margin: 0;
  padding: 0;
  columns: 2;
  column-gap: 32px;
  width: 100%;
}

.aad-svc-bullets-wrap ul.elementor-icon-list-items li.elementor-icon-list-item {
  font-family: 'halyard-display', sans-serif;
  font-weight: 300;
  font-size: 20px;
  color: #423939;
  line-height: 1.3;
  padding: 6px 0;
  margin: 0;
  position: relative;
  break-inside: avoid;
  list-style: none;
  display: block;      /* Elementor ships flex here; the original was a block <li> */
}

/* The original design removed every bullet glyph; the icon span is empty
   anyway (no icon is set) but this keeps it from reserving inline space. */
.aad-svc-bullets-wrap ul.elementor-icon-list-items li.elementor-icon-list-item::before,
.aad-svc-bullets-wrap ul.elementor-icon-list-items li.elementor-icon-list-item::after {
  content: none;
}

.aad-svc-bullets-wrap .elementor-icon-list-icon {
  display: none;
}

/* Elementor's own rule (`.elementor-widget-icon-list .elementor-icon-list-text`)
   is more specific than a bare `.aad-svc-bullets-wrap .elementor-icon-list-text`
   and was pulling the Kit's 22px/33px body token into the span, so the longest
   labels ("Cavity Prevention Therapy", "Oral Cancer & HPV Screenings") needed
   226px inside a 225px column and wrapped to a second line — which then pushed
   the last row out of the fixed-height bubble. Match Elementor's specificity and
   restore the original 20px/1.3 exactly. */
.elementor-widget-icon-list.aad-svc-bullets-wrap .elementor-icon-list-text,
.elementor-widget-icon-list.aad-svc-bullets-wrap .elementor-icon-list-item > .elementor-icon-list-text {
  padding: 0;
  color: #423939;
  font-family: 'halyard-display', sans-serif;
  font-size: 20px;
  font-weight: 300;
  line-height: 1.3;
}

/* The widget IS the white bubble (it carries .aad-svc-bullets-wrap, exactly as
   the html widget did), so aad-custom.css still paints the background, radius,
   26/28 padding and the fixed 270px height. Elementor's own wrapper just has to
   stop constraining the list inside it. */
.aad-svc-bullets-wrap > .elementor-widget-container {
  width: 100%;
  height: 100%;
  display: flex;
  align-items: flex-start;
}

/* Tablet/mobile: aad-custom.css collapses the bubble to one column. Mirror it. */
@media (max-width: 1024px) {
  .aad-svc-bullets-wrap ul.elementor-icon-list-items { columns: 1; }
}

/* 1b. Payment logos: 2 × html blocks → container + native `image` widgets.
   `.aad-pay-logos` (flex row, 22px gap) still comes from aad-custom.css and is
   carried by the new container. These rules just stop Elementor's image widget
   from stretching the logos, matching the old `height:30px; width:auto`. */
.aad-pay-logos .elementor-widget-image,
.aad-pay-logos .elementor-widget-image .elementor-widget-container {
  width: auto;
  flex: 0 0 auto;
}

.aad-pay-logos .elementor-widget-image img,
.aad-pay-logo-img img {
  height: 30px;
  width: auto;
  max-width: none;
  object-fit: contain;
  display: inline-block;
}

/* The CareCredit lockup sat 14px lower than the PayPal/Apple row. */
.aad-pay-logos--carecredit .elementor-widget-image img {
  margin-top: 14px;
}

/* "Now Accepting" was a <p class="aad-now-accepting"> inside the html widget and
   is now a heading widget rendering a <div> (house rule: never H1–H6 for a
   label). Elementor's heading styles have to be neutralised back to the label. */
.elementor-widget.elementor-widget-heading.aad-now-accepting .elementor-heading-title,
.elementor-widget-heading.aad-now-accepting .elementor-heading-title {
  font-family: 'halyard-display', sans-serif;
  text-transform: uppercase;
  letter-spacing: 3px;
  font-size: 13px;
  font-weight: 600;
  margin: 8px 0 14px;
  line-height: 1.2;
  /* JUSTIFIED !important (the only one in this file): aad-custom.css carries
       .page-id-79/87/89 .elementor-widget-heading .elementor-heading-title
       { color:#385703 !important; }
     which paints every heading on this page olive and cannot be beaten by
     specificity. This label was a <p>, not a heading, so it escaped that rule
     before the conversion and was brown #423939. Restoring the original colour
     therefore requires matching !important. Delete this when aad-custom.css is
     merged and that blanket rule is scoped properly. */
  color: #423939 !important;
}


/* --------------------------------------------------------------------------
   2. Mobile menu — restore Home + Contact (Phase R, 2026-08-19)
   --------------------------------------------------------------------------
   REGRESSION FIX. The June build showed Home and Contact in the mobile
   overlay only, via a pair of `.aad-mobile-only` rules: one hiding them on the
   desktop bar, one re-showing them in the drawer. A post-handoff editing pass
   COMMENTED OUT the second rule (aad-custom.css lines 49–50) and deleted the
   two menu items, so mobile users had no menu path to Contact at all — only
   the header CTA button. The items are rebuilt as page objects (task 4); this
   restores the missing half of the CSS pair.

   The surviving desktop-hide rule in aad-custom.css line 47 is
     .main-header-bar .main-header-menu .menu-item.aad-mobile-only
       { display:none !important; }
   Astra's off-canvas drawer (.ast-mobile-popup-drawer) renders the SAME menu,
   and its markup sits inside .main-header-bar, so that !important rule catches
   the drawer copy too. Overriding it therefore also needs !important — scoped
   as tightly as possible to the drawer so the desktop bar is untouched.
   -------------------------------------------------------------------------- */
.ast-mobile-popup-drawer .main-header-menu .menu-item.aad-mobile-only,
.ast-mobile-popup-drawer .menu-item.aad-mobile-only,
.main-header-bar-navigation.toggle-on .menu-item.aad-mobile-only {
  display: block !important;
}

/* ==== PHASE B BLOCK START (Sullivan) ==== */
/* --------------------------------------------------------------------------
   3. BLOG CARD (Loop Item template) — Phase B, 2026-08-19
   --------------------------------------------------------------------------
   One card design, three consumers: the blog archive grid, the blog-single
   "related" grid, and the service-subpage "related services" grid. Elementor
   renders the Loop Item template inside `.e-loop-item`.

   Equal-height cards WITHOUT a magic pixel value: the loop item and the card
   root stretch to the grid row height, and the card body flex-grows so the
   Read More button can be pushed to the bottom with margin-top:auto.
   -------------------------------------------------------------------------- */
/* NOTE: do NOT use `.elementor-loop-container > *` here. Elementor prints the loop
   item's generated stylesheet as a <style id="loop-NNN"> element that is a DIRECT
   CHILD of .elementor-loop-container, so a universal child selector sets display:flex
   on the <style> tag and DUMPS THE WHOLE STYLESHEET ON SCREEN AS TEXT. Target the
   loop items themselves. */
.elementor-widget-loop-grid .e-loop-item {
  display: flex;
  align-items: stretch;
}
.elementor-widget-loop-grid .elementor-loop-container > style { display: none; }
.aad-card {
  width: 100%;
  height: 100%;
  box-shadow: 0 1px 3px rgba(66, 57, 57, .07);
  transition: box-shadow .25s ease, transform .25s ease;
}
.aad-card:hover {
  box-shadow: 0 10px 26px rgba(66, 57, 57, .13);
  transform: translateY(-3px);
}
.aad-card-body {
  flex: 1 1 auto;
}

/* Featured image: fixed 3:2 window, cover-cropped. The widget exposes no
   height/object-fit control on this Elementor version, so it is done here. */
.aad-card-img,
.aad-card-img .elementor-widget-container,
.aad-card-img a {
  display: block;
  width: 100%;
}
.aad-card-img img {
  display: block;
  width: 100%;
  aspect-ratio: 3 / 2;
  object-fit: cover;
  border-radius: 0;
}

/* Category chip — eyebrow language (uppercase, letterspaced), never a heading. */
.aad-card-cat .elementor-post-info__item,
.aad-card-cat .elementor-inline-item,
.aad-card-cat a {
  color: #385703;
  text-transform: uppercase;
  letter-spacing: 2px;
  text-decoration: none;
}
.aad-card-cat ul.elementor-inline-items {
  margin: 0;
  padding: 0;
}
/* post-info renders an icon SLOT even when the row's show_icon is 'no'; the slot keeps
   its left padding and, on some rows, a default glyph. Remove both. */
.aad-card-cat .elementor-icon-list-icon,
.aad-card-date .elementor-icon-list-icon,
.aad-single-cats .elementor-icon-list-icon,
.aad-single-meta .elementor-icon-list-icon { display: none !important; }
.aad-card-cat .elementor-icon-list-text,
.aad-card-date .elementor-icon-list-text,
.aad-single-cats .elementor-icon-list-text,
.aad-single-meta .elementor-icon-list-text { padding-left: 0; }

/* ERIC REVIEW ITEM 3 (2026-08-20): the card title size is set on the WIDGET
   (loop item 627, element aadbf9435a), not here. This rule declared 24px from
   Phase B onward and never once applied: a loop item prints its CSS inline as
   `.elementor-627 .elementor-element.elementor-element-aadbf9435a ...` at
   specificity (0,3,0), which beats `.aad-card-title .elementor-heading-title`
   (0,2,0), so the widget's aad_h3 global (31px) always won. Rather than escalate
   specificity here, the widget now carries an explicit 24px/20px. Only the
   colour + hover language stays in this file. */
.aad-card-title .elementor-heading-title {
  line-height: 1.25;
}
.aad-card-title a {
  color: #423939;
  text-decoration: none;
  transition: color .2s ease;
}
.aad-card-title a:hover { color: #385703; }

/* R3 (closing fixes 2026-08-20): the date was #423939 under `opacity:.8`, which paints
   the settled glyph at rgb(133,127,127) = 3.93:1 on white - under the 4.5:1 bar. The
   opacity layer is dropped rather than lightened further: at 18px the text is already
   antialiased well below its nominal colour, so a translucency layer on top is what
   pushed it under. Keeping the brand ink token at full strength is the smallest change
   that passes, and the date stays visually quiet because it is small and unemphasised. */
.aad-card-date .elementor-post-info__item,
.aad-card-date .elementor-inline-item {
  color: #423939;
}
.aad-card-date ul.elementor-inline-items { margin: 0; padding: 0; }

.aad-card-excerpt { margin-top: 2px; }
.aad-card-excerpt p { margin: 0; }

/* Read More — reuses the RETIRED .aad-form-dl button language (white / green
   text / 1px green border / 7px radius / uppercase, hover inverts). The old
   class is deliberately NOT resurrected; this is a fresh implementation of the
   same visual language, per the Phase B brief. Pushed to the card bottom so a
   row of cards ends level regardless of excerpt length. */
.aad-card-btn {
  margin-top: auto;
  padding-top: 16px;
}
/* Specificity note: Elementor's kit sheet carries
   `.elementor-widget-button .elementor-button { background: var(--e-global-color-accent) }`
   at 0-2-1, which beats a plain `.aad-card-btn .elementor-button` (0-2-0). Adding the
   widget class here matches it at 0-3-0 and wins on order WITHOUT !important. */
.elementor-widget-button.aad-card-btn .elementor-button,
.aad-card-btn .elementor-button {
  display: inline-block;
  background: #ffffff;
  color: #385703;
  border: 1px solid #385703;
  border-radius: 7px;
  padding: 11px 24px;
  font-family: 'halyard-display', sans-serif;
  font-size: 13px;
  font-weight: 400;
  text-transform: uppercase;
  letter-spacing: 2px;
  text-decoration: none;
  transition: background .2s ease, color .2s ease;
}
.elementor-widget-button.aad-card-btn .elementor-button:hover,
.elementor-widget-button.aad-card-btn .elementor-button:focus,
.aad-card-btn .elementor-button:hover,
.aad-card-btn .elementor-button:focus {
  background: #385703;
  color: #ffffff;
}

/* --------------------------------------------------------------------------
   4. BLOG ARCHIVE template — Phase B
   -------------------------------------------------------------------------- */
.aad-arch-head .elementor-heading-title { text-align: center; }
.aad-arch-intro { max-width: 720px; margin-left: auto; margin-right: auto; }
.aad-arch-intro p { margin: 0; }

/* Category filter = a real WP nav menu (crawlable, no JS filter plugin). */
.aad-arch-filter .elementor-nav-menu {
  justify-content: center;
  flex-wrap: wrap;
  gap: 6px 4px;
}
.aad-arch-filter .elementor-nav-menu a.elementor-item {
  text-transform: uppercase;
  letter-spacing: 2px;
  padding: 9px 18px;
  border: 1px solid #c9dc97;
  border-radius: 999px;
  color: #423939;
  transition: background .2s ease, color .2s ease, border-color .2s ease;
}
.aad-arch-filter .elementor-nav-menu a.elementor-item:hover,
.aad-arch-filter .elementor-nav-menu .current-menu-item > a.elementor-item {
  background: #385703;
  border-color: #385703;
  color: #ffffff;
}

/* Pagination — numbers + prev/next, matching the button language. */
.aad-arch-grid .elementor-pagination {
  margin-top: 44px;
  text-align: center;
}
.aad-arch-grid .elementor-pagination .page-numbers {
  display: inline-block;
  min-width: 40px;
  padding: 8px 12px;
  margin: 0 3px;
  border: 1px solid #c9dc97;
  border-radius: 7px;
  font-family: 'halyard-display', sans-serif;
  font-size: 14px;
  color: #423939;
  text-decoration: none;
  transition: background .2s ease, color .2s ease;
}
.aad-arch-grid .elementor-pagination .page-numbers:hover,
.aad-arch-grid .elementor-pagination .page-numbers.current {
  background: #385703;
  border-color: #385703;
  color: #ffffff;
}

/* --------------------------------------------------------------------------
   5. MIGRATION CTA BAND — Phase B
   --------------------------------------------------------------------------
   This band REPLACES the live site's repeated in-page CTA chrome ("Let's Get
   Started" / "Send Us a Message" / "Schedule an Appointment" / "No Dental
   Insurance?"), which is stripped from every migrated page and post. One CTA,
   at the end, pointing at /contact-us/.
   -------------------------------------------------------------------------- */
.aad-mig-cta .elementor-heading-title { text-align: center; }
.elementor-widget-button.aad-mig-btn .elementor-button,
.aad-mig-btn .elementor-button {
  display: inline-block;
  background: #385703;
  color: #ffffff;
  border: 1px solid #385703;
  border-radius: 7px;
  padding: 14px 34px;
  font-family: 'halyard-display', sans-serif;
  font-size: 14px;
  text-transform: uppercase;
  letter-spacing: 2px;
  text-decoration: none;
  transition: background .2s ease, color .2s ease;
}
.elementor-widget-button.aad-mig-btn .elementor-button:hover,
.elementor-widget-button.aad-mig-btn .elementor-button:focus,
.aad-mig-btn .elementor-button:hover,
.aad-mig-btn .elementor-button:focus {
  background: #ffffff;
  color: #385703;
}

/* --------------------------------------------------------------------------
   6. BLOG SINGLE template — Phase B
   --------------------------------------------------------------------------
   ASTRA WIDTH TRAP: on single posts Astra applies `.ast-narrow-container` and
   caps `.ast-container` at 750px. The Elementor "Full Width" page template
   (elementor_header_footer) removes the SIDEBAR but NOT that cap, so the whole
   Theme Builder template rendered inside a ~620px column. Release the cap only
   where one of our TB templates is actually rendering, so ordinary Astra
   pages/posts keep the theme's own measure.
   -------------------------------------------------------------------------- */
/* Match on the ELEMENTOR DOCUMENT, not on a body class. Body classes differ per
   template type (`elementor-template-full-width` appears for the archive/single-post
   documents but a service PAGE still carries `page-template-default`), so keying off
   them silently misses cases. `.ast-container:has()` targets exactly the containers that
   actually hold one of our Theme Builder documents. */
.ast-container:has(> .elementor-637),
.ast-container:has(> .elementor-641),
.ast-container:has(> .elementor-643),
.ast-container:has(> [data-elementor-type="archive"]),
.ast-container:has(> [data-elementor-type="single-post"]),
.ast-container:has(> [data-elementor-type="single-page"]) {
  max-width: 100%;
  padding-left: 0;
  padding-right: 0;
}
.ast-separate-container .site-main:has([data-elementor-type="archive"]),
.ast-separate-container .site-main:has([data-elementor-type="single-post"]),
.ast-separate-container .site-main:has([data-elementor-type="single-page"]) {
  padding: 0;
  background: transparent;
}
/* Fallback for browsers without :has() - keeps the old body-class rules in play.
   ⛔ NEVER let a star-slash sequence appear inside a CSS comment. A path glob
   written as slash-category-slash-star-slash does exactly that: it CLOSES the
   comment early, the remaining prose is parsed as CSS, and it silently eats the
   selector list of the NEXT rule. That is what broke single posts on 2026-08-20
   (see BUILD_STATE 22.12). Write globs as /category/<slug>/ instead.

   ERIC REVIEW ITEM 1 (2026-08-20): this fallback used to end at `.ast-container`,
   which is ALSO the class on the header's `.site-primary-header-wrap`. On /blog/,
   the category archives and post singles it therefore blew the HEADER out to the
   full viewport (logo x=0, nav x=1177, grid 1920) while ordinary pages kept the
   1240 grid (logo x=360, nav x=817) - the "logo and navigation fly out to the
   edges" Eric reported. Astra's own cap that this overrides is already scoped
   `.ast-narrow-container .site-content > .ast-container`, i.e. it never touched
   the header either; matching that `.site-content >` scope releases the content
   column exactly as before and leaves the header on the shared grid.
   Verified in-browser: logo 360 / nav 817 / button-right 1560 / grid 1240 on
   /blog/, /category/<slug>/ and post singles - identical to /about-us/. */
.single-post.elementor-template-full-width .site-content > .ast-container,
.archive.elementor-template-full-width .site-content > .ast-container,
.blog.elementor-template-full-width .site-content > .ast-container {
  max-width: 100%;
  padding-left: 0;
  padding-right: 0;
}


.aad-single-meta ul.elementor-inline-items { margin: 0; padding: 0; }
.aad-single-meta .elementor-post-info__item,
.aad-single-meta .elementor-post-info__item a {
  color: #423939;
  text-decoration: none;
  text-transform: uppercase;
  letter-spacing: 2px;
}
.aad-single-title .elementor-heading-title { max-width: 980px; }

.aad-single-hero-img img {
  display: block;
  border-radius: 12px;
  /* P2-1: the forced 1250x703 cover crop was removed here and re-applied ONLY to
     genuinely large sources, in the TOUCH-UP block at the end of this file.
     Nothing is sized in this rule, so an image can never be upscaled by it. */
}

/* Post body — one place that styles ALL migrated post copy. */
.aad-single-body {
  max-width: 820px;
  margin-left: auto;
  margin-right: auto;
}
.aad-single-body p,
.aad-single-body li {
  font-family: 'halyard-display', sans-serif;
  font-weight: 300;
  font-size: 20px;
  line-height: 1.55;
  color: #423939;
}
.aad-single-body h2 {
  font-family: 'ivyjournal', serif;
  font-weight: 400;
  font-size: 34px;
  line-height: 1.2;
  color: #385703;
  margin: 40px 0 14px;
}
.aad-single-body h3 {
  font-family: 'ivyjournal', serif;
  font-weight: 400;
  font-size: 26px;
  line-height: 1.25;
  color: #385703;
  margin: 30px 0 10px;
}
.aad-single-body h4 {
  font-family: 'halyard-display', sans-serif;
  font-weight: 400;
  font-size: 20px;
  letter-spacing: 1px;
  color: #423939;
  margin: 24px 0 8px;
}
.aad-single-body ul,
.aad-single-body ol { padding-left: 22px; margin: 0 0 20px; }
.aad-single-body li { margin-bottom: 8px; }
.aad-single-body a { color: #385703; text-decoration: underline; }
.aad-single-body figure { margin: 28px 0; }
.aad-single-body figure img {
  display: block;
  /* D5: never upscale. `width:100%` used to stretch a 175px graphic to 1250px
     (7.14x) - see the FIX PASS block at the end of this file. */
  max-width: 100%;
  width: auto;
  height: auto;
  border-radius: 12px;
}
.aad-single-body blockquote {
  margin: 28px 0;
  padding: 4px 0 4px 24px;
  border-left: 3px solid #c9dc97;
  font-style: normal;
}

/* Author box */
.aad-single-author {
  border-top: 1px solid #e1edec;
  border-bottom: 1px solid #e1edec;
  padding: 28px 0;
}
.aad-single-author .elementor-author-box__name {
  font-family: 'ivyjournal', serif;
  font-weight: 400;
  font-size: 22px;
  color: #385703;
}
.aad-single-author .elementor-author-box__bio {
  font-family: 'halyard-display', sans-serif;
  font-weight: 300;
  font-size: 18px;
  line-height: 1.45;
  color: #423939;
}
.aad-single-author .elementor-author-box__avatar img { border-radius: 50%; }

/* Prev / next */
.aad-single-nav .post-navigation__prev--label,
.aad-single-nav .post-navigation__next--label {
  text-transform: uppercase;
  letter-spacing: 2px;
  font-size: 12px;
  color: #385703;
}
.aad-single-nav .post-navigation__prev--title,
.aad-single-nav .post-navigation__next--title {
  font-family: 'ivyjournal', serif;
  font-size: 18px;
  color: #423939;
}
.aad-single-nav a { text-decoration: none; }

.aad-related-head .elementor-heading-title { text-align: center; }

/* --------------------------------------------------------------------------
   7. SERVICE SUBPAGE template — Phase B
   -------------------------------------------------------------------------- */
/* FULL-BLEED HERO. Astra caps .ast-container at 1200px even on the full-width
   Elementor template, so a `content_width:full` container still stops at the grid.
   Break out with the standard viewport-width trick (no !important needed). */
.aad-svc-hero-band {
  position: relative;
  background-size: cover;
  background-position: center;
  background-repeat: no-repeat;
  /* Elementor sets --width on .e-con and Astra caps .ast-container at 1200px, so the
     band stops at the grid. Override the custom property (which is what Elementor's own
     layout reads) AND break out of the container in one go. */
  --width: 100vw;
  width: 100vw;
  max-width: 100vw;
  margin-left: calc(50% - 50vw);
  margin-right: calc(50% - 50vw);
}
/* The hero sits on a photo, so ALL its text is white. The eyebrow needs an explicit
   colour because aad-custom.css sets `.aad-eyebrow` to brown #423939 site-wide at a
   specificity this cannot out-rank by class alone. */
/* JUSTIFIED !important: aad-custom.css sets
   `.aad-eyebrow .elementor-heading-title { color:#423939 !important }` site-wide.
   An !important declaration can only be beaten by another !important, regardless of
   load order or specificity. The hero eyebrow sits on a dark-overlaid photo and MUST
   be white to be legible. Remove this when aad-custom.css is merged and de-importanted. */
.aad-svc-hero-band .aad-eyebrow .elementor-heading-title,
.aad-svc-hero-band .aad-svc-eyebrow .elementor-heading-title {
  color: #ffffff !important;
}
.aad-svc-hero-band .aad-svc-title .elementor-heading-title {
  color: #ffffff;
}
/* Keep the hero's own content on the 1250 grid even though the band is full-bleed. */
.aad-svc-hero-inner {
  width: 100%;
  max-width: 1250px;
  margin-left: auto;
  margin-right: auto;
}
.aad-svc-hero-band .elementor-widget-theme-post-excerpt,
/* D7: the hero sub-line is now a `heading` widget (H2) rather than
   theme-post-excerpt - see the FIX PASS block. Both are listed so the rule keeps
   working whichever widget renders it. */
.aad-svc-hero-band .aad-svc-hero-excerpt {
  color: #ffffff;
}
.aad-svc-hero-inner {
  position: relative;
  z-index: 2;
}
.aad-svc-hero-excerpt {
  max-width: 720px;
}
.aad-svc-hero-excerpt p,
.aad-svc-hero-excerpt .elementor-heading-title {
  color: #ffffff;
  margin: 0;
}

/* Body copy — same rules as the blog single so migrated service copy and
   migrated post copy read identically. */
.aad-svc-body {
  max-width: 860px;
  margin-left: auto;
  margin-right: auto;
}
.aad-svc-body p,
.aad-svc-body li {
  font-family: 'halyard-display', sans-serif;
  font-weight: 300;
  font-size: 20px;
  line-height: 1.55;
  color: #423939;
}
.aad-svc-body h2 {
  font-family: 'ivyjournal', serif;
  font-weight: 400;
  font-size: 34px;
  line-height: 1.2;
  color: #385703;
  margin: 40px 0 14px;
}
.aad-svc-body h3 {
  font-family: 'ivyjournal', serif;
  font-weight: 400;
  font-size: 26px;
  line-height: 1.25;
  color: #385703;
  margin: 30px 0 10px;
}
.aad-svc-body h4 {
  font-family: 'halyard-display', sans-serif;
  font-weight: 400;
  font-size: 20px;
  letter-spacing: 1px;
  color: #423939;
  margin: 24px 0 8px;
}
.aad-svc-body ul,
.aad-svc-body ol { padding-left: 22px; margin: 0 0 20px; }
.aad-svc-body li { margin-bottom: 8px; }
.aad-svc-body a { color: #385703; text-decoration: underline; }
.aad-svc-body figure { margin: 28px 0; }
.aad-svc-body figure img {
  display: block;
  /* D5: never upscale (see the FIX PASS block at the end of this file). */
  max-width: 100%;
  width: auto;
  height: auto;
  border-radius: 12px;
}

/* --------------------------------------------------------------------------
   8. SERVICES PAGE (79) — line items become links — Phase B
   --------------------------------------------------------------------------
   The 4 service cards' bullet lists are `icon-list` widgets whose items now
   carry links to their subpages (or to a General Dentistry anchor). Elementor
   wraps a linked item's text in an <a>.

   ERIC REVIEW ITEM 7 (2026-08-20) REVERSES the original Phase-B decision here.
   That decision was "keep it visually identical to the unlinked text so the
   cards do not suddenly read as a wall of links" - Eric's review asks for the
   opposite: a linked item must be visibly distinguishable as a link. So the
   underline moves from :hover onto the resting state, and this is the rule that
   changes rather than a new one being layered on top (a later, more specific
   `text-decoration: none` here would beat any appended override).

   Scoping to `a` does the whole job with no per-item classes: of the 36 line
   items, 33 are anchors and 3 are deliberately plain text (Full Mouth
   Reconstruction / Gum lifts / Gum sculpting - no live page exists,
   BUILD_STATE 15.5), so the unlinked three cannot match. It covers the 9
   #anchor jumps into General Dentistry and the external orthogum.com link
   equally, because those are anchors too. A hairline rule held off the baseline
   keeps 20px halyard from reading as struck through inside the bubbles.
   -------------------------------------------------------------------------- */
.aad-svc-bullets-wrap ul.elementor-icon-list-items .elementor-icon-list-item > a {
  color: inherit;
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-underline-offset: 3px;
  text-decoration-color: rgba(66, 57, 57, .38);
  transition: color .18s ease, text-decoration-color .18s ease;
}
.aad-svc-bullets-wrap ul.elementor-icon-list-items .elementor-icon-list-item > a:hover,
.aad-svc-bullets-wrap ul.elementor-icon-list-items .elementor-icon-list-item > a:focus {
  color: #385703;
  text-decoration-color: #385703;
}

/* --------------------------------------------------------------------------
   9. RESPONSIVE — Phase B
   -------------------------------------------------------------------------- */
@media (max-width: 1024px) {
  .aad-single-body,
  .aad-svc-body { max-width: 100%; }
  /* item 3: mobile size also lives on the widget (typography_font_size_mobile). */
}

@media (max-width: 767px) {
  .aad-arch-filter .elementor-nav-menu a.elementor-item {
    padding: 8px 14px;
    font-size: 13px;
  }
  .aad-single-body p,
  .aad-single-body li,
  .aad-svc-body p,
  .aad-svc-body li { font-size: 18px; }
  .aad-single-body h2,
  .aad-svc-body h2 { font-size: 27px; margin-top: 30px; }
  .aad-single-body h3,
  .aad-svc-body h3 { font-size: 22px; }
  .aad-card-img img { aspect-ratio: 16 / 9; }
  .aad-mig-btn .elementor-button { padding: 13px 26px; }
}
/* ==== PHASE B BLOCK END ==== */

/* ==== PHASE C BLOCK START (Sullivan, finisher) ==== */
/* --------------------------------------------------------------------------
   10. Long raw URLs in migrated body copy
   --------------------------------------------------------------------------
   29 of the 81 migrated posts carry raw, unbracketed citation URLs in the
   client's original 2016-era copy (e.g. a full nidcr.nih.gov path). Migrated
   VERBATIM per the recipe, so the copy is not ours to rewrite. A URL is one
   unbreakable token, so at 390px a single <a> measured up to 701px wide and
   pushed the document 351px past the viewport.

   Diagnosed, not assumed: at 390 the ONLY offending element on each flagged
   post is one <a> inside .elementor-widget-theme-post-content with
   overflow-wrap:normal. Scoped to links in migrated body content only, so
   headings, nav, buttons and every non-migrated page are untouched.
   `anywhere` (not `break-word`) because it also lets the element SHRINK below
   the long token's width, which is what actually clears the overflow.
   -------------------------------------------------------------------------- */
.elementor-widget-theme-post-content a,
.aad-single-body a,
.aad-svc-body a {
  overflow-wrap: anywhere;
}
/* ==== PHASE C BLOCK END ==== */

/* ==== FIX PASS BLOCK START (Sullivan, 2026-08-19 — Quincy defects D5/D6/D7) ==== */
/* --------------------------------------------------------------------------
   11. D5 — body images: no upscaling, and the 70/30 copy/media pattern
   --------------------------------------------------------------------------
   TWO parts.

   (a) NO UPSCALING (the defect). `.aad-single-body figure img{width:100%}` and its
       `.aad-svc-body` twin forced EVERY body image to the 1250px content column
       regardless of its real file size. 95 migrated body images are under 800px
       wide; a 175px winter-specials graphic was painted at 1250px (7.14x) and a
       450px composite-fillings photo at 2.78x — visibly soft. The same files on
       ddsdenver.com render 1:1. Replaced with `max-width:100%; width:auto` so an
       image paints at its natural size and only ever scales DOWN.

   (b) THE 70/30 COPY/MEDIA PATTERN (Eric's requested layout change).
       Built from what the LIVE site actually does, measured across the 96 cached
       source pages rather than assumed — and the source uses TWO different shapes:

         * 61 of 70 live body images are FLOATS: `<img class="alignright|alignleft">`
           sitting INSIDE the first <p>, with the copy wrapping around them. This is
           the blog-post pattern (e.g. /dry-mouth-nothing-to-spit-at/, 300px image
           floated right at ~30% with copy filling the remaining ~70%).
         * 4 are true two-column rows — `<div class="col-md-8">copy</div>
           <div class="col-md-4 text-center">img</div>` — and they are all on
           /service/technology/, the flagship service page.

       So BOTH are implemented. `.aad-copy-media` is the explicit two-column row
       (66.7/33.3 = col-md-8/col-md-4, top-aligned, image centred in its column).
       `.aad-cm-float` is the float form used for the many blog cases, which gives
       the same ~70/30 optical split while letting short copy wrap naturally
       instead of leaving a tall empty column beside it.

       Both stack to a single column at the tablet breakpoint (copy first, then the
       image at natural size) — never a 30%-wide image on a phone.
   -------------------------------------------------------------------------- */
.aad-copy-media {
  display: flex;
  align-items: flex-start;
  gap: 32px;
  margin: 28px 0;
}
.aad-copy-media > .aad-cm-copy {
  flex: 1 1 68%;
  min-width: 0;               /* let long words/URLs wrap instead of stretching the row */
}
.aad-copy-media > .aad-cm-media {
  flex: 0 0 30%;
  max-width: 30%;
  display: flex;
  flex-direction: column;
  align-items: center;        /* live site uses .text-center in the media column */
  gap: 12px;
}
.aad-copy-media > .aad-cm-copy > *:first-child { margin-top: 0; }
.aad-copy-media > .aad-cm-copy > *:last-child { margin-bottom: 0; }
.aad-copy-media .aad-cm-media figure { margin: 0; }
.aad-copy-media .aad-cm-media figure img {
  max-width: 100%;
  width: auto;
  height: auto;
  border-radius: 12px;
}

/* Float form — the blog-post pattern. The figure is capped at 30% of the measure
   so the copy keeps a readable ~70%, and never below its natural width. */
.aad-single-body figure.aad-cm-float,
.aad-single-body figure.aad-cm-float-left,
.aad-svc-body figure.aad-cm-float,
.aad-svc-body figure.aad-cm-float-left {
  max-width: 30%;
}
.aad-single-body figure.aad-cm-float,
.aad-svc-body figure.aad-cm-float {
  float: right;
  margin: 6px 0 20px 32px;
}
.aad-single-body figure.aad-cm-float-left,
.aad-svc-body figure.aad-cm-float-left {
  float: left;
  margin: 6px 32px 20px 0;
}
.aad-single-body figure.aad-cm-float img,
.aad-single-body figure.aad-cm-float-left img,
.aad-svc-body figure.aad-cm-float img,
.aad-svc-body figure.aad-cm-float-left img {
  max-width: 100%;
  width: auto;
  height: auto;
}
/* Headings must NOT clear the float — ASTRA ships `h1,h2,h3,h4,h5,h6{clear:both}`
   globally (main.min.css), which would drop every section heading below the image.
   The live pages fake their section headings with <p><strong>...</strong></p>, so the
   copy wraps CONTINUOUSLY past them and beside the image. Our migration promotes those
   to real H2/H3 (correct for the outline), so the theme's blanket clear has to be
   undone INSIDE migrated body copy only — a 450px image next to two short paragraphs
   would otherwise push the next heading down a full image height. */
.aad-single-body h1, .aad-single-body h2, .aad-single-body h3,
.aad-single-body h4, .aad-single-body h5, .aad-single-body h6,
.aad-svc-body h1, .aad-svc-body h2, .aad-svc-body h3,
.aad-svc-body h4, .aad-svc-body h5, .aad-svc-body h6 { clear: none; }

/* The body wrapper itself DOES clear, so a float can never bleed out of the body
   copy into the related-posts / CTA bands below. */
.aad-single-body::after,
.aad-svc-body::after { content: ""; display: block; clear: both; }

@media (max-width: 1024px) {
  .aad-copy-media { display: block; }
  .aad-copy-media > .aad-cm-media {
    max-width: 100%;
    margin-top: 20px;
  }
  .aad-copy-media .aad-cm-media figure { text-align: center; }
  .aad-copy-media .aad-cm-media figure img { margin-left: auto; margin-right: auto; }

  /* floats stop floating: full-width block, image at natural size, centred */
  .aad-single-body figure.aad-cm-float,
  .aad-svc-body figure.aad-cm-float,
  .aad-single-body figure.aad-cm-float-left,
  .aad-svc-body figure.aad-cm-float-left {
    float: none;
    max-width: 100%;
    margin: 24px auto;
    text-align: center;
  }
  .aad-single-body figure.aad-cm-float img,
  .aad-svc-body figure.aad-cm-float img { margin-left: auto; margin-right: auto; }
}

/* --------------------------------------------------------------------------
   12. D6 — H1 line-height on the three new templates
   --------------------------------------------------------------------------
   The archive (637), blog single (641) and service subpage (643) rendered their
   H1 at line-height 1.4 (75.6px @54px) while every established page on the site
   inherits the theme's `h1{line-height:1.2}` (64.8px) — a 10.8px-per-line drift
   visible whenever a new page sits next to an existing one.
   The 1.4 comes from the Kit's `aad_h1` global typography applied by the widget,
   so it is corrected here for these three templates' hero headings only.
   -------------------------------------------------------------------------- */
/* Specificity note: the competing rule is ASTRA's dynamic CSS, not Elementor -
   `.elementor-widget-heading h1.elementor-heading-title{line-height:1.4em}` (0,2,2).
   (Astra also ships `h1{line-height:1.2em}` at (0,1,0), which is why every
   NON-Elementor page on this site already renders 1.2 - the drift only ever showed
   up on Elementor-built headings.) aad-migration.css loads last, but last-wins only
   settles ties, so the selector below matches that structure and adds the widget's
   own class to land at (0,3,2) - no !important needed. */
.aad-arch-title.elementor-widget-theme-archive-title h1.elementor-heading-title,
.aad-single-title.elementor-widget-theme-post-title h1.elementor-heading-title,
.aad-svc-title.elementor-widget-theme-post-title h1.elementor-heading-title {
  line-height: 1.2;
}

/* --------------------------------------------------------------------------
   13. D7 — the hero sub-line is an H2 (semantics only, zero visual change)
   --------------------------------------------------------------------------
   Service pages ran H1 -> H3 with no H2, because the live page's "lined" H2
   tagline was migrated into the hero as an excerpt/subtitle <div>. The element is
   re-tagged to <h2> in the template so the outline is legal; these rules make the
   H2 render EXACTLY as the excerpt div did (the browser's own h2 defaults for
   size/weight/margin are what would otherwise change the look).
   -------------------------------------------------------------------------- */
.aad-svc-hero-excerpt h2.elementor-heading-title {
  /* measured off the outgoing excerpt <div> before the swap, so the H2 is
     pixel-identical: halyard-display 20px / 300 / 24px, white, no margin. */
  font-family: inherit;
  font-size: inherit;
  font-weight: inherit;
  line-height: inherit;
  letter-spacing: inherit;
  color: inherit;
  margin: 0;
}
/* ==== FIX PASS BLOCK END ==== */

/* ==== TOUCH-UP BLOCK START (Sullivan, 2026-08-20 — Quincy P2-1 / P2-2) ==== */

/* --------------------------------------------------------------------------
   14. P2-1 — blog-single featured images must never upscale
   --------------------------------------------------------------------------
   THE DEFECT. The single template painted every featured image into a fixed
   1250x703 slot (width:100% + aspect-ratio:16/9 + object-fit:cover). Measured
   across all 84 migrated posts, 78 sources are SMALLER than the 1250px column
   (13 are 400px, 15 are 420px, 36 are 450px, 10 are 600px), so almost every post
   ran 2.1x - 3.1x. Two visible symptoms:
     1. softness/blur, worst on images with lettering baked into the pixels;
     2. `cover` cropping the top and bottom off the 45 near-SQUARE sources -
        "Smile, It's Good For You" rendered as a truncated "Smili...".
   No larger rendition exists to re-serve: these are the original files from the
   live site (verified - the -1024x, -768x and -scaled variants 404).

   Same class as D5 (section 12), whose scope was BODY images only; heroes were
   never touched by it. This is the hero half, built the same way.

   THE RULE. Nothing here forces a width, so an image paints at its natural size
   and `max-width:100%` only ever scales it DOWN (mobile). Height follows the real
   aspect ratio, so no crop can eat baked-in wording.

   Large sources keep the designed full-bleed 16:9 hero via .aad-hero-wide, a body
   class set by the aad-migration mu-plugin (CSS cannot branch on intrinsic image
   size). Threshold = the 1250px column; 6 posts qualify, of which 4 are the brand
   fallback asset (2000x1123) - so the designed treatment survives exactly where
   the pixels support it.
   -------------------------------------------------------------------------- */
.aad-single-hero-img img {
  max-width: 100%;
  height: auto;
  margin-inline: auto;      /* natural-size images sit centered in the column */
}

/* Large enough to fill the column: keep the approved 16:9 full-bleed crop.
   These only ever scale DOWN (2000 -> 1250 = 0.63x), so they stay sharp. */
body.aad-hero-wide .aad-single-hero-img img {
  width: 100%;
  aspect-ratio: 16 / 9;
  object-fit: cover;
}

/* --------------------------------------------------------------------------
   15. P2-2 — the phone number is a tel: link (zero visual change)
   --------------------------------------------------------------------------
   The "call us" icon-box rendered the number as plain description text, so it was
   not tappable on mobile - for a practice whose primary conversion is a phone
   call. The number is now wrapped in <a href="tel:+13032460100">.

   These rules exist ONLY to make the anchor invisible as an anchor: it must
   inherit the description's colour and type exactly, with no underline, because
   the surrounding design has no underlined links in that block. `color:inherit`
   also keeps it correct against both the light and dark card variants.
   -------------------------------------------------------------------------- */
.elementor-icon-box-description a[href^="tel:"],
.aad-tel-plain {
  color: inherit;
  font: inherit;
  letter-spacing: inherit;
  text-decoration: none;
}

/* The in-copy instances sit inside migrated body text whose links ARE underlined
   and green by design (.aad-single-body a / .aad-svc-body a). A phone number in a
   sentence should read like the rest of that sentence, not like a link. */
.aad-single-body a.aad-tel-plain,
.aad-svc-body a.aad-tel-plain,
.elementor-widget-text-editor a.aad-tel-plain {
  color: inherit;
  text-decoration: none;
}

/* ==== TOUCH-UP BLOCK END ==== */

/* ==== AUDREY FIX BLOCK START (Sullivan, 2026-08-20 - AUDREY_REVIEW-2026-08-20) ==== */

/* --------------------------------------------------------------------------
   16. P1-1 - the Services bullet bubbles must CONTAIN their longest list
   --------------------------------------------------------------------------
   THE DEFECT. "Oral Cancer & HPV Screenings" painted 48px BELOW its white box, on
   the beige, colliding with the next section's zone. TWO bubbles were affected, not
   one: General Dentistry (13 items, needs 344px) and Specialty Services (13 items,
   318px) - both inside a bubble hard-coded to `height:270px` in aad-custom.css,
   sized in June for the longest list of the day (10 items).

   MEASURED, the tablet range was far worse than the 1920 that was reported: at
   922-1024px the list collapses to ONE column, so both 13-item bubbles need 546px
   and were overflowing their 270px box by 250px.

   ROOT CAUSE of the tablet half. aad-custom.css already carries
   `height:auto !important; min-height:270px !important` for 769-1024px, and it DOES
   win the cascade - yet the box still computed to exactly 270px. The reason is in
   this stylesheet, not that one: section 1a gives the inner
   `.aad-svc-bullets-wrap > .elementor-widget-container` a `height:100%`. Against a
   parent whose only definite size is its own `min-height`, that percentage resolves
   circularly and pins the flex container at the minimum, so the auto-height rule
   could never take effect. Releasing the inner height is what makes `height:auto`
   mean anything.

   THE RULE, in the June language. The four bubbles are meant to "start AND end at
   the same vertical spot" (aad-custom.css comment). That is preserved exactly: one
   shared `min-height` per breakpoint keeps all four boxes identical and level, while
   `height:auto` means any future list that outgrows the box GROWS it instead of
   spilling onto the beige. Values are the measured worst case across a 17-width
   sweep, not estimates: 370px desktop (the true peak is at ~1025-1150px, where the
   narrower column wraps a label - NOT at 1920), and 572px for the single-column
   tablet range (peak at 769px). Below 769px the cards stack one per row, so each
   bubble sizes to its own content and no shared height applies.

   Verified 1920/1440/1280/1150/1100/1060/1025/1024/1000/922/900/800/769/768/600/390/360:
   every bubble contains its longest item (max spill -26px, i.e. 26px of headroom),
   all four heights identical per breakpoint, two distinct tops and two distinct
   bottoms (= the two rows, exactly level), zero horizontal scroll.
   -------------------------------------------------------------------------- */
.aad-svc-bullets-wrap {
  height: auto !important;
  min-height: 370px !important;
}

/* Release the circular percentage described above; without this, `height:auto`
   is inert and the box stays pinned at its min-height. */
.aad-svc-bullets-wrap > .elementor-widget-container {
  height: auto !important;
}

/* Single-column list range: same rule, the taller shared minimum. */
@media (min-width: 769px) and (max-width: 1024px) {
  .aad-svc-bullets-wrap {
    height: auto !important;
    min-height: 572px !important;
  }
}

/* Cards are one-per-row here, so a shared height would only add dead space. */
@media (max-width: 768px) {
  .aad-svc-bullets-wrap {
    height: auto !important;
    min-height: 0 !important;
  }
}

/* --------------------------------------------------------------------------
   17. P1-2 - suppress the hero when it duplicates a body image
   --------------------------------------------------------------------------
   59 of 84 posts painted the same image FILE twice within one screen: the template
   hero, then the identical graphic floated into the opening copy (back-to-back at
   390). The body copy is the one that carries the source's context - it is floated
   beside the paragraph it illustrates - so the HERO is the duplicate to remove.

   `aad-hero-dupe` is set by the aad-migration mu-plugin, which compares attachment
   file BASENAMES (not URLs, which differ by rendition). See that file for the
   detection rules and scope guards. Hiding the band in CSS keeps the template and
   all post content untouched - the hero is one line away from coming back.

   The whole band goes, not just the <img>, so its vertical rhythm goes with it and
   the title band meets the body copy directly.
   -------------------------------------------------------------------------- */
body.aad-hero-dupe .aad-single-imgband {
  display: none;
}

/* --------------------------------------------------------------------------
   18. P1-3 - no post date on SERVICE sibling cards
   --------------------------------------------------------------------------
   Loop card 627 is shared by the blog archive, the blog single's "More from our
   blog", and the service template's "Other services we offer". On a blog card the
   date is correct; on an evergreen service page it printed "August 19, 2026" - the
   MIGRATION date - on every sibling card of all 18 service pages. Meaningless for a
   service, permanently stale, and it leaks build timing to the client.

   Scoped by `.aad-svc-related`, which template 643 puts on its loop-grid and which
   appears on NOTHING else (verified against templates 627/637/641: the blog single's
   related grid carries `.aad-related-grid` WITHOUT it). So blog cards keep their
   dates and only the service context loses them - no card variant needed.
   -------------------------------------------------------------------------- */
.aad-svc-related .aad-card-date {
  display: none;
}

/* --------------------------------------------------------------------------
   19. P2-4 - READ MORE pinned to the bottom of every card
   --------------------------------------------------------------------------
   Card OUTER edges were already level (grid stretch verified at 3/2/1 columns), but
   the buttons ragged by up to ~92px within a row because the body column packs to
   its content. The June bubble discipline pins content bottoms too.

   `margin-top:auto` on the button inside the flex column absorbs the slack - the
   same mechanism aad-custom.css already uses to bottom-pin the service bubbles.
   Nothing about the card's outer geometry changes.
   -------------------------------------------------------------------------- */
.aad-card .aad-card-body {
  flex-grow: 1;             /* the body column fills the stretched card */
}

.aad-card .aad-card-btn {
  margin-top: auto;         /* ...and the button sinks to its bottom */
}

/* --------------------------------------------------------------------------
   20. P2-6 - Patient Info WELCOME band, balanced
   --------------------------------------------------------------------------
   Reported as 74px above the eyebrow vs 109px below the copy. Measured, the widget
   BOXES are already symmetrical (74/74, band padding 64/64 intact) - the asymmetry
   is in the painted copy: the single <p> inside `.aad-welcome-body` carries a 35px
   bottom margin (theme paragraph rhythm) that used to be absorbed by the forms grid
   beneath it. With that grid deleted the 35px became trailing dead space, which is
   exactly the 109 - 74 that was measured.

   Dropping the margin on the LAST paragraph only keeps normal spacing between
   paragraphs if this copy ever grows, and is scoped to this band so no other
   text-editor rhythm changes.
   -------------------------------------------------------------------------- */
.aad-welcome-body p:last-child {
  margin-bottom: 0;
}

/* --------------------------------------------------------------------------
   21. P2-7 - a section-final float must not bleed into the next section
   --------------------------------------------------------------------------
   On /service/general-dentistry/ the Root Canal illustration (`rootcanals.png`)
   floated right out of "Root Canals & Extractions" and painted beside "Mouthguards
   & Sportsguards" (image 2074-2302 vs the Mouthguards H3 at 2068). DOM order was
   correct; nothing cleared the float, and the sub-service headings render with
   `clear:none`.

   TWO parts, because containment alone left a hole.

   (a) CLEARING - the general protection. Every sub-service heading in a migrated body
   clears preceding floats, so no float can ever escape the section that owns it. This
   guards all 18 service pages and every migrated post, not just the page where the
   collision happened to be visible.

   (b) UN-FLOATING THIS ONE IMAGE - because clearing alone just moved the problem: the
   Root Canals section is a heading plus ONE short paragraph that ends above the image,
   so the float had nothing to wrap and simply left a large empty gutter beside it.
   Measured at 1920, a genuine 70/30 float has 76-92% of its height covered by adjacent
   copy; this one had ZERO. The live source agrees - it carries no align class there
   (ddsdenver.com line 641, a plain centred block).

   The class swap (aad-cm-float -> aad-cm-center) was made in CONTENT on page 872 only,
   scoped by filename, because CSS cannot test "is there copy beside this". A census
   first confirmed the blast radius: 9 section-final floats exist, but 6 are the
   winter-specials product rows (verified 76-92% coverage - real 70/30 rows built in
   19.5) and 2 more genuinely wrap. Only this one was hollow, so only this one changed;
   the other 55 wrapped floats and all 6 product rows are untouched.
   -------------------------------------------------------------------------- */
.aad-svc-body h2,
.aad-svc-body h3 {
  clear: both;
}

/* Plain centred block - matches the live source's treatment.
   NOTE the <img> inside is display:block (from the body-image rules in section 14),
   so `text-align:center` on the figure does NOT move it - measured, it sat flush left
   with a 753px gutter. The image needs its own auto side margins. */
.aad-cm-center {
  float: none !important;
  text-align: center;
}

.aad-cm-center img {
  display: block;
  margin-left: auto;
  margin-right: auto;
}

/* The caption travels with the image. */
.aad-cm-center figcaption {
  text-align: center;
}

/* --------------------------------------------------------------------------
   22. P3-8 - uppercase micro-controls are halyard, not ivyjournal
   --------------------------------------------------------------------------
   The archive filter chips computed to `18px ivyjournal` with 2px tracking. In the
   June system every uppercase micro-control is halyard (buttons 14px, eyebrows
   16-18px); ivyjournal is the display serif for headings only. The chips are built
   on a nav-menu widget, so they INHERITED nav typography rather than being chosen.

   Set to the button voice - halyard 400 at 15px with the same 2px tracking - so the
   chips read as controls and match the pagination directly below them.

   Scoped to `.aad-arch-filter` (the class template 637 puts on the nav-menu widget)
   and to the `--main` nav specifically: this widget also emits a `--dropdown` copy
   for mobile, which Elementor already renders in halyard 14px, so styling both would
   silently resize the mobile control. Verified against the computed styles of both
   navs before writing.
   -------------------------------------------------------------------------- */
.aad-arch-filter .elementor-nav-menu--main .elementor-item {
  font-family: 'halyard-display', sans-serif;
  font-size: 15px;
  font-weight: 400;
  letter-spacing: 2px;
}

/* --------------------------------------------------------------------------
   23. P3-10 - a disabled pagination control must LOOK disabled
   --------------------------------------------------------------------------
   On page 1, "Previous" renders as a <span class="page-numbers prev"> (WP emits a
   span, not an anchor, when there is nowhere to go) but was styled identically to
   the live "Next" anchor - same `#423939`, no dimming, no cursor cue. Nothing told
   the user it was inert.

   Targeting `span.page-numbers` (not `.prev`) covers the disabled NEXT on the last
   page by the same rule. `.current` is excluded - it is also a span, but it is a
   state marker, not a dead control. Muted rather than hidden so the control row
   keeps its shape across pages.
   -------------------------------------------------------------------------- */
.aad-pagination span.page-numbers:not(.current),
.elementor-pagination span.page-numbers:not(.current) {
  opacity: .4;
  cursor: default;
}

/* --------------------------------------------------------------------------
   24. P3-11 - service related band on the section rhythm
   --------------------------------------------------------------------------
   The band ran 48px above its heading vs 64px below the grid. Its neighbour, the CTA
   band, is a clean 72/72. Squared to 64/64 - matching the 64 the band already had
   below the grid, and the house 64 rhythm used by the archive header band - so this
   is the smallest change that makes the band symmetrical without disturbing the CTA
   band beside it.

   NOTE the padding lives on the container's INNER wrapper (`.e-con-inner`, 48/64),
   not on `.aad-related-band` itself, which computes 0/0. Setting it on the band
   would ADD to the inner padding rather than replace it (measured: that produced
   112/128). Target the inner box.
   -------------------------------------------------------------------------- */
.aad-related-band > .e-con-inner {
  padding-top: 64px;
  padding-bottom: 64px;
}

/* ==== AUDREY FIX BLOCK END ==== */


/* ===== ERIC REVIEW BLOCK (Sullivan 2026-08-20) =============================
   Items 5 and 7 of Eric's staging review. Items 1 and 3 are edits in place
   above; items 2, 4 and 6 needed no CSS.
   ========================================================================== */

/* --------------------------------------------------------------------------
   25. ITEM 5 - post categories moved to the FOOT of the post, and linked.
   --------------------------------------------------------------------------
   The top meta row on template 641 now carries the date only; a second
   post-info widget (`aad-single-cats`) sits at the end of the body band with
   `link: yes`, so each term is a real anchor to its own archive. Styled in the
   site's quiet meta voice - halyard, uppercase, letterspaced - so it reads as
   the same language as the archive filter chips rather than as body copy.
   -------------------------------------------------------------------------- */
.aad-single-cats {
  margin-top: 36px;
  padding-top: 22px;
  border-top: 1px solid rgba(66, 57, 57, .16);
}
.aad-single-cats ul.elementor-inline-items {
  margin: 0;
  padding: 0;
  align-items: baseline;
}
.aad-single-cats .elementor-icon-list-item,
.aad-single-cats .elementor-inline-item {
  margin: 0;
}
/* The aad_eyebrow global carries family + size only; the uppercase/letterspaced
   VOICE is painted here, exactly as `.aad-card-cat` does it above, so the foot
   row reads as the same meta language as the archive chips. */
.aad-single-cats .elementor-post-info__item,
.aad-single-cats .elementor-inline-item,
.aad-single-cats .elementor-icon-list-text {
  font-size: 15px;
  text-transform: uppercase;
  letter-spacing: 2px;
  color: #423939;
}
/* the label that precedes the terms - see the mu-plugin's `aad_cats_label` */
.aad-single-cats .elementor-icon-list-text { padding-left: 0; }
.aad-single-cats a {
  color: #385703;
  text-decoration: none;
  border-bottom: 1px solid rgba(56, 87, 3, .35);
  padding-bottom: 1px;
  transition: color .2s ease, border-color .2s ease;
}
.aad-single-cats a:hover,
.aad-single-cats a:focus {
  color: #423939;
  border-bottom-color: rgba(66, 57, 57, .6);
}

/* --------------------------------------------------------------------------
   26. ITEM 7 - the linked Services line items read as links.
   --------------------------------------------------------------------------
   36 line items across the four bubbles; 33 are anchors, 3 are deliberately
   plain text (Full Mouth Reconstruction / Gum lifts / Gum sculpting - no live
   page exists, BUILD_STATE 15.5). Scoping the rule to `a` therefore does the
   whole job with no per-item classes: the three plain items cannot match it.
   A hairline underline offset off the baseline keeps 22px halyard from looking
   struck through inside the bubbles, and covers the #Anchor jumps and the
   external orthogum.com link equally because they are anchors too.
   -------------------------------------------------------------------------- */
/* (the rule itself lives in section 8 above, where the Phase-B
   `text-decoration: none` it replaces was declared - see ITEM 7 there.) */

/* ==== FIGURE-SHADOW BLOCK START (Sullivan, 2026-08-20 - Eric approved) ==== */
/* --------------------------------------------------------------------------
   27. FIGURE BOX-SHADOW GAP - the shadow outlined the COLUMN, not the photo.
   --------------------------------------------------------------------------
   Astra's own dynamic CSS (astra-theme-dynamic-css-post-NNN.css) declares:

       .ast-article-single figure,
       .ast-article-single img:not(figure img) { box-shadow: 0 0 30px rgba(0,0,0,.15); }

   A <figure> is block-level, so it fills the full 1250px Elementor column even
   when the image inside is narrower. The shadow therefore traced a 1250px-wide
   box while the photo sat at its natural width - reading as an empty white
   panel beside the image. Measured on post 629 (untouched by the featured-image
   pass): figure 1250px, image 960px = 290px of empty shadowed panel.

   PRE-EXISTING, not introduced by the 2026-08-20 featured-image pass: 8 figures
   across 8 posts, 4 of which (629, 656, 751, 633) that pass never touched. It
   only became more visible once 4 more posts started painting a body image.

   `width: fit-content` shrink-wraps the figure to its content, so the shadow
   traces the PHOTO. `max-width: 100%` keeps a large image from overflowing the
   column. No `!important` needed - this is a plain specificity win over the
   Phase-B `.aad-single-body figure { margin }` rule, and it does not touch the
   D5 no-upscale contract on `figure img` (width:auto there is untouched).

   SAFE FOR THE FLOAT PATTERN: `.aad-cm-float` / `.aad-cm-float-left` declare
   `max-width: 30%` LATER in this file, so they win the cascade on max-width and
   keep their 30% cap; fit-content already matched what a float does (shrink-to-
   fit), so those figures are unchanged. Full-width images are a no-op too:
   fit-content resolves to the image's own width, which is the column width.
   -------------------------------------------------------------------------- */
.aad-single-body figure {
  width: fit-content;
  max-width: 100%;
}
/* ==== FIGURE-SHADOW BLOCK END ==== */
