/* ═══════════════════════════════════════════════════════════════════════════
   blog-content.css — design system for the modern self-contained posts.

   16 posts were authored with an inline "Design System v3" <style> shell
   (.vshr-blog components). WordPress kses stripped those <style> blocks on
   import, so the posts rendered as raw unstyled markup. This restores the
   system as a THEME stylesheet (DRY, survives kses), loaded on single posts.

   Scoped to .vshr-blog, so the 166 plain posts are unaffected.

   The rebuilt single-post FRAME (content-single.blade.php) already provides the
   header, featured image, sidebar ToC, author card and closing CTA — so the
   post's OWN duplicates of those (.vshr-blog-hero / .toc / .cta-section /
   .author-card) are hidden to avoid double chrome. The unique body components
   (.lead / .insight-box / .checklist-card / .faq-*) are what we style.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ── hide chrome the new frame already renders (no double header/toc/cta/author) ── */
.e-content .vshr-blog-hero,
.e-content .toc,
.e-content .cta-section,
.e-content .author-card { display: none !important; }

/* ── body typography ── */
.vshr-blog { color: #0f1a2a; font-family: 'Work Sans', var(--font-sans, system-ui), sans-serif; }
.vshr-blog p { color: #0f1a2a; font-size: 17px; line-height: 1.78; margin-bottom: 20px; }
.vshr-blog h2 { color: #07192E; font-size: 26px; font-weight: 700; line-height: 1.18; letter-spacing: -0.01em; margin: 44px 0 14px; }
.vshr-blog h2:first-of-type { margin-top: 0; }
.vshr-blog h3 { color: #07192E; font-size: 17px; font-weight: 700; line-height: 1.25; }
.vshr-blog ul, .vshr-blog ol { color: #0f1a2a; margin: 0 0 16px; padding-left: 24px; font-size: 17px; line-height: 1.7; }
.vshr-blog li { margin-bottom: 3px; }
.vshr-blog li::marker { color: #2170b5; }
.vshr-blog a { color: #1665a8; text-decoration: underline; text-decoration-color: rgba(22,101,168,.32); text-underline-offset: 3px; }
.vshr-blog a:hover { color: #07192E; text-decoration-color: #07192E; }
.vshr-blog strong { color: #07192E; }
.vshr-blog .lead { font-size: 18px; color: #0f1a2a; line-height: 1.8; margin-bottom: 28px; }

/* ── insight boxes (gradient accent bar) ── */
.vshr-blog .insight-box {
  background: #f6f8fb; border-radius: 0 10px 10px 0; padding: 16px 20px 16px 24px;
  margin: 24px 0; position: relative; overflow: hidden;
}
.vshr-blog .insight-box::after {
  content: ''; position: absolute; left: 0; top: 0; bottom: 0; width: 5px;
  background: linear-gradient(180deg, #2170b5, #0a92d0, #ea1c72);
}
.vshr-blog .insight-box .label { color: #2170b5; font-size: 11px; font-weight: 700; text-transform: uppercase; letter-spacing: 1.6px; margin-bottom: 6px; display: block; }
.vshr-blog .insight-box p { font-size: 15px; line-height: 1.65; margin-bottom: 0; }
.vshr-blog .insight-box + .insight-box { margin-top: 8px; }

/* ── checklist cards (numbered) ── */
.vshr-blog .checklist-card {
  background: #fff; border: 1px solid #dce1e8; border-radius: 10px;
  padding: 32px 32px 32px 36px; margin: 32px 0;
  box-shadow: 0 1px 3px rgba(0,0,0,.06), 0 1px 2px rgba(0,0,0,.04);
  position: relative; overflow: hidden;
}
.vshr-blog .checklist-card::before {
  content: ''; position: absolute; left: 0; top: 0; bottom: 0; width: 5px;
  background: linear-gradient(180deg, #2170b5 0%, #0a92d0 40%, #ea1c72 100%);
  border-radius: 10px 0 0 10px;
}
.vshr-blog .checklist-card h3 { color: #07192E; font-size: 17px; font-weight: 700; margin-bottom: 24px; display: flex; align-items: center; gap: 10px; }
.vshr-blog .checklist-card h3 .icon-circle { background: #edf4fb; width: 32px; height: 32px; border-radius: 50%; display: flex; align-items: center; justify-content: center; flex-shrink: 0; }
.vshr-blog .checklist-card h3 svg { color: #2170b5; width: 15px; height: 15px; }
.vshr-blog .check-item { display: flex; gap: 12px; padding: 10px 0; border-bottom: 1px solid #edf0f5; align-items: flex-start; }
.vshr-blog .check-item:last-child { border-bottom: none; padding-bottom: 0; }
.vshr-blog .check-num { background: #2170b5; color: #fff; width: 28px; height: 28px; border-radius: 50%; font-size: 12px; font-weight: 700; display: flex; align-items: center; justify-content: center; flex-shrink: 0; margin-top: 2px; }
.vshr-blog .check-content strong { color: #07192E; display: block; font-size: 15px; font-weight: 600; margin-bottom: 4px; }
.vshr-blog .check-content span { color: #5f6d7e; font-size: 15px; line-height: 1.65; }

/* ── FAQ accordion ── */
.vshr-blog .faq-section { margin-top: 52px; padding-top: 44px; border-top: 1px solid #dce1e8; }
.vshr-blog .faq-section h2 { text-align: center; margin-bottom: 32px; }
.vshr-blog .faq-item { border: 1px solid #edf0f5; border-radius: 10px; margin-bottom: 10px; overflow: hidden; background: #fff; }
.vshr-blog .faq-item:hover { box-shadow: 0 1px 3px rgba(0,0,0,.06); border-color: #dce1e8; }
.vshr-blog .faq-item.active { border-color: #2170b5; box-shadow: 0 2px 10px rgba(33,112,181,.08); }
.vshr-blog .faq-question { width: 100%; border: none; background: #fff; padding: 20px 24px; font-size: 15px; font-weight: 600; color: #07192E; cursor: pointer; display: flex; justify-content: space-between; align-items: center; gap: 14px; text-align: left; font-family: inherit; line-height: 1.4; }
.vshr-blog .faq-question:hover { background: #f6f8fb; }
.vshr-blog .faq-question svg { flex-shrink: 0; width: 18px; height: 18px; color: #2170b5; }
.vshr-blog .faq-item.active .faq-question { background: #f6f8fb; }
.vshr-blog .faq-answer-inner { padding: 0 24px 20px; font-size: 15px; color: #0f1a2a; line-height: 1.72; }

/* ── disclaimer ── */
.vshr-blog .vshr-disclaimer { margin-top: 40px; padding: 16px 20px; background: #f9fafb; border-radius: 10px; border: 1px solid #e5e7eb; font-size: 11.5px; line-height: 1.65; color: #6b7280; }
.vshr-blog .vshr-disclaimer p { margin: 0; font-size: 11.5px; color: #6b7280; }
.vshr-blog .vshr-disclaimer strong { color: #4b5563; }

@media (max-width: 640px) {
  .vshr-blog .checklist-card { padding: 20px 18px; }
  .vshr-blog .insight-box { padding: 16px; }
}

/* ═══════════════════════════════════════════════════════════════════════════
   SUPPLEMENTAL — recovered .vshr-blog components (2026-06-25)

   The classes below were used inside the modern posts but had no rule in this
   file: their definitions lived in the per-post inline <style> that kses
   stripped on import. Recovered from the raw backups and re-expressed in the
   brand palette (navy #07192E · blue #2170b5 · link #1665a8 · magenta #ea1c72 ·
   surface #f6f8fb). Everything stays scoped to .vshr-blog so it cannot leak to
   the 166 plain posts.

   NOTE on classes intentionally NOT styled here:
   • hero-meta-item / hero-meta / hero-badge etc. live inside .vshr-blog-hero,
     which the frame already hides (see top of file) — styling them is moot.
   • vshr-utility is a bare semantic marker (no inline rule of its own in the
     originals); it only ever co-occurs on already-styled/hidden blocks
     (faq-section, author-card[hidden], vshr-disclaimer), so no rule is added.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ── proof / red-flag rows inside checklist cards (callout-label is their tag) ──
   Two evidence chips that sit under a .check-content line: a green "Proof" row
   and an amber "Red flag" row. callout-label is the small uppercase tag. ── */
.vshr-blog .check-proof,
.vshr-blog .check-redflag {
  display: flex;
  align-items: flex-start;
  gap: 8px;
  margin-top: 9px;
  padding: 8px 11px;
  border-radius: 8px;
  font-size: 13px;
  line-height: 1.55;
}
.vshr-blog .check-proof  { background: #f0fdf4; border-left: 3px solid #10b981; }
.vshr-blog .check-redflag { background: #fff7ed; border-left: 3px solid #f59e0b; }
.vshr-blog .check-proof > span,
.vshr-blog .check-redflag > span { color: #374151; font-size: 13px; line-height: 1.55; }
.vshr-blog .callout-label {
  flex-shrink: 0;
  font-size: 10.5px;
  font-weight: 700;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  white-space: nowrap;
  padding-top: 1px;
}
.vshr-blog .check-proof  .callout-label { color: #065f46; }
.vshr-blog .check-redflag .callout-label { color: #92400e; }

/* ── alternate inline "red flag" note (a single post uses .check-red-flag as a
   block span inside .check-content, with a <strong> uppercase prefix) ── */
.vshr-blog .check-red-flag {
  display: block;
  margin-top: 8px;
  font-size: 13px;
  line-height: 1.55;
  font-style: italic;
  color: #991b1b;
}
.vshr-blog .check-red-flag strong {
  display: inline;
  margin-right: 3px;
  font-style: normal;
  font-weight: 700;
  font-size: 11.5px;
  letter-spacing: 0.04em;
  text-transform: uppercase;
  color: #b42318;
}

/* ── source / citation note (sits under a section or the article body) ── */
.vshr-blog .source-note {
  margin: 18px 0 24px;
  font-size: 13px;
  line-height: 1.65;
  color: #5f6d7e;
}
.vshr-blog .source-note a { color: #1665a8; }

/* ── pull quotes ─────────────────────────────────────────────────────────────
   .pull-quote (.vshr-pull-quote) ships with an inline style attribute that
   survives kses, so we only brand its inner type and supply a fallback rule for
   posts where the inline style is absent (no !important — inline wins by design,
   we just fill the gaps). .vshr-pullquote is the bare variant with no inline
   style at all and needs the full treatment. ── */
.vshr-blog .pull-quote,
.vshr-blog .vshr-pull-quote,
.vshr-blog .vshr-pullquote {
  margin: 28px 0;
  padding: 18px 22px;
  background: #f6f8fb;
  border-left: 4px solid #2170b5;
  border-radius: 0 10px 10px 0;
}
.vshr-blog .pull-quote p,
.vshr-blog .vshr-pull-quote p,
.vshr-blog .vshr-pullquote p {
  margin: 0;
  font-size: 18px;
  line-height: 1.55;
  font-style: italic;
  color: #1f2937;
}
.vshr-blog .vshr-pullquote cite {
  display: block;
  margin-top: 12px;
  font-size: 14px;
  font-style: normal;
  line-height: 1.4;
  color: #5f6d7e;
}
.vshr-blog .vshr-pullquote cite strong { color: #07192E; }

/* ── FAQ answer collapse ─────────────────────────────────────────────────────
   Two FAQ markups exist across the modern posts:
   (A) native <details class="faq-item">…<div class="faq-answer"> — the browser
       handles show/hide, so .faq-answer only needs base spacing.
   (B) <div class="faq-item"><button class="faq-question" onclick="toggleFaq()">
       …<div class="faq-answer"> — the toggleFaq() helper was inline and was
       stripped with the rest of the <style>/<script>, so it no longer exists.
       We collapse .faq-answer by default and expand it under .faq-item.active,
       and re-supply the click wiring in single-post.js (see jsCode in handoff).
   The :not(details) guard keeps the collapse OFF the native <details> variant
   (whose open answers carry no .active class and would otherwise stay shut). ── */
.vshr-blog details.faq-item .faq-answer { padding-bottom: 4px; }

.vshr-blog .faq-item:not(details) > .faq-answer {
  display: grid;
  grid-template-rows: 0fr;
  transition: grid-template-rows 280ms ease;
}
.vshr-blog .faq-item:not(details).active > .faq-answer { grid-template-rows: 1fr; }
.vshr-blog .faq-item:not(details) > .faq-answer > .faq-answer-inner { overflow: hidden; }

/* rotate the chevron in the button (Pattern B) when its item is open */
.vshr-blog .faq-item:not(details) .faq-question svg { transition: transform 200ms ease; }
.vshr-blog .faq-item:not(details).active .faq-question svg { transform: rotate(180deg); }