/*
	Theme Name: Hello Elementor Child
	Theme URI: https://southeaststoneworks.com
	Description: Child theme of Hello Elementor for Southeast Stoneworks. Put all custom CSS and PHP tweaks here so parent-theme updates never overwrite them.
	Author: Southeast Stoneworks
	Template: hello-elementor
	Version: 1.4.0
	Requires at least: 6.0
	Requires PHP: 7.4
	License: GNU General Public License v3 or later.
	License URI: https://www.gnu.org/licenses/gpl-3.0.html
	Text Domain: hello-elementor-child
*/

/* ==========================================================================
   Custom CSS for Southeast Stoneworks
   Add your site-wide style overrides below. Most design is done in Elementor,
   so only put things here that Elementor can't do (or global tweaks).

   NOTE: global CSS lives in WPCode snippet #644, but WPCode reverts external
   edits to it, so cross-cutting fixes are placed here in the child theme
   (guaranteed to load; higher-specificity selectors win the cascade).
   ========================================================================== */

/* --------------------------------------------------------------------------
   FIX 2026-07-22 — Mega-menu overflow (desktop nav dropdowns)
   The .ses-mega-menu is centered on its trigger via left:50%/translateX(-50%).
   "Monuments & Services" sits left-of-center, so the 920px-wide menu ran off
   the LEFT edge of the viewport (Monument Types column clipped).
   Fix: make .ses-nav-item non-positioning so the menu anchors to the centered
   max-width container (.ses-nav-inner) and centers in the viewport instead.
   Desktop nav only shows >=1101px, where a 920px menu stays fully on-screen.
   -------------------------------------------------------------------------- */
.ses-site-header .ses-nav-primary .ses-nav-item { position: static; }

/* --------------------------------------------------------------------------
   FIX 2026-07-22 — Footer grid (after removing the "Our Brands" column)
   The desktop footer grid was 5 tracks (2fr 1fr 1fr 1fr 1fr); with Our Brands
   removed there are 4 columns, leaving an empty 5th track. Collapse to 4 tracks.
   Scoped to desktop; the desktop footer is hidden <=768px anyway.
   -------------------------------------------------------------------------- */
@media (min-width: 769px) {
  .ses-site-footer .ses-footer__inner.ses-footer__desktop-only {
    grid-template-columns: 2fr 1fr 1fr 1fr;
  }
}

/* ==========================================================================
   SES NOTIFICATION DESIGN SYSTEM — on-page message states (v1.1.0, 2026-07-23)
   Reusable feedback component for forms (success / error / info). Pairs with the
   branded email templates in /email-templates/. Uses the brand tokens from WPCode
   #644 with hard fallbacks so it renders even if that snippet hasn't loaded.
   Markup: <div class="ses-form-message is-success|is-error|is-info"> … </div>
   ========================================================================== */
