/* ============================================================================
   seed-guide.css — PROTOTYPE ONLY, not production
   Pack 2, Industry Buyer Guides: Seed ERP Buyer's Guide

   Layered on main.css + pages/knowledge-article.css + buyer-guide.css.

   buyer-guide.css is NOT modified. The Buyer Guide visual system was
   permanently frozen after Pack 1, so the industry guide adapts to the system
   rather than the system adapting to the guide. Seeds loads none of
   guide2-7.css: the prototypes stay independent.

   Reused from the frozen buyer-guide.css, unchanged:
     .bga-hero .bga-doc .bga-band          brand-aligned shell + semantic bands
     .bg-rail .bg-toc .bg-toc-m            contents, desktop and mobile
     .bg-answer .bg-tag                    direct answer + hero label
     .bg-trio                              the three warehouse storage stages
     .bg-record                            the warehouse control attributes
     .bg-qlist                             the long question sets
     .bg-pair                              "our industry is different" contrast
     .bg-show                              the eight SHOW ME scenarios
     .bg-ask .bg-principle                 the prominent question + key principle
     .bg-signoff                           the evaluation record
     .bg-proof                             Limagrain and Pioneer evidence
     .bg-check                             the thirteen-group checklist
     .bg-vendor .bg-cta .bg-sr h2.bg-rule  Exactlly band, CTA, a11y, rhythm
     .kn-note .kn-next                     knowledge-article idioms

   Only five components are defined here, each because the shared set cannot
   express it: a blockquote (nothing styles <blockquote>), the lifecycle chain,
   the two traceability directions, the five delivery classifications and the
   red flags.

   A seed guide carries a specific risk: it must never imply that one seed
   lifecycle is universal, or that industry-specific software is automatically
   better. Nothing below ranks, numbers or colours any member of a set.
   ============================================================================ */

/* ── Quotations ────────────────────────────────────────────────────────────
   The approved copy sets roughly sixty questions and statements as
   blockquotes — the densest in the programme. Nothing in main.css or
   knowledge-article.css styles <blockquote>. */

.kn-article .sd-quote {
  margin: 0 0 22px;
  padding: 16px 20px;
  background: var(--bg-s);
  border-left: 3px solid var(--b-bd);
  border-radius: 0 var(--r) var(--r) 0;
}

.kn-article .sd-quote p {
  font-size: 16.5px !important;
  line-height: 1.6;
  color: var(--t) !important;
  font-weight: 500;
  margin: 0 !important;
}

/* The question the buyer should ask instead of the one being set aside. */
.kn-article .sd-quote.is-key { background: var(--b-lt); border-left-color: var(--b); }

.sd-quotes { display: flex; flex-direction: column; gap: 8px; margin: 0 0 22px; }
.sd-quotes .sd-quote { margin: 0; }

/* ── Lifecycle chains ──────────────────────────────────────────────────────
   Four chains: the two halves of the short answer, FOLLOW THE LOT, and the
   seasonal commercial flow.

   flex-direction:row is REQUIRED and explicit. knowledge-article.css:107 sets
   flex-direction:column on .kn-article ul/ol and wins otherwise — the defect
   found in Guides 2, 5 and 6 and guarded against in Guide 7. flex-wrap:wrap is
   retained so a thirteen-stage chain wraps on a narrow screen rather than being
   forced onto one line or overflowing the page. */

.kn-article .sd-chain {
  list-style: none;
  display: flex;
  flex-direction: row;
  flex-wrap: wrap;
  align-items: center;
  gap: 8px 10px;
  margin: 4px 0 22px !important;
  padding: 16px 18px !important;
  background: var(--bg-s);
  border: 1px solid var(--br);
  border-radius: var(--r);
}

.kn-article .sd-chain li {
  display: flex;
  align-items: center;
  gap: 10px;
  padding: 0 !important;
  margin: 0;
  font-size: 14.5px !important;
  font-weight: 600;
  color: var(--t) !important;
  line-height: 1.4;
}

.kn-article .sd-chain li::before { content: none; }

.sd-chain-a { color: var(--b); font-weight: 700; }

/* ── The two traceability directions ───────────────────────────────────────
   Deliberately not .bg-pair, whose three-track grid places an arrow between the
   halves: that reads as "the left one leads to the right one". These are two
   independent procedures a buyer must demand separately, and the approved copy
   is explicit that both matter. One rule styles both panels, so neither can
   read as the primary direction. */

