/* ===========================================================================
   CASE EXTRAS. Loaded by every case study, AFTER every shared stylesheet,
   because both things in here have to beat swiss.css: the icon list turns
   off a dash that swiss sets with one type selector more than this file
   uses, and it reads --mark-top, which swiss declares.

   Written for Hasta on 2026-10-27 and moved here the same day, when he
   asked for the icons and the layouts on the other case studies too.
   Nothing in it fires unless a page opts in by putting .ico-list on a list
   or <strong> in a sentence, so linking it costs a page nothing.

   Hasta keeps its own file for the one thing that is page-specific: the
   size of its pictures.
   =========================================================================== */


/* ---------------------------------------------------------------------------
   1. NAMED TERMS

   The page already has two inline weights: .principles li b, which leads a
   list row, and .why b, which is the mono "TRADE-OFF:" marker. A named law,
   a model name or a term of art inside a sentence is a third thing, and the
   browser default for <strong> is 700 against a 400 body, which reads as a
   shout two words wide. 600 is one step up from the 500 the list leads use,
   which is what tells a term apart from a whole bold sentence.
   --------------------------------------------------------------------------- */

[data-case] .col p strong,
[data-case] .col li strong {
  font-weight: 600;
  color: var(--ink);
}


/* ---------------------------------------------------------------------------
   2. THE ICON LIST

   ul.plain.ico-list is ul.plain with its 6px dash swapped for a 16px line
   icon. Everything else - the hairline between rows, the 34px indent, the
   24px padding block - is inherited untouched, so an icon row sits on the
   same grid as a dashed one.

   The icon is placed by the SAME formula the dash uses (swiss.css 1220):
   the li's own top padding, plus half a line box, less half the icon. It
   therefore sits on the middle of the first line at any body size, and it
   follows --mark-top when section 17 changes the row padding.

   left: 3px, not the dash's 8px. The icons' own paths start about 2.6 units
   into a 16 unit box, so a 3px left puts their drawn edge within a hair of
   where the dash starts and keeps a clear 13px channel before the text.
   --------------------------------------------------------------------------- */

/* A list of named things is a block, not three more sentences: without this
   the paragraph after the Outcome rows sat on the last row's padding alone
   and read as a fourth item with its icon missing. .why keeps its own s5. */
[data-case] .col .ico-list + p:not(.why) { margin-top: var(--s3); }

/* ul.plain.ico-list, not .ico-list: swiss.css sets the dash with
   `ul.plain li::before`, one type selector more than a bare class, and it
   loads before this file. Written as `.ico-list li::before` the dash kept
   painting - 6x1px of ink-40 at left: 8px, inside the icon's own box, which
   is why it was invisible in a screenshot and obvious in a probe. */
ul.plain.ico-list li::before { content: none; }

.ico-list .ico {
  position: absolute;
  left: 3px;
  top: calc(var(--mark-top, 0px) + var(--lh-body) * 0.5em - 8px);
  width: 16px;
  height: 16px;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.5;
  stroke-linecap: round;
  stroke-linejoin: round;
  /* The dash's colour. An icon at full ink would outweigh the sentence it
     is pointing at; this is a marker, not an illustration. */
  color: var(--ink-40);
}


/* ---------------------------------------------------------------------------
   3. THE LEAD LINE  —  p.lede

   The reading problem on these pages was never the amount of copy, it was
   that every sentence had the same rank, so a skimmer had nothing to land
   on between one h3 and the next and the column read as a wall.

   The fix reuses a rank the page already owns. swiss.css has exactly one
   promoted-sentence device, --t-quote (clamp 20->24px, 1.3, -0.01em, 400),
   and two things wear it: .lead-note above the hero and .hmw at the end of
   The problem. One per page. p.lede is the same declaration applied once
   per argument instead of once per page: the sentence that carries a
   decision, promoted verbatim out of its own paragraph.

   SIZE ALONE, and the measure. Weight stays 400 and colour stays --ink,
   which is what body copy already is. Going bold and large and coloured at
   the same time would read as a different website; one axis is enough when
   the ratio is 1.5x (24/16 desktop) and the leading drops from 1.6 to 1.3
   at the same time, which makes the block visibly denser as well as bigger.
   The 38ch cap is a ceiling, not a visible step: body copy runs 60ch (555px
   at 1280+) and a 38ch lede caps at 527px, so the cap is doing one job only,
   which is stopping a long promoted sentence from filling the whole measure
   and reading as a big paragraph instead of a line. Up to about ten words
   still holds a single line. It is deliberately tighter than .hmw's 40ch
   and .lead-note's 44ch, because those two sit alone and a lede has body
   copy immediately under it.

   HOW THE THREE PROSE RANKS RELATE. Body copy is the middle of three, and
   the other two leave it in opposite directions on different axes:
     .lede   16 -> 24px, colour unchanged   (bigger, same ink)
     p       16px, --ink                    (the baseline)
     .why    16px unchanged, ink at 68%     (same size, less ink)
   Nothing is added to .why and nothing is taken off it. The two can never
   be confused because they do not compete on the same property, and they
   never meet: a .lede opens a decision and a .why closes it.

   AGAINST THE HEADINGS. h3 on these pages is 18px/500, 1.125x body - a
   bookmark, not a headline - so a 24px lead line under it is larger than
   its own heading. That is deliberate. The number and the h3 together are
   a title block that says what the decision is about; the lead line says
   what the decision WAS. The skimmer should be caught by the argument, not
   by the label. h2 keeps the top of the ladder at 28px/700, and weight is
   what keeps 28/700 clearly above 24/400.
   --------------------------------------------------------------------------- */