.ses-form-message {
  display: none;                 /* revealed by the form JS on submit */
  margin: 20px 0 0;
  padding: 14px 18px;
  border-radius: 4px;
  border-left: 4px solid var(--ses-taupe, #C8B89A);
  background: var(--ses-cream, #F5F0E8);
  color: #2b2622;
  font-size: 15px;
  line-height: 1.5;
}
.ses-form-message.is-success {
  border-left-color: var(--ses-gold, #B8A750);
  background: #f3f0e4;
  color: #4a4326;
}
.ses-form-message.is-error {
  border-left-color: #a3412e;
  background: #f7ece9;
  color: #7a2c1e;
}
.ses-form-message.is-info {
  border-left-color: var(--ses-taupe, #C8B89A);
  background: var(--ses-cream, #F5F0E8);
}

/* ==========================================================================
   SES CONTACT FORM — reusable branded form component (v1.2.0, 2026-07-23)
   Styles forms built with the [ses_contact_form] shortcode markup (.ses-field
   structure). Scoped to .ses-field so it does NOT touch the Contact page's
   own bespoke form (which uses .form-group and keeps its inline design).
   Uses brand tokens (WPCode #644) with hard fallbacks.
   ========================================================================== */
.ses-contact-form { width: 100%; }

/* Honeypot — visually and AT-hidden, never focusable/submitted by humans */
.ses-contact-form .ses-hp {
  position: absolute !important;
  left: -9999px !important;
  width: 1px; height: 1px; overflow: hidden;
}

/* Rows: two fields side by side on desktop, stacked on mobile */
.ses-contact-form .ses-field-row {
  display: flex;
  gap: 18px;
  flex-wrap: wrap;
}
.ses-contact-form .ses-field-row > .ses-field { flex: 1 1 220px; }

.ses-contact-form .ses-field { margin: 0 0 18px; }

.ses-contact-form .ses-field label {
  display: block;
  margin: 0 0 7px;
  font-size: 13px;
  font-weight: 600;
  letter-spacing: .3px;
  color: var(--ses-charcoal, #1C2120);
}

.ses-contact-form .ses-field input,
.ses-contact-form .ses-field select,
.ses-contact-form .ses-field textarea {
  width: 100%;
  box-sizing: border-box;
  padding: 12px 14px;
  font-size: 15px;
  font-family: inherit;
  color: var(--ses-charcoal, #1C2120);
  background: #ffffff;
  border: 1px solid var(--ses-taupe, #C8B89A);
  border-radius: 4px;
  transition: border-color .15s ease, box-shadow .15s ease;
}
.ses-contact-form .ses-field textarea { min-height: 140px; resize: vertical; }

.ses-contact-form .ses-field input:focus,
.ses-contact-form .ses-field select:focus,
.ses-contact-form .ses-field textarea:focus {
  outline: none;
  border-color: var(--ses-gold, #B8A750);
  box-shadow: 0 0 0 3px var(--ses-gold-subtle, rgba(184,167,80,0.18));
}

/* Validation: only flag an invalid required field AFTER the user has touched it */
.ses-contact-form .ses-field input:required:invalid:not(:placeholder-shown),
.ses-contact-form .ses-field textarea:required:invalid:not(:placeholder-shown) {
  border-color: #a3412e;
}

/* Submit button */
.ses-contact-form .ses-btn {
  display: inline-block;
  width: 100%;
  padding: 14px 28px;
  font-size: 14px;
  font-weight: 700;
  letter-spacing: 1.5px;
  text-transform: uppercase;
  color: var(--ses-charcoal, #1C2120);
  background: var(--ses-gold, #B8A750);
  border: 0;
  border-radius: 4px;
  cursor: pointer;
  transition: background-color .15s ease;
}
.ses-contact-form .ses-btn:hover { background: var(--ses-gold-light, #D4C06A); }
.ses-contact-form .ses-btn:disabled { opacity: .6; cursor: default; }

.ses-contact-form .ses-form-note {
  margin: 12px 0 0;
  font-size: 12px;
  color: var(--ses-gold-dark, #8A7A38);
}

/* Host-page armor (v1.2.1): the bespoke location pages wrap content in an ID
   (#sm-page / #eh-page / #mm-page) and apply an ID-scoped universal reset
   (`#page *, #page ::before, #page ::after { margin:0; padding:0 }`). An ID beats
   class selectors, so it zeroes this component's padding/margins and the form
   renders cramped. Re-assert the structural spacing with !important so the form
   looks identical on every page. (Contact #811 uses .form-group, not .ses-field,
   so it is unaffected.) */
.ses-contact-form .ses-field { margin-bottom: 18px !important; }
.ses-contact-form .ses-field label { margin-bottom: 7px !important; }
.ses-contact-form .ses-field input,
.ses-contact-form .ses-field select,
.ses-contact-form .ses-field textarea { padding: 12px 14px !important; }
.ses-contact-form .ses-btn { padding: 14px 28px !important; }
.ses-contact-form .ses-form-note { margin-top: 12px !important; }
.ses-contact-form .ses-form-message { padding: 14px 18px !important; margin-top: 20px !important; }

@media (max-width: 600px) {
  .ses-contact-form .ses-field-row { gap: 0; }
}

/* ==========================================================================
   MADISON HERO CTA BUTTONS — label readability + spacing (v1.2.2, 2026-07-23, QA)
   The Madison page rule `.mm-page a { color: inherit }` (specificity 0,1,1) outranks
   the button rules `.mm-btn-* { color: var(--mm-…) }` (0,1,0), so the labels inherited
   the dark body color — and once the re-theme made the button backgrounds green/dark,
   "Request a Consultation" (dark text on green) and "(706) 343-0089" (dark text over the
   photo) became unreadable. These overrides (`.mm-page .mm-btn-*` = 0,2,0) win cleanly
   and restore readable white labels + a coherent hover; the hero action row also gets
   a little more breathing room between the two buttons.
   ========================================================================== */
.mm-page .mm-btn-primary { color: #ffffff; }
.mm-page .mm-btn-outline { color: #ffffff; }
/* The global `html body a:hover { color: var(--ses-gold) !important }` (WPCode #644) hijacks
   EVERY link's hover colour — including these buttons — turning the label gold and low-contrast
   on the green fills. Override at matching strength (`html body …` + !important), scoped to the
   two hero buttons only. */
html body .mm-page .mm-btn-primary:hover { color: #ffffff !important; }
html body .mm-page .mm-btn-outline:hover {
  color: #ffffff !important;
  border-color: var(--mm-gold, #2F4A3C);
  background: var(--mm-gold, #2F4A3C); /* fill with brand green so white text stays readable over any part of the photo */
}
.mm-page .mm-hero-actions { gap: 22px; margin-bottom: 64px !important; } /* lift the buttons off the black stats section (hero is centered + overflow:hidden, so extra space below shifts them up) */

/* "Ready to Begin the Design Process?" CTA section (green backdrop) — same inherited-dark-label
   problem on the OTHER two variants: mm-btn-dark (black button) and mm-btn-ghost-dark (transparent,
   originally designed for a light bg). Make both readable on the dark/green backdrop, hover kept coherent. */
.mm-page .mm-btn-dark { color: #ffffff; }
html body .mm-page .mm-btn-dark:hover { color: #ffffff !important; }
.mm-page .mm-btn-ghost-dark { color: #ffffff; border-color: rgba(255, 255, 255, 0.55); }
html body .mm-page .mm-btn-ghost-dark:hover {
  color: #ffffff !important;
  border-color: #111111;
  background: #111111; /* ghost fills dark on hover so the white label stays readable on the green section */
}

/* Hero eyebrow: after the green re-theme it used the (now-green) --mm-gold, so the small
   uppercase line rendered green-on-photo and was invisible — worst on mobile over the bright
   top of the image. Give it a readable warm cream + a shadow for legibility over the photo. */
.mm-page .mm-hero-eyebrow {
  color: #E8DFD0 !important;
  text-shadow: 0 1px 4px rgba(0, 0, 0, 0.55);
}

/* Other location hero eyebrows (EH / Spence / GAM) — small gold accent lines over busy
   photos that wash out on the brighter/warmer areas (EH worst, over the golden workshop
   light). Keep their brand gold, just add a shadow so they lift off the photo. */
.eh-hero-eyebrow,
.sm-hero-eyebrow,
.ga-overline { text-shadow: 0 1px 4px rgba(0, 0, 0, 0.6); }

/* ==========================================================================
   MADISON — low-contrast accent text on dark sections (v1.2.9, QA)
   The green re-theme set the accent (--mm-gold) to #2F4A3C. That reads on light
   backgrounds and as the large hero word, but on the page's DARK sections (stats
   bar #111, statement band #3F3F3F, section eyebrows, contact labels) the small
   green text is effectively invisible. Recolor to readable, on-brand tones:
   light sage for the prominent numbers, warm cream for the small eyebrows/labels.
   (The 0.15-opacity mm-cemetery-card-num watermark is intentional — left alone.)
   ========================================================================== */
.mm-page .mm-stat-num { color: #9DC3AE !important; }
.mm-page .mm-section-eyebrow,
.mm-page .mm-cemetery-eyebrow,
.mm-page .mm-contact-info-eyebrow,
.mm-page .mm-statement-attr,
.mm-page .mm-area-label,
.mm-page .mm-contact-detail-label { color: #E8DFD0 !important; }
/* "Ready to Begin" CTA sits on the dark green band; its heading (#111) + sub (#111/.7)
   were dark-on-dark. Make them light for readable contrast on the green. */
.mm-page .mm-cta-text-title { color: #F5F0E8 !important; }
.mm-page .mm-cta-text-sub { color: rgba(245, 240, 232, 0.85) !important; }

/* ==========================================================================
   HOME + TRADE PARTNERS HERO — fluid, proportional spacing (v1.3.5, QA)
   Was: hard padding-top steps (130/112/88 at 1024/600) bolted onto a 100vh,
   vertically-centered hero with a bottom stat bar. Two problems surfaced at
   1440-and-down desktop: (1) the steps jumped discontinuously, so the spacing
   visibly "broke" between breakpoints while resizing; (2) on laptop-height
   viewports (~788px) top-pad + the tall headline + the stat bar exceeded 100vh,
   so the eyebrow crammed against the nav and the stat bar clipped below the fold.

   Fix (what a senior would do): one CONTINUOUS clamp() scale for top / bottom /
   side padding — no breakpoints, so there is no size at which it jumps — and a
   BOUNDED headline (the old unbounded 6vw ran to 115px+ on wide screens and
   wrapped to 4 lines that ate the vertical space). The visible header stack ends
   at ~96px (util bar 36 + overlaid brand row), so 104px is the clearance floor.
   Targets .ses-hero (home) + .tp-hero (trade partners); location heroes untouched.
   ========================================================================== */
.ses-hero,
.tp-hero {
  /* top: clears the ~96px header (104 floor) + a gap that grows with viewport
     height; bottom: breathing room. Self-contained — no dependency on the
     header's own --ses-nav-h var (which is 72px = brand row only). */
  padding-top: clamp(104px, calc(88px + 3vh), 148px) !important;
  padding-bottom: clamp(24px, 4vh, 56px) !important;
  box-sizing: border-box;
}
/* Fluid side gutters: 64px on desktop down to 22px on phones, continuous (was a
   fixed 0 64px that left mobile text nearly edge-to-edge under the old breakpoints). */
.ses-hero__content {
  padding-left: clamp(22px, 5vw, 64px) !important;
  padding-right: clamp(22px, 5vw, 64px) !important;
}
/* Bound the viewport-scaled headline so it stays proportional and can't consume the
   whole hero on wide/short screens (was an unbounded 6vw). 42px floor → 72px ceiling. */
.ses-hero__headline {
  font-size: clamp(2.6rem, 5.2vw, 4.5rem) !important;
  line-height: 1.06 !important;
}

/* ==========================================================================
   SHORT-BAND HEROES — unified fluid clearance (v1.3.6, QA)
   Contact / About / Locations use a short banner hero (no 100vh) that sits UNDER
   the ~96px overlay nav. Their top padding was only 6-7rem (96-112px) — barely the
   nav height — so the headline crowded the nav (Contact & Locations ~36px gap,
   About ~52px), and each page used a slightly different value. FAQ's band already
   clears comfortably (~94px) and is the reference we match. Normalize these three
   to one continuous clamp() scale: a consistent, comfortable gap below the nav at
   every width (no hard breakpoints), fluid side gutters, and proportional bottom
   room. Full-viewport heroes (home/TP/outdoor/EH/Spence/Madison/Monuments) already
   clear the nav generously via centered/bottom content and are left as-is; GAM is
   do-not-touch; FAQ is left alone (already comfortable). */
.contact-hero,
.about-hero,
.loc-hero {
  /* top clears the ~96px nav + a gap that scales with viewport height (≈96px gap on
     desktop, ≈78px on mobile) so the headline never crowds the nav at any size */
  padding-top: clamp(130px, calc(96px + 6vh), 168px) !important;
  padding-bottom: clamp(48px, 7vh, 88px) !important;
  padding-left: clamp(20px, 3vw, 40px) !important;
  padding-right: clamp(20px, 3vw, 40px) !important;
  box-sizing: border-box;
}

/* Madison hero on mobile: its heading is the longest (wraps to ~4 lines), so the CENTERED
   hero content grew tall enough that the eyebrow tucked behind the nav (only "GEORGIA" showed).
   On mobile, anchor the content to the top with nav clearance so the eyebrow is fully visible.
   (EH/Spence/GAM have shorter headings and don't need this.) */
@media (max-width: 600px) {
  .mm-page .mm-hero { align-items: flex-start !important; padding-top: 100px !important; box-sizing: border-box; }
}

/* Spence hero — mobile gutter parity (v1.3.7, QA)
   Spence was the only full-viewport location hero WITHOUT a small-screen override,
   so on phones it kept the desktop 8rem/2rem (128px top, 32px sides) while EH,
   Monuments and Madison all drop to ~112px/24px. That left Spence's text column
   ~16px narrower than its siblings. Match the group so mobile gutters/clearance
   are uniform across the location heroes. */
@media (max-width: 600px) {
  .sm-hero-content { padding: 7rem 1.5rem 5rem !important; }
}

/* ==========================================================================
   GOLD SECTION LABELS — AA readability on LIGHT sections (v1.3.1, QA)
   The gold accent labels/eyebrows (#B8A750) sat at ~1.95-2.13 contrast on the
   cream/white content sections (below WCAG AA). Darken to a deeper antique gold
   that clears AA while staying on-brand. IMPORTANT: some of these classes (esp.
   .ses-section-label) are ALSO used on dark feature bands where the bright gold
   already reads — re-brighten those so we don't regress them.
   (Left alone: hero eyebrows on dark, GAM's ga-overline [do-not-touch], the large
   italic heading accents, and the gold review stars — all fine as-is.)
   ========================================================================== */
/* `html body` prefix raises specificity above the pages' inline `!important` gold rules */
html body .ses-section-label,
html body .ses-service-row__link,
html body .ses-label,
html body .mon-eyebrow,
html body .faq-section__eyebrow,
html body .faq-section__count { color: #7A6A2E !important; }
/* keep bright gold where the section label sits on a DARK band */
html body .ses-concierge .ses-section-label,
html body .ses-booking .ses-section-label { color: var(--ses-gold, #B8A750) !important; }


/* ==========================================================================
   AMELIA BOOKING FORM — Greater Atlanta Memorials branding
   Lives in the child theme (not a WPCode snippet or mu-plugin) so it travels
   with the site on migration and needs no setup on live.
   ========================================================================== */

/* ── Core palette + typography ──────────────────────────────────────────── */
.amelia-v2-booking,
.amelia-v2-booking .am-fs__wrapper,
.amelia-v2-booking .am-fs-sb,
.amelia-v2-booking .am-fs__main,
.amelia-v2-booking [style*="--am-"] {
  --am-c-primary:            #8A7A38 !important;
  --am-c-btn-prim:           #C9A84C !important;
  --am-c-btn-prim-text:      #1E1B16 !important;
  --am-c-btn-sec:            #FFFFFF !important;
  --am-c-btn-sec-text:       #1C2120 !important;

  --am-c-sb-bgr:             #1C2120 !important;
  --am-c-sb-text:            #F5F0E8 !important;

  --am-c-main-bgr:           #FFFFFF !important;
  --am-c-main-heading-text:  #1C2120 !important;
  --am-c-main-text:          #333333 !important;

  --am-c-inp-bgr:            #FFFFFF !important;
  --am-c-inp-text:           #1C2120 !important;
  --am-c-inp-border:         rgba(30, 27, 22, .22) !important;
  --am-c-inp-placeholder:    #8A8378 !important;

  --am-c-drop-bgr:           #FFFFFF !important;
  --am-c-drop-text:          #1C2120 !important;
  --am-c-checkbox-border:    rgba(30, 27, 22, .32) !important;

  --am-c-scroll-op30:        rgba(138, 122, 56, .30) !important;
  --am-c-scroll-op10:        rgba(138, 122, 56, .10) !important;

  --am-font-family: "Jost", -apple-system, "Segoe UI", Roboto, sans-serif !important;
  --am-rad-inp: 0px !important;
}

/* ── Calendar + time-slot palette ───────────────────────────────────────────
   Amelia keys availability density off cal-init / cal-low / cal-high, all of
   which default to blue. "selected" becomes charcoal rather than gold: at slot
   text size gold on white fails AA, charcoal on cream passes comfortably. */
.amelia-v2-booking,
.amelia-v2-booking .am-advsc__wrapper,
.amelia-v2-booking [style*="--am-c-cal"],
.amelia-v2-booking [style*="--am-c-advsc"] {
  --am-c-cal-init:          #6E6129 !important;
  --am-c-cal-init-op10:     rgba(138, 122, 56, .1) !important;
  --am-c-cal-init-op20:     rgba(138, 122, 56, .2) !important;
  --am-c-cal-init-op30:     rgba(138, 122, 56, .3) !important;
  --am-c-cal-init-op60:     rgba(138, 122, 56, .6) !important;

  --am-c-cal-low:           #8A7A38 !important;
  --am-c-cal-low-text:      #6E6129 !important;
  --am-c-cal-low-op10:      rgba(138, 122, 56, .1) !important;
  --am-c-cal-low-op60:      rgba(138, 122, 56, .6) !important;
  --am-c-cal-low-op80:      rgba(138, 122, 56, .8) !important;

  --am-c-cal-high:          #8A7A38 !important;
  --am-c-cal-high-text:     #6E6129 !important;
  --am-c-cal-high-op10:     rgba(138, 122, 56, .1) !important;
  --am-c-cal-high-op20:     rgba(138, 122, 56, .2) !important;
  --am-c-cal-high-op30:     rgba(138, 122, 56, .3) !important;
  --am-c-cal-high-op60:     rgba(138, 122, 56, .6) !important;
  --am-c-cal-high-op80:     rgba(138, 122, 56, .8) !important;

  --am-c-cal-selected:      #1C2120 !important;
  --am-c-cal-selected-op80: rgba(28, 33, 32, .8) !important;

  --am-c-advsc-slot-text:   #6E6129 !important;
  --am-c-advsc-cell-bgr:    rgba(138, 122, 56, .1) !important;
}

/* ── Shell reads as one of the page's cards ─────────────────────────────── */
.amelia-v2-booking .am-fs__wrapper,
.amelia-v2-booking .am-fs {
  border: 1px solid rgba(30, 27, 22, .08);
  border-radius: 0 !important;
  box-shadow: none;
}

/* ── Display headings in Cormorant Garamond ──────────────────────────────────
   Only real h1–h4 headings. Amelia's step titles are spans
   (.am-fs__main-heading-inner-title) and stay in Jost on purpose: the Greater
   Atlanta page uses Cormorant for display type and Jost for UI labels, and an
   18px serif step title reads weak next to the rest of the widget chrome. */
.amelia-v2-booking h1,
.amelia-v2-booking h2,
.amelia-v2-booking h3,
.amelia-v2-booking h4,
.amelia-v2-booking .am-fs__header-title,
.amelia-v2-booking .am-fs-sb__step-heading {
  font-family: "Cormorant Garamond", Georgia, serif !important;
  font-weight: 400;
  letter-spacing: .2px;
}

/* ── Buttons: square, uppercase, letter-spaced — same as page CTAs ──────── */
.amelia-v2-booking .am-button,
.amelia-v2-booking .am-button__inner {
  border-radius: 0 !important;
}

.amelia-v2-booking .am-button {
  font-family: "Jost", sans-serif !important;
  text-transform: uppercase;
  letter-spacing: 1.6px;
  font-weight: 500;
}

/* Amelia hardcodes the filled/primary background, so set it explicitly. The
   --am-c-btn-first/second pair below drives its hover and active states. */
.amelia-v2-booking .am-button.am-button--primary,
.amelia-v2-booking .am-button.am-button--filled,
.amelia-v2-booking .am-button--filled.am-button--primary {
  background-color: #C9A84C !important;
  border-color: #C9A84C !important;
  color: #1E1B16 !important;
}

.amelia-v2-booking .am-button.am-button--primary:hover,
.amelia-v2-booking .am-button--filled.am-button--primary:hover {
  background-color: #B8A750 !important;
  border-color: #B8A750 !important;
  color: #1E1B16 !important;
}

.amelia-v2-booking .am-button--primary,
.amelia-v2-booking .am-button--filled.am-button--primary {
  --am-c-btn-first:       #C9A84C !important;
  --am-c-btn-second:      #1E1B16 !important;
  --am-c-btn-first-op80:  rgba(201, 168, 76, .80) !important;
  --am-c-btn-first-op30:  rgba(201, 168, 76, .30) !important;
  --am-c-btn-first-op20:  rgba(201, 168, 76, .20) !important;
}

.amelia-v2-booking .am-button--secondary,
.amelia-v2-booking .am-button--plain {
  --am-c-btn-first:       #1C2120 !important;
  --am-c-btn-second:      #FFFFFF !important;
  --am-c-btn-first-op80:  rgba(28, 33, 32, .80) !important;
  --am-c-btn-first-op30:  rgba(28, 33, 32, .30) !important;
  --am-c-btn-first-op20:  rgba(28, 33, 32, .12) !important;
}

/* ── Square off everything Amelia rounds ────────────────────────────────── */
.amelia-v2-booking .am-advsc__slot-wrapper,
.amelia-v2-booking .am-advsc__dayGridMonth-cell,
.amelia-v2-booking .fc-daygrid-day-frame,
.amelia-v2-booking .am-fs-sb,
.amelia-v2-booking .am-fs-sb__step,
.amelia-v2-booking input,
.amelia-v2-booking select,
.amelia-v2-booking textarea,
.amelia-v2-booking .el-input__wrapper {
  border-radius: 0 !important;
}

/* #6E6129 rather than the lighter #8A7A38: on the 10%-gold cell fill that is
   5.5:1, where #8A7A38 measured only 3.8:1 and failed AA for normal text. */
.amelia-v2-booking .fc-daygrid-day-number {
  color: #6E6129 !important;
}

/* The 4px "today" indicator dot is drawn as a pseudo-element and is the last
   place Amelia's blue survives. */
.amelia-v2-booking .fc-day-today .fc-daygrid-day-frame::after {
  background-color: #8A7A38 !important;
}

/* Empty timezone row inherits the old primary; harmless today but would show
   through if a timezone label is ever enabled. */
.amelia-v2-booking .am-advsc__time-zone,
.amelia-v2-booking .am-advsc__time-zone * {
  color: #6E6129 !important;
}