/* Chuẩn Sâm Korea — layout: page chrome (wrap, header/nav, footer, section rhythm).
   Split from assets/site.css — see docs/SOURCE-AUDIT.md */

.wrap { max-width: 1240px; margin: 0 auto; padding: 0 24px; }
@media (max-width: 640px) { .wrap { padding: 0 18px; } }

/* texture: faint parchment grain via layered radial dots */
.grain-bg {
  background-image:
    radial-gradient(circle at 15% 8%, rgba(184,134,59,0.06), transparent 40%),
    radial-gradient(circle at 85% 92%, rgba(139,30,36,0.05), transparent 45%);
}

/* ---------- header / nav ---------- */
.site-header {
  position: sticky;
  top: 0;
  z-index: 100;
  background: rgba(250, 243, 227, 0.92);
  backdrop-filter: blur(10px);
  -webkit-backdrop-filter: blur(10px);
  border-bottom: 1px solid var(--border);
}
.site-header .wrap {
  display: flex;
  align-items: center;
  gap: 22px;
  height: 78px;
}
/* .nav-search (added 2026-09-04) needs to sit snugly next to .nav-links/
   .nav-toggle rather than getting stranded far away from them — the old
   `justify-content: space-between` distributed exactly 2 real gaps evenly
   across .wrap's children, which worked fine for the original 3 items
   (brand | nav-links | nav-toggle) but would space a 4th item just as far
   from its neighbor as .brand is from .nav-links. margin-left:auto on
   .nav-links absorbs all the leftover space in one place (right after the
   brand), so everything from .nav-links onward hugs together on the right
   with the shared `gap` above between them instead.
   Real regression found+fixed 2026-09-04 (Mi Pad 7 portrait report: hamburger
   button crowded to the left): once .nav-links switches to position:absolute
   at the tablet breakpoint below, it drops out of flex flow entirely — so
   THIS margin-left:auto stops applying, and nothing was left to push
   .nav-search/.nav-toggle to the right edge; they just packed against
   .brand with only the base `gap`. Fixed by giving .nav-search its own
   margin-left:auto, scoped inside that same breakpoint (see below), so the
   spacer role transfers to whichever element is actually still in-flow. */
.nav-links { margin-left: auto; }
.brand {
  display: flex;
  align-items: center;
  gap: 10px;
  font-family: 'Playfair Display', serif;
  font-weight: 700;
  font-size: 22px;
  color: var(--fg);
}
.brand small {
  font-family: 'Inter', sans-serif;
  font-weight: 500;
  font-size: 11px;
  color: var(--muted);
  letter-spacing: 0.02em;
}
@media (max-width: 420px) {
  .site-header .brand { font-size: 18px; }
  .site-header .brand small { display: none; }
}
.brand-mark {
  width: 44px;
  height: 44px;
  border-radius: 50%;
  overflow: hidden;
  flex-shrink: 0;
  display: inline-flex;
  box-shadow: 0 0 0 1px rgba(0,0,0,.08);
}
.brand-mark img { height: 44px; width: auto; max-width: none; object-fit: cover; object-position: left center; display: block; }
.site-footer .brand-mark { box-shadow: 0 0 0 1px rgba(255,255,255,.18); }

.nav-links {
  display: flex;
  align-items: center;
  gap: 34px;
}
.nav-links a {
  font-size: 14px;
  font-weight: 500;
  letter-spacing: 0.02em;
  color: var(--fg);
  position: relative;
  padding: 6px 0;
}
.nav-links a.active { color: var(--accent-deep); }
.nav-links a:not(.btn-primary)::after {
  content: '';
  position: absolute;
  left: 0; right: 0; bottom: 0;
  height: 2px;
  background: var(--accent-deep);
  transform: scaleX(0);
  transform-origin: left;
  transition: transform 200ms ease;
}
.nav-links a:not(.btn-primary):hover::after { transform: scaleX(1); }
/* .nav-links a's own color/padding (above) has higher specificity than .btn-primary
   alone and was silently overriding it — text rendered in --fg (dark espresso) on
   the accent-deep maroon pill with almost no horizontal padding. Restore the
   intended white text + even pill padding here. */