.sd-trace {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 14px;
  margin: 4px 0 22px;
}

.sd-trace-c {
  border: 1px solid var(--br);
  border-top: 3px solid var(--b-bd);
  border-radius: var(--r);
  background: var(--w);
  padding: 18px 20px 16px;
}

.kn-article .sd-trace-h {
  font-size: 13px;
  font-weight: 700;
  letter-spacing: .04em;
  text-transform: uppercase;
  color: var(--b);
  margin: 0 0 12px;
}

.kn-article .sd-trace-c p { font-size: 15px !important; }
.kn-article .sd-trace-c .sd-quote { margin: 0 0 14px; padding: 12px 14px; }
.kn-article .sd-trace-c .sd-quote p { font-size: 15px !important; }
.kn-article .sd-trace-c > :last-child { margin-bottom: 0 !important; }

/* ── Delivery classification ───────────────────────────────────────────────
   Five members, so neither .bg-trio nor .bg-prio — both three-track — fits.
   Unnumbered and identically styled: the approved copy states that none of the
   labels is automatically good or bad, so nothing here may imply that Standard
   is safe or Custom is a warning. */

.sd-class {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 12px;
  margin: 4px 0 22px;
}

.sd-class-i {
  border: 1px solid var(--br);
  border-radius: var(--r);
  background: var(--w);
  box-shadow: var(--sh-xs);
  padding: 16px 18px 14px;
}

.kn-article .sd-class-k {
  display: block;
  font-size: 12.5px;
  font-weight: 700;
  letter-spacing: .04em;
  text-transform: uppercase;
  color: var(--b);
  margin-bottom: 8px;
}

.kn-article .sd-class-i p {
  font-size: 14.5px !important;
  line-height: 1.6;
  margin: 0 !important;
}

/* ── Red flags ─────────────────────────────────────────────────────────────
   Sixteen of them. Restrained, exactly as Pack 1: a hairline and a heading, no
   alarm colour and no icon. The approved copy is diagnostic, not accusatory. */

.sd-flag {
  border-top: 1px solid var(--br);
  padding: 16px 0 0;
  margin: 0 0 18px;
}

.kn-article .sd-flag-h {
  font-size: 15.5px;
  font-weight: 700;
  color: var(--t);
  margin: 0 0 6px;
}

.kn-article .sd-flag p { font-size: 15px !important; }
.kn-article .sd-flag > :last-child { margin-bottom: 0 !important; }

/* ── Ground-aware surfaces on alternate bands ──────────────────────────────
   The frozen shell alternates the body ground between white and var(--bg). Two
   Seed surfaces are designed against white:

     .sd-quote   var(--bg-s)  #FAFBFC on #F7F8FA — no reading
     .sd-chain   var(--bg-s)  no reading

   Lifted to var(--w) on an alt band, keeping the panel lighter than its ground,
   which is the production idiom of white cards on a .sec-alt section.

   GUARDED, following the Pack 1 closure. Two things this selector must not do:

   1. It must not read `.bga-band.is-alt .kn-article .sd-quote`. In the aligned
      shell .kn-article is the grid container and .bga-band sits inside it, so
      .kn-article is an ANCESTOR of the band — that shape matches nothing.

   2. It must not lift every instance. The direct child combinator admits only
      surfaces whose ground really is the band column, directly or through the
      transparent .sd-quotes wrapper; a quotation nested inside a painted
      .sd-trace-c panel keeps its own fill rather than becoming white-on-white.
      :not(.is-key) leaves the intentionally blue key quotations alone. */

.bga-band.is-alt > .bga-col > .sd-quote:not(.is-key),
.bga-band.is-alt > .bga-col > .sd-quotes > .sd-quote:not(.is-key),
.bga-band.is-alt > .bga-col > .sd-chain {
  background: var(--w);
}

/* ── Responsive ─────────────────────────────────────────────────────────── */

@media (max-width: 720px) {
  .sd-trace { grid-template-columns: 1fr; }
  .sd-class { grid-template-columns: 1fr; }
}

@media print {
  .sd-quote, .sd-trace-c, .sd-class-i { box-shadow: none; break-inside: avoid; }
  .sd-flag { break-inside: avoid; }
  .sd-trace { grid-template-columns: repeat(2, 1fr); }
  /* The chain reads as a sequence on paper without its box. */
  .kn-article .sd-chain { background: none; border: 0; padding: 0 !important; }
}