[data-case] .col p.lede {
  max-width: 38ch;
  font-size: var(--t-quote);
  line-height: var(--lh-quote);
  letter-spacing: var(--tr-quote);
  font-weight: var(--w-quote);
  color: var(--ink);
  /* Two or three lines of near-equal length, rather than a short orphan on
     the last line. At this size an orphan is the thing you notice. */
  text-wrap: balance;
}

/* The gap below is bigger than the gap above. h3 keeps its own 24px bottom
   margin, so a lead line sits 24px under its heading and 32px above its
   body copy, and the heading and the lead line group as one unit while the
   body reads as the detail hanging off it. Every gap in this column was
   24px before, which is a large part of why it read as a wall: nothing in
   the spacing told you where one thought ended.

   .col p and .col p:last-child are both (0,2,0) in swiss.css and would
   otherwise flatten this - the same trap the .hmw comment at swiss.css 1068
   records. (0,3,1) here clears both. */
[data-case] .col p.lede { margin: 0 0 var(--s4); }

/* Supaca nests its decision copy in .d-words beside a screen column, and
   that column is ~420px at 1280+. The cap above is a max-width, so it does
   nothing there and the lead line simply takes the column. No page-specific
   size: one pattern. */

/* ===== Agent pipeline diagram (Produsa #how) =======================
   Drawn from the page's own tokens — ink on paper, one accent, thin
   rules. Connected cards with a chevron in each gap; a single branch
   shows the self-check. No colour or shape outside the system. */
.amap { margin: var(--s2) 0 var(--s3); }
.amap__kick {
  font-family: var(--sans); font-size: 12px; font-weight: 600;
  letter-spacing: 0.08em; text-transform: uppercase; color: var(--label);
  margin: 0 0 var(--s2);
}
.amap__pipe {
  display: flex; align-items: stretch; gap: 22px; list-style: none;
  margin: 0 0 var(--s5); padding: 0;
}
.amap__pipe > li {
  position: relative; flex: 1 1 0; min-width: 0;
  display: flex; flex-direction: column; justify-content: center; gap: 3px;
  border: 1px solid var(--rule); border-radius: 10px; background: var(--surface);
  padding: 15px 13px; font-size: 14px; font-weight: 600; color: var(--ink); line-height: 1.22;
}
.amap__n { font-size: 11px; color: var(--accent); letter-spacing: 0.04em; font-variant-numeric: tabular-nums; }
.amap__cap {
  flex: 0 0 auto; max-width: 104px; background: var(--bg); color: var(--soft);
  justify-content: center; text-align: center; font-size: 12.5px; font-weight: 600;
}
.amap__pipe > li:not(:last-child)::after {
  content: ""; position: absolute; right: -16px; top: 50%; width: 9px; height: 9px;
  border-top: 1.6px solid var(--soft); border-right: 1.6px solid var(--soft);
  transform: translateY(-50%) rotate(45deg);
}
.amap__check { border-top: 1px dashed var(--rule); padding-top: var(--s4); }
.amap__fork { display: flex; flex-wrap: wrap; align-items: center; gap: 16px 34px; }
.amap__chip {
  position: relative; display: inline-block; border: 1.5px solid var(--ink); border-radius: 999px;
  padding: 10px 18px; font-size: 14px; font-weight: 600; color: var(--ink); background: var(--surface);
}
.amap__out { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; gap: 9px; }
.amap__out li { position: relative; padding-left: 28px; font-size: 14px; color: var(--body); line-height: 1.4; }
.amap__out li::before { position: absolute; left: 1px; top: -1px; font-size: 15px; font-weight: 700; }
.amap__pass::before { content: "\2713"; color: var(--accent); }
.amap__fail::before { content: "\21BA"; color: var(--soft); }
.amap__fork { flex-direction: column; align-items: flex-start; gap: 14px; }
@media (max-width: 639px) {
  .amap__pipe { flex-direction: column; gap: 20px; }
  .amap__cap { max-width: none; }
  .amap__pipe > li:not(:last-child)::after {
    right: auto; left: 50%; top: auto; bottom: -15px;
    transform: translateX(-50%) rotate(135deg);
  }
}