.nav-links a.btn-primary { color: #fff; padding: 13px 26px; }

/* ---------- dropdown submenu (e.g. "Danh mục" → 9 real product categories) ---------- */
.nav-item { position: relative; display: inline-flex; align-items: center; }
.nav-parent-link { display: inline-flex; align-items: center; gap: 5px; }
.nav-caret { transition: transform 180ms ease; flex-shrink: 0; }
.nav-item:hover .nav-caret,
.nav-item:focus-within .nav-caret { transform: rotate(180deg); }
.sub-menu {
  position: absolute;
  top: 100%;
  left: 50%;
  transform: translate(-50%, 6px);
  min-width: 240px;
  background: var(--surface);
  border: 1px solid var(--border);
  border-radius: 12px;
  box-shadow: var(--shadow);
  padding: 8px;
  display: flex;
  flex-direction: column;
  gap: 2px;
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
  transition: opacity 180ms ease, transform 180ms ease, visibility 180ms;
  z-index: 10;
}
.nav-item:hover .sub-menu,
.nav-item:focus-within .sub-menu {
  opacity: 1;
  visibility: visible;
  pointer-events: auto;
  transform: translate(-50%, 0);
}
.sub-menu a {
  padding: 9px 14px;
  border-radius: 8px;
  white-space: nowrap;
}
.sub-menu a:not(.btn-primary)::after { display: none; }
.sub-menu a:hover,
.sub-menu a.active { background: var(--bg); color: var(--accent-deep); }
@media (prefers-reduced-motion: reduce) {
  .sub-menu, .nav-caret { transition: none; }
}

/* ---------- header search (2026-09-04) ----------
   search.php already fully implements real results (confirmed `?s=` was
   already returning real product cards before this existed) — this is
   purely the missing front-end entry point. An icon that expands into a
   dropdown flyout (same visual language as .sub-menu) rather than a
   permanent input, so it doesn't compete for space in an already-tight
   header (see the earlier "menu bị dồn" work moving Tin tức/Khách hàng
   nói gì into a submenu, same underlying constraint). */
.nav-search { position: relative; }
.search-toggle {
  display: flex; align-items: center; justify-content: center;
  width: 40px; height: 40px; border-radius: 50%;
  color: var(--fg);
  transition: background-color 180ms ease, color 180ms ease;
}
.search-toggle svg { width: 19px; height: 19px; }
.search-toggle:hover, .nav-search.is-open .search-toggle { background: var(--accent-deep); color: #fff; }

.search-flyout {
  position: absolute;
  top: calc(100% + 12px);
  right: 0;
  width: 340px;
  max-width: calc(100vw - 36px);
  /* Slightly translucent + blurred (same frosted-glass treatment as
     .site-header itself) instead of a flat opaque white card — matches the
     header it drops from and reads softer against the page behind it.
     0.9 alpha (first attempt) still read as flat opaque white per user
     feedback — dropped to 0.6 so the page texture behind genuinely shows
     through. The inner .search-flyout__form pill keeps its own solid
     var(--bg) fill unchanged — that one's meant to read as a normal input
     field, only this outer card is the "khung search" being softened. */
  background: rgba(255, 252, 246, 0.6);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  border: 1px solid var(--border);
  border-radius: 14px;
  box-shadow: var(--shadow);
  padding: 10px;
  opacity: 0;
  visibility: hidden;
  transform: translateY(-8px) scale(.98);
  transform-origin: top right;
  transition: opacity 200ms cubic-bezier(0.2,0,0,1), transform 200ms cubic-bezier(0.2,0,0,1), visibility 200ms;
}
.nav-search.is-open .search-flyout { opacity: 1; visibility: visible; transform: translateY(0) scale(1); }
@media (prefers-reduced-motion: reduce) { .search-flyout { transition: opacity 120ms ease, visibility 120ms; transform: none; } }

.search-flyout__form { display: flex; align-items: center; gap: 8px; background: var(--bg); border: 1.5px solid var(--border); border-radius: 999px; padding: 6px 6px 6px 16px; transition: border-color 150ms ease; }
.search-flyout__form:focus-within { border-color: var(--accent); }
.search-flyout__icon { width: 17px; height: 17px; flex-shrink: 0; color: var(--muted); }
.search-flyout__input { flex: 1; min-width: 0; border: 0; background: none; font-family: 'Inter', sans-serif; font-size: 13.5px; color: var(--fg); padding: 8px 0; }
.search-flyout__input:focus { outline: none; }
.search-flyout__input::placeholder { color: var(--muted); }
.search-flyout__input::-webkit-search-cancel-button { display: none; }
.search-flyout__submit {
  display: flex; align-items: center; justify-content: center; flex-shrink: 0;
  width: 34px; height: 34px; border-radius: 50%;
  background: var(--accent-deep); color: #fff;
  transition: background-color 150ms ease, transform 150ms ease;
}
.search-flyout__submit svg { width: 15px; height: 15px; }
.search-flyout__submit:hover { background: var(--accent-deep-dark); transform: scale(1.06); }

@media (max-width: 640px) {
  /* Real bug found via a real screenshot, not assumed fixed: `right`
     positions relative to .nav-search's OWN box, and .nav-search sits to
     the left of the hamburger button — not near the viewport's right edge
     at all on mobile — so this offset pushed the flyout ~68px past the
     left edge of the screen, clipping the input text and icon. Switching
     to `position: fixed` anchors it to the viewport itself instead, so it
     centers correctly under the header regardless of where the toggle
     icon happens to sit. */
  .search-flyout { position: fixed; top: 84px; left: 14px; right: 14px; width: auto; transform-origin: top center; }
}

.nav-toggle { display: none; color: var(--fg); }
.nav-toggle .icon-close { display: none; }
.nav-toggle[aria-expanded="true"] .icon-menu { display: none; }
.nav-toggle[aria-expanded="true"] .icon-close { display: block; }
/* Breakpoint raised 860px -> 1180px 2026-09-04 (Mi Pad 7 landscape report:
   "vẫn bị dồn menu"). At 860px, a typical ~11" Android tablet's landscape
   CSS width (Mi Pad 7's 2136x1600 3:2 panel reports ~1068px CSS-wide at its
   2x DPR) still fell into the DESKTOP branch, forcing brand + 5 nav links +
   the hotline pill + the search icon into one row with barely any slack —
   technically fits, reads as crowded. Tablets are touch-first anyway, so
   there's no real UX cost to giving them the same roomy hamburger nav as
   phones; 1180px clears Mi Pad 7's ~1068px landscape width with margin to
   spare while still leaving genuine small-laptop widths (1280px+) on the
   full desktop nav. */
@media (max-width: 1180px) {
  .nav-toggle {
    display: flex; align-items: center; justify-content: center;
    width: 44px; height: 44px; border-radius: 10px; border: 1px solid var(--border);
    background: var(--surface);
  }
  /* See the margin-left:auto comment above .nav-links earlier in this file:
     .nav-links leaves flex flow below, so .nav-search takes over as the
     spacer that keeps the search icon + hamburger pinned to the right edge. */
  .nav-search { margin-left: auto; }
  .nav-links {
    display: flex; flex-direction: column; align-items: flex-start; gap: 4px;
    position: absolute; top: 78px; left: 0; right: 0;
    background: var(--surface); border-bottom: 1px solid var(--border);
    padding: 14px 24px 22px;
    box-shadow: var(--shadow);
    opacity: 0; visibility: hidden; transform: translateY(-8px); pointer-events: none;
    transition: opacity 220ms cubic-bezier(0.2,0,0,1), transform 220ms cubic-bezier(0.2,0,0,1), visibility 220ms;
  }
  .nav-links.open {
    opacity: 1; visibility: visible; transform: translateY(0); pointer-events: auto;
  }
  .nav-links a { padding: 10px 0; width: 100%; }
  /* No room/hover on mobile for a real dropdown, and this menu is short
     (9 items) — always-expanded indented list under "Danh mục" is simpler
     and more reliable than adding a tap-to-toggle accordion + new JS. */
  .nav-item { flex-direction: column; align-items: flex-start; width: 100%; }
  .nav-caret { display: none; }
  /* Real bug found 2026-09-01 via a live mobile tap test: `visibility` and
     `pointer-events` are inherited properties that a descendant CAN
     override even while an ancestor is hidden — a bare `.sub-menu` rule
     here forced `visibility:visible; pointer-events:auto` unconditionally,
     which broke OUT of `.nav-links`'s closed state (`visibility:hidden;
     pointer-events:none`) above. Result: with the mobile menu closed, an
     invisible (opacity still inherited as 0 from `.nav-links`, so not
     visible — but very much clickable) copy of the whole "Danh mục"
     category list sat positioned right under the header, overlapping the
     top of any page's actual content. Confirmed via a real Puppeteer touch
     test: `document.elementFromPoint()` at a product card's coordinates
     returned this `.sub-menu`, and tapping it navigated to the FIRST
     category link inside it ("Rượu Sâm...") instead of the product
     underneath — exactly the "tapping a product goes back to a category
     page" symptom reported. Fix: scope every one of these overrides to
     `.nav-links.open .sub-menu` so they only ever apply while the menu is
     genuinely open, matching `.nav-links.open`'s own re-enabling above. */
  .nav-links.open .sub-menu {
    position: static; transform: none; opacity: 1; visibility: visible; pointer-events: auto;
    width: 100%; border: none; box-shadow: none; padding: 0 0 6px 16px; margin-top: -4px;
    border-left: 2px solid var(--border);
  }
  .nav-links.open .sub-menu a { padding: 8px 0 8px 12px; width: 100%; font-size: 13.5px; color: var(--muted); }
}
@media (max-width: 1180px) and (prefers-reduced-motion: reduce) {
  .nav-links { transition: opacity 150ms ease, visibility 150ms; transform: none; }
}

/* ---------- footer ---------- */
.site-footer {
  background: var(--fg);
  color: #E9DCC3;
  margin-top: 90px;
}
.site-footer .wrap { padding: 56px 24px 30px; }
.footer-grid { display: grid; grid-template-columns: 1.4fr 1fr 1fr; gap: 40px; }
@media (max-width: 720px) { .footer-grid { grid-template-columns: 1fr; gap: 30px; } }
.site-footer h3 { color: #F3E6C8; font-size: 15px; margin-bottom: 14px; font-family: 'Inter', sans-serif; font-weight: 600; letter-spacing: 0.03em; }
.site-footer .brand { color: #F3E6C8; }
.site-footer .brand small { color: #B9A87E; opacity: .6; }
.site-footer p, .site-footer li, .site-footer a { font-size: 13.5px; color: #C9B896; line-height: 2; }
.site-footer a:hover { color: #F3E6C8; }

/* Footer contact rows — icon + text, added 2026-09-02 for a more
   professional/scannable look than plain "Hotline: ..." text lines. */
.footer-contact { display: flex; flex-direction: column; gap: 10px; margin-bottom: 18px; }
.footer-contact li { display: flex; align-items: flex-start; gap: 10px; line-height: 1.5; }
.footer-contact .ico { flex: none; width: 20px; height: 20px; margin-top: 1px; color: #C9A868; }
.footer-contact .ico svg { width: 100%; height: 100%; }
.footer-social { display: flex; gap: 10px; margin-bottom: 18px; }
.footer-social a {
  display: inline-flex; align-items: center; justify-content: center;
  width: 34px; height: 34px; border-radius: 50%;
  background: rgba(233, 220, 195, 0.1); color: #E9DCC3;
  transition: background-color 150ms ease, color 150ms ease;
}
.footer-social a:hover { background: var(--accent-deep); color: #FDF3E7; }
.footer-social a svg { width: 16px; height: 16px; }

/* ---------- floating call/Zalo buttons (2026-09-02) ---------- */
.floating-contact {
  position: fixed;
  left: 18px;
  bottom: max(18px, env(safe-area-inset-bottom));
  z-index: 150;
  display: flex;
  flex-direction: column;
  gap: 12px;
}
.fc-btn {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 52px;
  height: 52px;
  border-radius: 50%;
  color: #fff;
  box-shadow: 0 10px 22px -8px rgba(30, 20, 10, .45);
  transition: transform 200ms ease, box-shadow 200ms ease;
}
.fc-btn:hover { transform: scale(1.08); color: #fff; }
.fc-btn svg { width: 24px; height: 24px; position: relative; z-index: 2; }
.fc-call { background: var(--accent-deep); }
.fc-zalo { background: #0068FF; }
/* A soft, slow expanding ring — gentle enough to read as "alive" rather
   than a nagging notification badge; paused entirely under reduced-motion. */
.fc-btn::after {
  content: '';
  position: absolute;
  inset: 0;
  border-radius: 50%;
  animation: fc-pulse 2.6s ease-out infinite;
  pointer-events: none;
}
.fc-call::after { box-shadow: 0 0 0 0 rgba(139, 30, 36, .55); animation-delay: 0s; }
.fc-zalo::after { box-shadow: 0 0 0 0 rgba(0, 104, 255, .5); animation-delay: 1.3s; }
@keyframes fc-pulse {
  0% { box-shadow: 0 0 0 0 rgba(139, 30, 36, .5); }
  70% { box-shadow: 0 0 0 16px rgba(139, 30, 36, 0); }
  100% { box-shadow: 0 0 0 16px rgba(139, 30, 36, 0); }
}
/* Text tooltip that slides out to the right on hover — desktop/mouse only,
   a touch device has no hover state to reveal it, and the icon alone is
   already a well-understood affordance at this size. */
.fc-tip {
  position: absolute;
  left: calc(100% + 12px);
  top: 50%;
  transform: translate(-8px, -50%);
  background: var(--fg);
  color: #F3E6C8;
  font-size: 12.5px;
  font-weight: 600;
  white-space: nowrap;
  padding: 7px 14px;
  border-radius: 999px;
  opacity: 0;
  pointer-events: none;
  transition: opacity 180ms ease, transform 180ms ease;
}
@media (hover: hover) and (pointer: fine) {
  .fc-btn:hover .fc-tip { opacity: 1; transform: translate(0, -50%); }
}
@media (max-width: 640px) {
  .floating-contact { left: 14px; gap: 10px; }
  .fc-btn { width: 46px; height: 46px; }
  .fc-btn svg { width: 21px; height: 21px; }
}
@media print { .floating-contact { display: none; } }
@media (prefers-reduced-motion: reduce) { .fc-btn::after { animation: none; } }
/* Real bug found 2026-09-04 via a live mobile scroll test on /checkout/: this
   widget's `position: fixed` sits on top of whatever the page currently
   shows at that screen corner — on a long form like checkout it ends up
   parked directly over address/payment fields as the visitor scrolls,
   visually overlapping text and even sitting on top of tappable radio
   buttons. WooCommerce keeps the `woocommerce-checkout` body class on the
   whole checkout flow, including the order-received/thank-you step, so one
   rule here covers both pages. */
body.woocommerce-checkout .floating-contact,
body.woocommerce-checkout .chat-widget { display: none; }

/* ---------- chat widget, bottom-right (2026-09-02, UI only for now) ---------- */
.chat-widget {
  position: fixed;
  right: 18px;
  bottom: max(18px, env(safe-area-inset-bottom));
  z-index: 150;
  display: flex;
  flex-direction: column;
  align-items: flex-end;
  gap: 14px;
}
.chat-toggle {
  position: relative;
  width: 56px;
  height: 56px;
  border-radius: 50%;
  background: var(--accent-deep);
  color: #fff;
  display: flex;
  align-items: center;
  justify-content: center;
  box-shadow: 0 10px 24px -8px rgba(30, 20, 10, .5);
  transition: transform 200ms ease, background-color 200ms ease;
}
.chat-toggle:hover { transform: scale(1.08); color: #fff; }
.chat-toggle-icon { width: 26px; height: 26px; }
.chat-toggle-icon svg { width: 100%; height: 100%; display: block; }
.chat-toggle-icon--close { display: none; }
.chat-widget.is-open .chat-toggle { background: var(--fg); }
.chat-widget.is-open .chat-toggle-icon--open { display: none; }
.chat-widget.is-open .chat-toggle-icon--close { display: block; }

.chat-panel {
  width: 340px;
  max-width: calc(100vw - 36px);
  height: 460px;
  max-height: calc(100vh - 120px);
  background: var(--surface);
  border-radius: 18px;
  box-shadow: 0 30px 60px -20px rgba(30, 20, 10, .4);
  border: 1px solid var(--border);
  display: flex;
  flex-direction: column;
  overflow: hidden;
  transform-origin: bottom right;
  animation: chat-panel-in 220ms cubic-bezier(0.2,0,0,1);
}
/* The `hidden` attribute (toggled by assets/js/chat-widget.js) needs an
   explicit override here — the plain `.chat-panel { display: flex }` rule
   above has higher specificity than the browser's own `[hidden]{display:
   none}` UA rule, so without this the panel would stay visible even while
   `hidden` is set. */
.chat-panel[hidden] { display: none; }
@keyframes chat-panel-in { from { opacity: 0; transform: scale(.92) translateY(12px); } to { opacity: 1; transform: scale(1) translateY(0); } }
@media (prefers-reduced-motion: reduce) { .chat-panel { animation: none; } }

.chat-panel__header { display: flex; align-items: center; gap: 12px; padding: 16px 18px; background: var(--fg); color: #F3E6C8; flex-shrink: 0; }
.chat-panel__avatar { width: 38px; height: 38px; border-radius: 50%; background: var(--accent-deep); color: #fff; display: flex; align-items: center; justify-content: center; flex-shrink: 0; }
.chat-panel__avatar svg { width: 20px; height: 20px; }
.chat-panel__title { display: flex; flex-direction: column; gap: 2px; }
.chat-panel__title strong { font-size: 14px; font-family: 'Inter', sans-serif; }
.chat-panel__status { font-size: 11.5px; color: #C9B896; display: flex; align-items: center; gap: 5px; }
.chat-panel__dot { width: 7px; height: 7px; border-radius: 50%; background: #4ADE80; display: inline-block; }

.chat-panel__thread { flex: 1; overflow-y: auto; padding: 16px; display: flex; flex-direction: column; gap: 10px; background: var(--bg); }
.chat-msg { max-width: 82%; padding: 10px 14px; border-radius: 14px; font-size: 13.5px; line-height: 1.5; }
.chat-msg--bot { align-self: flex-start; background: var(--surface); border: 1px solid var(--border); color: var(--fg); border-bottom-left-radius: 4px; }
.chat-msg--user { align-self: flex-end; background: var(--accent-deep); color: #FDF3E7; border-bottom-right-radius: 4px; }
.chat-msg--typing { display: flex; gap: 4px; align-items: center; padding: 12px 14px; }
.chat-msg--typing span { width: 6px; height: 6px; border-radius: 50%; background: var(--muted); animation: chat-typing 1.2s ease-in-out infinite; }
.chat-msg--typing span:nth-child(2) { animation-delay: .15s; }
.chat-msg--typing span:nth-child(3) { animation-delay: .3s; }
@keyframes chat-typing { 0%, 60%, 100% { opacity: .3; transform: translateY(0); } 30% { opacity: 1; transform: translateY(-3px); } }
@media (prefers-reduced-motion: reduce) { .chat-msg--typing span { animation: none; opacity: .6; } }

.chat-panel__form { display: flex; gap: 8px; padding: 12px; border-top: 1px solid var(--border); background: var(--surface); flex-shrink: 0; }
.chat-panel__input { flex: 1; border: 1.5px solid var(--border); border-radius: 999px; padding: 10px 16px; font-size: 13.5px; font-family: 'Inter', sans-serif; background: var(--bg); color: var(--fg); }
.chat-panel__input:focus { outline: none; border-color: var(--accent); }
.chat-panel__send { width: 40px; height: 40px; border-radius: 50%; flex-shrink: 0; background: var(--accent-deep); color: #fff; display: flex; align-items: center; justify-content: center; transition: background-color 150ms ease, transform 150ms ease; }
.chat-panel__send svg { width: 17px; height: 17px; }
.chat-panel__send:hover { background: var(--accent-deep-dark); transform: scale(1.06); }

@media (max-width: 640px) {
  .chat-widget { right: 14px; }
  .chat-toggle { width: 50px; height: 50px; }
  .chat-panel { width: calc(100vw - 28px); height: min(70vh, 520px); }
}
@media print { .chat-widget { display: none; } }
.footer-legal { font-size: 12px !important; color: #A6926F !important; line-height: 1.7 !important; padding-top: 14px; border-top: 1px solid rgba(233,220,195,0.14); }
.footer-legal a { color: #A6926F; }
.footer-legal a:hover { color: #F3E6C8; }

.footer-bottom {
  margin-top: 40px; padding-top: 22px; border-top: 1px solid rgba(233,220,195,0.14);
  display: flex; justify-content: space-between; flex-wrap: wrap; gap: 10px;
  font-size: 12px; color: #A6926F;
}

/* ---------- misc sections ---------- */
.section { padding: 84px 0; }
@media (max-width: 640px) { .section { padding: 56px 0; } }
.section-head { text-align: center; max-width: 620px; margin: 0 auto 46px; display: flex; flex-direction: column; align-items: center; gap: 14px; }
.section-head h2 { font-size: clamp(28px, 4vw, 42px); }
.section-head p { color: var(--muted); font-size: 15.5px; }