/* ==========================================================================
   SHOP BY BIKE — the ribbon (.sfbr), home section 4, container sfbk01

   Replaces the bike wall (.sfbw), which stays in git: bike-wall.css/js and
   assets/html/bike-wall.html are untouched, so going back is a widget write
   plus re-enabling its enqueue.

   The arrangement is detroit.paris's home hero, measured value by value in
   docs/research/2026-11-12-detroit-paris-hero-ribbon.md and reproduced at
   docs/research/detroit-ribbon/. READ THAT FIRST — most of the numbers here
   are theirs and the write-up says how each was obtained.

   WHAT IS THEIRS: the card shape, the shared bottom-left origin, the scale
   ramp .055 -> 1.6, zIndex round(scale*10), --parallax-x -15%..0%, the
   110%-wide picture, the caption above the card and its 1/scale.

   WHAT IS OURS, and says so in place: the carbon surface, the finite
   runway (their page never scrolls; this one has a section below it), the
   gap ratio, and the phone fallback.
   ========================================================================== */

:root{
  /* THE SURFACE. The house pair — every band on the front page carries
     both diagonals; one alone reads as corduroy. See "One surface for the
     home page" in CLAUDE.md. */
  --sfbr-page:   var(--wp--preset--color--base, #171717);
  --sfbr-ink:    #f2f2f4;
  --sfbr-accent: var(--wp--preset--color--accent-1, #ec1e79);

  /* THE HEADLINE IS A SHADE SOFTER THAN EVERYTHING ELSE, ON PURPOSE.

     The reference sets this type black on white; here it is light on
     carbon, and light on dark irradiates — the ink bleeds into the ground
     and the strokes read fatter and the counters tighter than the same
     glyphs do the other way round. The geometry is identical (measured:
     "CRAFTING" is 3.4398em here against their 3.4399em), so this is purely
     an optical correction, and it only matters at display size.

     #dcdce1 on #171717 is 13.5:1, so nothing is given up on contrast. The
     captions, the lede and everything small stay on --sfbr-ink, where
     legibility matters more than the bloom. Set this to var(--sfbr-ink)
     to turn the correction off. */
  --sfbr-ink-display: #dcdce1;

  /* THE CARD — theirs. 30vw x 27.5vw, 12:11. Their rule is min-width:30rem
     against a root font-size of exactly 1vw, so 30rem IS 30vw. */
  /* SQUARE — operator, 2026-11-12. The reference's card is 30rem x 27.5rem,
     a 12:11 box; this one is 1:1.

     The ribbon maths does not care: the loop, the ramp and ce are all
     driven by WIDTH, so the staircase and the brand order are untouched.
     What changes is the height a full-size card reaches — at the 2.1 step
     a 30vw square is 63vw tall, which is 140vh of a 606px-tall stage, so
     more of a big photograph is cropped top and bottom than before. The
     stage is `overflow: hidden` and the reference crops too; raise
     --sfbr-card-w if that ever matters more than the shape. */
  --sfbr-card-w: 30vw;
  --sfbr-card-h: 30vw;

  /* THEIRS. The step between cards is HALF a card width, and it is what
     makes them pack tight instead of sitting in a row.

     Two cards overlap when the scaled width exceeds the step: 30s > 30g.
     At their 0.5 that starts at scale 0.5 — a third of the way up the
     ramp — so everything from there on is a continuous collage. At 0.75
     it does not start until 0.75, and every card below that has carbon
     showing between it and its neighbour. That was the visible
     difference from the reference and it is why 0.75 is gone.

     0.75 WAS PUT IN TO AVOID A DUPLICATE THAT CANNOT HAPPEN, and the
     reasoning was wrong. The worry was that with only six cards the loop
     (90vw) is shorter than the 130vw a card can be seen across, so a
     brand would be on screen twice. It cannot: the modulo in
     bike-ribbon.js gives every card exactly ONE position, inside a
     90vw window, and nothing is ever drawn at two places. Swept 91
     positions through the runway: zero duplicates.

     What the short loop actually costs is that the band's right edge is
     covered by a card's WIDTH rather than by another card's origin.
     Measured across the runway: the rightmost edge never falls below
     96.99vw, so it never opens up. Worst gap between any two
     neighbours is 5.93vw, among the slivers at the left — theirs
     measures about 6.4vw in the same place. */
  --sfbr-gap-ratio: .5;

  /* Set per frame by bike-ribbon.js, per card. */
  --parallax-x: 0%;

  /* The page gutter. 44px is the navbar logo's line, which .sfidx and the
     hero also sit on. */
  --sfbr-gutter: clamp(20px, 3.1vw, 44px);
}

/* --------------------------------------------------------------------------
   1 · The section and its runway
   THEIR PAGE DOES NOT SCROLL — the hero is fixed and the wheel is captured
   for ever. Ours cannot be: there is a dealer wall under it. So the ribbon
   is driven by a FINITE runway instead, and travels exactly one loop over
   it: every brand passes the big end once, and at the end the ribbon is
   back where it started, so the release is seamless.

   `position: sticky`, never a ScrollTrigger pin. A pin writes an inline
   pixel width onto a .pin-spacer and gives the whole page a horizontal
   scrollbar — CLAUDE.md records that failure at length, and page 42 has
   had zero .pin-spacer since 2026-11-10. Keep it that way.
   -------------------------------------------------------------------------- */

.sfbr{
  /* 135vw of runway is 1:1 with the ribbon's own travel, so the cards move
     at the speed the page would have. The svh floor keeps a usable runway
     on a narrow window. */
  --sfbr-runway: max(135vw, 120svh);

  /* THE CARD OVERLAY, AND IT IS THE DIAL THE OPERATOR KEEPS TURNING.
     Three states in one afternoon, all measured as mean luma over the six
     real files (the rule on .sfbr__img has the method):

         .34, no lift   14.1   "same overlay as section 2"
         0,   lift 1.55 32.3   matched section 2 exactly   — too light
         .30, lift 1.55 22.6   "moreeee darkkkkk"          — still too light
         .55, lift 1.55 14.5   "moreeeeee darkk"           — HERE

     The result is simply `lift x (1 - overlay)`, so the arithmetic is
     linear and needs no sweep: .40 -> 19.4, .50 -> 16.2, .65 -> 11.3.
     TURN THIS, not the lift — the lift is what keeps the chrome and the
     rim light readable at any darkness, and dropping it instead flattens
     the badge into the casting. */
  --sfbr-overlay: .55;

  /* The lift that does the matching — see .sfbr__img. */
  --sfbr-lift: 1.55;

  position: relative;
  height: calc(100svh + var(--sfbr-runway));

  /* Pulls into section 3's bottom padding — pure background, same base and
     weave both sides, and capped under that padding so the video is never
     reached. .sfbw carried exactly this; see "The gap between sections 2
     and 3" in CLAUDE.md for why it is a negative margin and not a smaller
     padding up there. */
  margin-top: calc(-1 * clamp(20px, 2.6vw, 44px));

  /* CONTAINS THE HEADLINE'S BLEND. `.sfbr__head` is
     `mix-blend-mode: difference`, and without a stacking context here the
     blend group would climb past this section and mix with whatever the
     page paints behind it. Isolating on the SECTION rather than the stage
     is deliberate: the backdrop then includes this band's own background,
     so the type inverts to near-white over bare carbon instead of
     blending against nothing. */
  isolation: isolate;

  background-color: var(--sfbr-page);
  background-image:
    repeating-linear-gradient( 45deg, rgba(255,255,255,.025) 0 2px, transparent 2px 4px),
    repeating-linear-gradient(-45deg, rgba(0,0,0,.35)        0 2px, transparent 2px 4px);
  color: var(--sfbr-ink);
}

.sfbr__stage{
  position: sticky;
  top: 0;
  height: 100svh;
  overflow: hidden;
}

/* --------------------------------------------------------------------------
   2 · The heading
   Inside the stage, so it holds while the ribbon runs. Section 2's ladder
   and type — Inter 600 on sohub's five values, which CLAUDE.md says to
   change in both files or neither.
   -------------------------------------------------------------------------- */

.sfbr__head{
  position: relative;

  /* THE HEAD CARRIES NO z-index OF ITS OWN, AND THAT IS LOAD-BEARING
     RATHER THAN TIDY (operator, 2026-11-12: "for title YOUR BIKE OUR
     PARTS i dont want z-index: 1, that z index only for short title
     only").

     The two halves of this block now sit on OPPOSITE sides of the
     ribbon — the big title under the cards at the reference's own
     z-index 1, the lede over them at 30 — so they cannot both be
     children of a z-indexed parent. **A z-index on an element creates a
     stacking context, and a descendant can never escape it**: with
     `z-index: 30` here the lede's own 30 would be resolved INSIDE the
     head and a card at 10 would still paint under both. Dropping to
     `auto` puts both children in the section's own stacking context,
     where they are ordered against the cards directly.

     Nothing else in this rule may reintroduce one — a transform, an
     opacity under 1, a filter or a `mix-blend-mode` other than normal
     all create a stacking context, and the blend ABOVE this comment was
     exactly such a case until it was turned off. */

  /* THE TYPE INVERTS AGAINST WHATEVER PASSES UNDER IT — operator,
     2026-11-12. The headline sits over the ribbon, and light grey on a
     bright photograph does not read: "OUR PARTS." and the lede went
     invisible every time a lit card slid beneath them.

     `difference` gives |backdrop - source|. With a PURE WHITE source that
     is exactly the inverse of the backdrop: near-white over this band's
     carbon (|23 - 255| = 232), dark over a bright photo. So it reads
     everywhere with no scrim, no layout change, and the cards keep
     running full-bleed.

     THE SOURCE MUST BE #fff OR THE INVERSION IS PARTIAL, which is why the
     type below is pure white and NOT --sfbr-ink-display. That token is
     the dark-bloom correction and it is superseded here: the blend
     decides the painted colour, so dialling the source back only dims the
     inversion. Remove this one line and the tokens take over again.

     Note the blend is contained by `isolation: isolate` on .sfbr, and
     that it disables subpixel antialiasing on this text — expected, and
     invisible at these sizes. */
  mix-blend-mode: difference;
  /* --sfbr-nav-clear is measured off the real bar by bike-ribbon.js. The
     stage is sticky at top:0, so at one scroll position the heading sits
     exactly where the floating navbar is. The hero solves the same problem
     with --sfop-under; do not hardcode a bar that has changed height
     twice. The fallback only has to be sane before the script runs. */
  /* Theirs puts the block at x=20, y=54 against 1353x606 — 1.5vw and 4vw.
     The 4vw has to clear the floating navbar here, which theirs does not
     have, so it is the larger of the two. */
  padding:
    max(4vw, calc(var(--sfbr-nav-clear, 104px) + clamp(12px, 1.4vw, 24px)))
    var(--sfbr-gutter)
    0
    1.5vw;
  /* The fixed social rail is 46px wide (40 below 782px) at z-index 90 on
     the left edge of every page. The house clearance, which disappears on
     its own once the gutter passes 58. The CARDS do not get it: a
     photograph passing under the rail is what the rail does everywhere. */
  padding-left: calc(1.5vw + max(0px, 58px - 1.5vw));
  pointer-events: none;
}

/* ...BUT ONLY WHERE THERE IS SOMETHING TO INVERT AGAINST (2026-11-12).

   The blend was pitched against PHOTOGRAPHS, which are bright and varied.
   Against a PLACEHOLDER it does the one thing it was added to prevent: the
   card is a magenta bloom over #0d0d10, so |backdrop - white| comes back a
   pale MINT, while the same word over bare carbon comes back near-white.
   "OUR PARTS." then changes colour halfway across and reads as a word cut
   in two — which is exactly what the operator saw and called "tercut".

   It is nothing to do with the mask, the leading or the clip, all of which
   this file has blamed before for a headline that looked cut.

   So the blend follows the art. The shortcode prints data-sfbr-art, and
   while it is "off" every card is a dark placeholder, nothing bright can
   pass under the type, and plain light ink reads perfectly — which also
   puts --sfbr-ink-display back in charge, the dark-bloom correction the
   blend supersedes.

   THIS IS A STATE, NOT A REVERSAL. Set art="on" and the inversion returns
   with the photographs it was written for, with nothing here to edit.

   SUPERSEDED 2026-11-12, THE SAME DAY: THE OVERRIDE IS UNCONDITIONAL NOW,
   because the photographs turned out to be the bad backdrop too.

   The six brand shots the operator supplied are near-black castings lit
   with a magenta rim — the brand magenta, the same #ec1e79 the placeholder
   bloom was painted in. |white - magenta| is (19,225,134): the identical
   pale MINT, so a rim light passing under "OUR PARTS." would cut the word
   in two exactly as the placeholder did. The art attribute never predicted
   that; what the blend actually needs is a backdrop with no large flat
   areas of ONE strong hue, and this band has not had one yet.

   The `mix-blend-mode: difference` above is therefore dead while this rule
   stands. It is kept rather than deleted: re-scope these two selectors
   back to [data-sfbr-art="on"] and it returns, which is the right move the
   day the cards carry bright, varied photography. */
.sfbr .sfbr__head{
  mix-blend-mode: normal;
  --sfbr-head-ink: var(--sfbr-ink-display);
}

/* The lede is small, and small type keeps the FULL ink — the dark-bloom
   correction above is for display sizes only. Same split the file already
   makes for the captions and the counts. */
.sfbr .sfbr__lede{ color: var(--sfbr-ink); }

/* THE HEADLINE IS THE REFERENCE'S, CAP-CORRECTED. Every number below was
   derived in docs/research/detroit-ribbon/ribbon.css and the reasoning is
   there in full — this is the short version.

   Their display face is Mangogrotesque, licensed. Nothing free is as
   narrow, so the stand-in is Anton — but the two faces put very different
   glyphs inside the same em, so matching their FONT-SIZE does not match
   their type. Scanned from pixels, same string, same size, with a plain
   sans-serif control that read 0.7275 on both machines:

       Mangogrotesque   cap 0.715em    "CRAFTING" 2.271em
       Anton            cap 0.8675em   "CRAFTING" 3.440em

   Anton's caps are 21% bigger. So the size comes off the CAP:

       their cap height  = .715  x 14.375vw = 10.278vw
       our font-size     = 10.278 / .8675   = 11.85vw
       our leading       = (.7513 x 14.375) / 11.85 = .9115em
       our squeeze       = (2.271 x 14.375) / (3.440 x 11.85) = .801

   DO NOT probe the cap height on screen. Dropping the leading until the
   two lines "touch" reads as .70em for Anton and it is .8675 — a small
   crop of a very heavy condensed face does not show a 10px collision. */

/* THE THREE LABELS IN THIS BAND ARE ARCHIVO EXTRA-CONDENSED 600
   (operator, 2026-11-12) — this one, the card caption and the
   PLACEHOLDER tag. They were Chakra Petch 500, which is the house
   label face everywhere else on the site; this band is deliberately
   the exception, and it pairs with section 3 taking Chakra Petch for
   its accents in the same pass.

   `font-stretch` NEEDS THE wdth AXIS IN THE URL and this band's own
   handle already carries it — `Archivo:wdth,wght@62.5..100,400..900`.
   Without it the browser renders normal-width Archivo and nothing
   reports the difference: a label that is simply too wide, in a face
   nobody picked.

   TRACKING IS .14em ON ALL THREE now, the caption's own value. A
   condensed face is narrower per character, so the eyebrow's .16em
   and the tag's .18em opened into gaps at this width.

   NOTE THIS EYEBROW IS NOT ON THE PAGE. The shortcode defaults it
   empty and the live widget passes nothing, so it only renders if
   someone sets an eyebrow attribute. It is kept in step anyway. */
.sfbr__eyebrow{
  /* With the lede, over the cards — it is a label, not display type.
     (It renders only if the widget passes an eyebrow; it does not today.) */
  position: relative;
  z-index: var(--sfbr-text-z, 30);

  margin: 0 0 clamp(10px, 1vw, 16px);
  font-family: "Archivo", system-ui, sans-serif;
  font-stretch: 62.5%;
  font-size: 11px;
  font-weight: 600;
  letter-spacing: .14em;
  text-transform: uppercase;
  color: var(--sfbr-accent);
}

/* The spoken heading. The split rebuilds the drawn lines node by node, so
   the sentence a screen reader gets is kept separate and unsplit. */
.sfbr__sr{
  position: absolute;
  width: 1px; height: 1px;
  margin: -1px; padding: 0; border: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
}

/*
	THE HEADLINE IS SECTION 1's TITLE, VALUE FOR VALUE — operator,
	2026-11-12. Everything above about Anton, cap heights and the squeeze
	is HISTORY and is kept because it is the only record of how the
	reference's type was derived; none of it is read any more.

	THESE SIX VALUES ARE COPIED FROM .sfop__title AS LITERALS, the same
	decision home-opening.css and category-grid.css already make between
	themselves and for the same reason: a custom property substitutes at
	computed-value time on the element where it is DECLARED, so a :root
	token declared in one stylesheet and read from another depends on load
	order and fails silently. All three files happen to load only on the
	front page, which is exactly what would let such a bug survive.

	    CHANGE ALL THREE OR NONE.
	    home-opening.css  -> .sfop__title
	    category-grid.css -> .sfcg__title

	READ THEM OFF THE SERVER, NOT OUT OF CLAUDE.md. This file recorded
	line-height 1 and mixed case; the live rule is 0.9em and uppercase,
	and the no-clip ceiling is 19vw - 20px where CLAUDE.md says 23vw -
	24px. The operator edits CSS on the box.
*/
.sfbr__fat{
  margin: 0;

  /* ───────────────────────────────────────────────────────────────
     ANTON, WHICH IS WHERE THIS BAND STARTED (operator, 2026-11-13:
     "i want the title font style height and so on exactly same like
     this image"). It was Anton when the band was built, went to Inter
     700 on 2026-11-12 to match sections 1 and 2, and comes back now
     because the ask is the REFERENCE's face rather than the page's.

     A SQUEEZED INTER IS NOT A CONDENSED FACE. Narrowing by transform
     thins the vertical stems while the horizontals keep their weight,
     so at .6 the letters read as a wide face pushed in rather than as
     a face drawn narrow. That is the whole of what was being asked
     about, and no amount of size fixes it.

     MEASURED, cap height against the width of "PARTS." — the ratio
     that matters here, because the size is settled against where the
     line ENDS:

       | face                      | "PARTS." | cap  | cap/width |
       | Mangogrotesque (theirs)   |  ~2.27em | .715 |   ~0.315  |
       | Anton 400                 |  2.505em | .860 |  **0.343**|
       | Inter 700 x .6 squeeze    |  2.153em | .730 |    0.339  |
       | Archivo 900 wdth 62.5     |  2.672em | .690 |    0.258  |
       | Chakra Petch 700          |  3.296em | .700 |    0.212  |
       | Inter 700, no squeeze     |  3.589em | .730 |    0.203  |

     So Anton gives the same cap height the squeeze was buying, with
     letterforms that are actually drawn that way — and it beats the
     reference's own ratio, which no free face does on width alone.

     IT NEEDS NO NEW ENQUEUE. superfly_bike_ribbon_assets() has always
     registered superfly-anton; the handle stayed through the Inter
     months. Note the stack falls back to Archivo, which IS loaded, so
     a missing enqueue renders wide and light rather than failing —
     the trap that cost a round when this band was built. Check the
     PAINTED width, never getComputedStyle().fontFamily.
     ─────────────────────────────────────────────────────────────── */
  font-family: 'Anton', 'Archivo Narrow', Archivo, sans-serif;

  /* **700, NOT THE 600 THE NOTE ABOVE DESCRIBES** (operator,
     2026-11-12: "now i want you make section 1 , 2 and section 4
     using weight 700"), after an audit found section 3 alone at 700
     and every other band at 600. The others came UP. `.sfbr__lede`
     moved with it, so the band stays one weight.

     The four files carrying these literals — home-opening.css,
     category-grid.css, this one and video-panel.css — are in step
     again. Change them together or not at all.

     ANTON HAS ONE WEIGHT AND IT IS 400. Asking for 700 against it is a
     synthesised fake bold — heavier, muddier and different in every
     browser. navbar.css records the same trap for Chakra Petch. */
  font-weight: 400;

  /* THIS BAND HAS LEFT THE SHARED LADDER (operator, 2026-11-12: "maybe
     you need to reduce a size font for big title"), and the note above
     is HISTORY for the size alone — the family, weight, leading,
     tracking and case are still section 1's and still change together.

     It is a MULTIPLIER on their expression rather than a rewritten
     clamp, so the two stay coupled: section 1 re-pitches its ramp and
     this follows at three quarters of it, and `--sfbr-fat-scale: 1`
     rejoins the set exactly. Measured at 1440x900: 124.2px -> 93.2px.

     The title went UNDER the cards in the same pass, which is why it
     could come down — it is a surface the ribbon crosses now, not the
     thing the band is read by. The lede does that job and did not
     move. */
  /* ───────────────────────────────────────────────────────────────
     THE SIZE IS FITTED TO THE MEASURE BY SCRIPT AS OF 2026-11-13, and
     the clamp below is only what is painted before it runs.

     Operator, against a screenshot of a CRAFTING / CULTURE hero: "i
     want only 2 words, like the image i give it to you". That
     arrangement is a word per line running edge to edge, which no
     ramp can produce - the size depends on how many characters the
     word has, and two different words want two different sizes.

     SO THIS BAND HAS LEFT THE SHARED LADDER ENTIRELY. It was already
     out for the SIZE alone (--sfbr-fat-scale, .75 of section 1's
     expression); the family, weight, leading, tracking and case are
     still section 1's and still change with it. Setting
     --sfbr-fat-scale back to 1 no longer rejoins the set on its own -
     the script would have to stop writing --sfbr-fat-size too.

     IT IS ALSO A RETURN TO THIS BAND'S OWN REFERENCE. detroit.paris
     sets its headline at 11.85vw of cap-corrected Anton, which is
     ~171px at 1440 - the wall of type the ribbon crosses. The 0.75
     multiplier had taken it to 93px, and two words per line is what
     made that necessary.

     bike-ribbon.js's fitHead() writes --sfbr-fat-size on the SECTION,
     so both lines take ONE size: the reference's two words are not
     equal in length and are plainly the same size, which is what makes
     them read as a block rather than as two fitted lines.

     THE FALLBACK MATTERS. With no script - or before it runs - the
     clamp below paints, so the band is never blank and never enormous.
     ─────────────────────────────────────────────────────────────── */
  --sfbr-fat-scale: .75;
  --sfbr-fat-fallback: calc(var(--sfbr-fat-scale) *
    clamp(30px, min(calc(5.5vw + 5svh), calc(19vw - 20px), 17svh), 200px));

  /* ───────────────────────────────────────────────────────────────
     THE REFERENCE'S OWN SIZE IS THE CEILING (operator, 2026-11-13:
     "why the title is too big? i want the title is like this the
     height of the title please follow that, then the title will not
     touch the image (refer image) its like ladder").

     FITTING THE WORD TO THE MEASURE WAS THE MISTAKE, and it was mine
     rather than theirs: "fill the width like the image" read the
     reference's PROPORTION off a screenshot where their two words
     happen to be long. They are not fitted at all - detroit.paris
     sets a flat vw and lets the word land where it lands. Measured
     on their live page at 1440x900:

         font-size   207px  =  14.375vw   (their --size-font x 14.375)
         line-height 165.6  =  .8em
         .fat.snd    margin-top -28.8px = -.1391em = -2vw
         "CRAFTING"  470px  =  32.65vw painted

     THE CAP IS WHAT TRANSFERS BETWEEN FACES, not the font-size - the
     whole reason this file carries a cap-correction table. Their
     Mangogrotesque puts caps at .715em, so their cap height is
     .715 x 14.375vw = 10.278vw. Inter's cap is .7275em, so:

         ours = 10.278 / .7275 = 14.127vw

     which is within 2% of their own number because the two faces
     happen to agree on cap height. (Anton, the stand-in this file's
     older notes derive, does NOT - its caps are 21% deeper, which is
     where the 11.85vw in those notes comes from.)

     WHAT DOES NOT TRANSFER IS THE WIDTH. Mangogrotesque is
     ultra-condensed: "CRAFTING" is 2.271em where our "PARTS." is
     3.26em. So at the same cap height our word covers about 46vw
     against their 32.65vw. That is the face, not the size, and the
     operator asked for the HEIGHT to follow - so the width is left
     where it falls rather than shrinking the type to match it.

     THIS IS ALSO WHAT KEEPS THE TITLE OFF THE CARDS. The staircase
     is short at the left and tall at the right, so a title that ends
     before the tall end never meets it - "its like ladder". At 1440
     the second line ends about 36px above the card under its right
     edge. A LONGER WORD EATS THAT CLEARANCE: the type does not come
     down any more, the line simply runs further right into taller
     cards. Re-measure that gap if either word changes.

     The fit and the height cap below are both KEPT, as ceilings - a
     word long enough to reach the gutter still cannot clip, and a
     short window still cannot push the lede off the stage. On a
     normal desktop neither binds and this is the size you get.
     ─────────────────────────────────────────────────────────────── */
/* THE COMMENTED VALUE BELOW IS INTER-DERIVED AND IS NOW WRONG FOR THIS
   FACE. The ceiling is the reference cap (10.278vw) divided by the cap
   ratio of whatever face is set: Inter .7275 -> 14.127vw, ANTON .86 ->
   **11.95vw**. Put that one back, not this one.

     --sfbr-fat-ref: 11.95vw;
 */
  --sfbr-fat-ref: 100em;
	
  font-size: min(
    var(--sfbr-fat-size, var(--sfbr-fat-fallback)),
    var(--sfbr-fat-ref));

  line-height: 0.9em;

  /* TRACKING MOVES WITH THE FACE, as it always does here. -.075em was
     pitched for Inter, which is drawn wide and wants the space taken
     out; Anton is already drawn narrow and closes its own counters at
     anything like that. The reference sets its display line with no
     tracking at all, so this is theirs. */
  letter-spacing: 0;
  text-transform: uppercase;
  color: var(--sfbr-head-ink, #fff);   /* pure white: see the blend note above */

  /* UNDER the cards, which is the reference's own value — their text
     block is z-index 1 and their pictures compute Math.round(scale*10),
     so the ribbon crosses the type. See the stacking note on .sfbr__head
     for why this cannot live on the parent. */
  position: relative;
  z-index: var(--sfbr-title-z, 1);

  /* Two lines stay two lines; the measure never does the breaking. The
     stage is `overflow: hidden`, so a line too long for the gutter is
     cropped rather than wrapped — see the narrow-width note below. */
  white-space: nowrap;

  /* ───────────────────────────────────────────────────────────────
     THE SQUEEZE IS WHAT BUYS THE HEIGHT (operator, 2026-11-13: "make
     it the text more height").

     THE SIZE HERE IS PAID FOR IN WIDTH, NOT IN HEIGHT — clearOfLadder()
     settles it against where the line ENDS, because that is what decides
     which card sits under it. So asking for taller letters by raising
     the size alone gives none of it back: the line reaches further
     right, meets a taller card and the solver takes the size straight
     off again.

     Narrowing the glyphs breaks that. At .8 the line is a fifth
     shorter, the solver can grow the type by about the same, and the
     caps come out taller while the line ends in the same place. It is
     the one dial that is not a trade.

     IT IS ALSO WHAT THE REFERENCE GETS FOR FREE. Mangogrotesque is
     ultra-condensed — 2.271em for "CRAFTING" against our 3.26em for
     "PARTS." — which is exactly why their hero can be that tall and
     still end at 32vw.

     A MECHANICAL SQUEEZE THINS THE VERTICAL STEMS while the horizontals
     keep their weight, so it is not free past about .55 on a heavy
     face: the letters start to read as drawn wrong rather than as
     condensed. video-panel.css argues the same number from the other
     side. .8 is mild and Inter carries it.

     NO WIDTH CORRECTION IS NEEDED HERE, unlike .sfvp's version: that
     one fits a line to the measure and so has to hand the box back the
     width the scale takes away. This line is sized by the solver, which
     measures the PAINTED rects — the transform included — so it sees
     the narrower line and grows the type on its own.

     Set it to 1 and the band is back to where it was, with no other
     edit: the solver simply settles smaller.
     ─────────────────────────────────────────────────────────────── */
  /* OFF, because the face is genuinely condensed now. Everything the
     squeeze did, Anton does by being drawn that way — see the ratio
     table at the top of this rule. Left wired rather than deleted: it
     is one number if a future face ever needs narrowing again, and
     sheen() still divides by it. */
  --sfbr-fat-squeeze: 1;
  transform: scaleX(var(--sfbr-fat-squeeze, 1));
  transform-origin: left center;
}

/* THE SECOND LINE IS THE ACCENT, AND IT IS SECTION 3's ACCENT EXACTLY
   (operator, 2026-11-12, against a screenshot of that band): Chakra Petch
   700 ITALIC in accent-1 — the pair `.sfvp__sayTitle em` carries, promoted
   from 9-11px labels to display size there and here.

   IT IS A REAL ITALIC ONLY BECAUSE THE HANDLE ASKS FOR ONE. Every other
   Chakra Petch URL in functions.php requests `wght@...` with NO ital axis,
   so `font-style: italic` against those obliques the upright — a fake that
   looks nearly right and differs in every browser. `superfly-chakra-italic`
   asks for `ital,wght@1,700`, the one cut these rules use. video-panel.css
   records the same trap from its own side.

   THE SCREENSHOT PUT THE ACCENT ON THE UPPER LINE and this is on the
   lower one, because "OUR PARTS." is what the band is selling and the
   reference's accent sits on the phrase that carries the meaning. Moving
   it is the `--snd` modifier in the widget markup, not a change here.

   The tracking opens from -.075em to -.03em: that value was pitched for
   Inter, and Chakra Petch is a squarer face whose counters close up under
   it. The SIZE is deliberately untouched, so the two lines keep one
   ladder and one leading. */
/* UPRIGHT INTER SINCE 2026-11-13 (operator:
     "the text that color pink, you no need to make it that text is
     italic, i want normal and please make it the text using font inter
     like the text white .. but that pink color text make it have effect
     like PERFORMANCE effect in section 2").

     SO THE WHOLE RULE IS NOW SUBTRACTION PLUS A GRADIENT. The family,
     the style and the tracking overrides are gone, which means this
     line computes identically to .sfbr__fat above it - one face, one
     ladder, one leading, one tracking - and the only thing telling the
     two apart is the magenta passing through this one. The italic
     Chakra Petch it replaces is in git; superfly-chakra-italic is still
     enqueued and is now read by nothing on this band.

     THE GRADIENT CANNOT GO ON THIS ELEMENT, and that is the whole
     reason the rule below exists. bike-ribbon.js splits the line into
     one <span class="sfbr__char"><span>X</span></span> per glyph and
     the inner span is TRANSFORMED - so it paints in its own layer, and
     Blink's text clip on an ancestor does not reach glyphs inside it.

     THE FAILURE MODE IS AN INVISIBLE LINE, NOT A WRONG ONE, which is
     why this is worth a paragraph: the rule is present, correct and
     computes exactly what you wrote, the element reports a sensible
     box, nothing errors, and the headline simply has one line missing.
     Measured in the harness: color: transparent + background-clip:
     text on this element painted nothing at all, and the same markup
     with transform: none forced onto the inner spans painted the
     gradient perfectly. So the test is the PAINTED PIXELS - a
     screenshot - never the computed value. */

/* ONE CHARACTER, ONE MASK, built at runtime by bike-ribbon.js the way
   their split helper does:
       yPercentStart 150 -> yPercentEnd 10, 1.2s, expo.out, stagger .05

   THE PADDING/MARGIN PAIR STOPS THE LETTERS BEING SHAVED AT THE BASELINE,
   and the amount is not a guess — the resting offset IS the overhang:

       mask height  = line-height         = .9115em
       resting drop = 10% of that         = .0912em

   so every glyph hangs that far below a mask exactly its own height, and
   `overflow: hidden` cuts it off. .13em leaves headroom at every size, and
   the equal negative margin takes the padding back out of the layout so
   neither the line box nor the gap between the two lines moves.
   CHANGE THE LEADING OR THE 10% AND REDO THE SUM. */
.sfbr__char{
  display: inline-block;
  overflow: hidden;
  vertical-align: top;
  padding-bottom: .13em;
  margin-bottom: -.13em;
}

/* ONCE THE ENTRANCE HAS LANDED THE CLIP COMES OFF — bike-ribbon.js adds
   is-settled when the last character's transition is done.

   The clip is only ever needed while the glyphs are sliding up through it.
   Left on, the line stays ~29 clipped, transformed inline-blocks for as
   long as the tab is open, and on a display at a fractional
   devicePixelRatio that clip edge falls between device pixels — which is
   the one construct here that can paint a faint seam across the line.

   NOTHING MOVES: every glyph clears its own clip by 11-18px (measured per
   letter, see CLAUDE.md), so there is nothing hidden for this to reveal,
   and the resting transform stays exactly as it was. */
.sfbr.is-settled .sfbr__char{ overflow: visible; }

/* A ONE-FRAME MEASURING STATE, added and removed inside
   clearOfLadder(). The entrance translates each glyph inside its mask,
   and a Range over the line includes that transform - so the painted
   block measures far taller than it is until the letters have landed.
   With the transform off for one read the geometry is the same at load
   as it is afterwards. */
.sfbr.is-sfbr-measuring .sfbr__char > span{
  /* BOTH, AND THE TRANSITION IS THE ONE THAT MATTERS. These spans carry a
     1.2s transition on transform, so changing the specified value only
     starts a tween - the COMPUTED value, which is what a Range measures,
     stays where it was until the tween runs. The class then looks like it
     does nothing, and in a tab that is not being given animation frames it
     never does. */
  /* THE RESTING OFFSET, NOT none. The letters finish at translateY(10%),
     so measuring them at 0 reports the block .09em shorter than it paints
     and the title lands that much too low - measured -9px of clearance
     against a model that said +19. Measure where the type ends up. */
  transform: translateY(10%) !important;
  transition: none !important;
}

.sfbr__char > span{
  display: inline-block;
  transform: translateY(150%);
  transition: transform 1.2s cubic-bezier(.16, 1, .3, 1);
  transition-delay: calc(var(--i, 0) * .05s);
}

/* Note the resting offset is 10%, NOT 0 — theirs rests the letters low in
   the mask on purpose. */
.sfbr.is-in .sfbr__char > span{ transform: translateY(10%); }

/* ─────────────────────────────────────────────────────────────────────
   SECTION 2's SHEEN ON THE ACCENT LINE, PAINTED PER CHARACTER AND
   ALIGNED BACK INTO ONE GRADIENT BY SCRIPT.

   The stops, the 2.2x size, the 5s ease loop and the two positions are
   .sfcg__word’s in category-grid.css, which is where this effect is
   argued. THIS IS THE FOURTH FILE CARRYING THOSE LITERALS rather than
   one shared token - home-opening.css and video-panel.css are the
   others - because a custom property substitutes at computed-value time
   on the element where it is DECLARED, so a :root token declared in one
   stylesheet and read from another resolves by load order and fails
   silently. CHANGE THEM TOGETHER OR NOT AT ALL.

   WHY IT IS NOT ONE GRADIENT ON ONE ELEMENT: see the note on
   .sfbr__fat--snd above. The glyphs are inside transformed spans, and a
   text clip does not reach them.

   WHY IT IS NOT SIMPLY A GRADIENT PER LETTER: every letter would then
   sweep its own box at the same instant, which pulses the line rather
   than passing a light along it. So each span is given the gradient at
   the width of the WHOLE LINE and then shifted back by its own distance
   from the line's first glyph - the fragments re-form one continuous
   sweep. bike-ribbon.js writes the two numbers in measure():

       --sfbr-fat-w   the painted width of the line, on the line
       --sfbr-cx      that glyph's offset from the first, on each span

   THE KEYFRAME MATHS IS SECTION 2's, RESOLVED. A background-position
   percentage is a percentage of (positioning area - image), so at a
   2.2x image 10% is -0.12 of the area and 91% is -1.092 of it.
   Those are the two numbers below, times the LINE's width, minus the
   glyph's own offset. Change the 220% and you must redo them.

   IF THE SCRIPT NEVER RUNS the fallbacks leave every glyph at the head
   of its gradient, which is the ink: the line reads as plain white type
   rather than disappearing. That is the right way round.

   The static background-position is the 0% keyframe, so the reduced
   motion rule at the foot of this file - which only stops the
   animation - leaves the line in ink rather than wherever 0 0 lands.
   ───────────────────────────────────────────────────────────────────── */
/* THE SECOND LINE IS PULLED UP, THE WAY THEIRS IS — .fat.snd carries
   margin-top: -2rem on a site where 1rem = 1vw, which is -.1391em of
   its own font-size. Written in em rather than vw so it scales with
   whatever size the three ceilings above settle on; at -2vw it would
   swallow the gap entirely on a narrow window.

   IT DOES NOT TOUCH line-height, which is the point: .9em is one of
   the five values this band shares with sections 1 and 2, and a
   negative margin on one line is how the reference tightens its own
   pair without changing the leading either. Measured after: the gap
   between the two caps is about .03em, theirs about .036em. */
/* NO PULL-UP WITH ANTON. The reference's -.1391em was closing a channel
   that its own face leaves open: Mangogrotesque's caps are .715em inside
   a .8em line, so without it the two lines sit far apart. Anton's caps are
   .86em inside our .9em line, which is a .04em channel on its own — put
   the pull-up back on top of that and the two rows of caps touch.

   The value is kept here, commented, because it is the reference's own and
   it is needed again the moment the face goes back to anything shallower:

       .sfbr__fat--snd{ margin-top: -.1391em; } */

.sfbr__fat--snd .sfbr__char > span{
  color: transparent;
  background-image: linear-gradient(90deg,
    var(--sfbr-head-ink, #fff)  0%,
    var(--sfbr-accent)         48%,
    var(--sfbr-head-ink, #fff) 100%);
  background-repeat: no-repeat;
  background-size: calc(var(--sfbr-fat-w, 100vw) * 2.2) 220%;
  background-position:
    calc(-0.12 * var(--sfbr-fat-w, 100vw) - var(--sfbr-cx, 0px)) 0;
  -webkit-background-clip: text;
  background-clip: text;
  animation: sfbrSheen 5s ease infinite;
}

@keyframes sfbrSheen{
  0%   { background-position:
           calc(-0.12  * var(--sfbr-fat-w, 100vw) - var(--sfbr-cx, 0px)) 0 }
  50%  { background-position:
           calc(-1.092 * var(--sfbr-fat-w, 100vw) - var(--sfbr-cx, 0px)) 100% }
  100% { background-position:
           calc(-0.12  * var(--sfbr-fat-w, 100vw) - var(--sfbr-cx, 0px)) 0 }
}

/* Their lede: same face, 0.1391em of the headline, broken with a <br>, and
   a third line at 0.75em of it. All three cap-corrected the same way —
   a literal .85 line-height on a face with 21% deeper caps closes the gap
   between the two lines to nothing and they touch. */
.sfbr__lede{
  /* OVER the cards — the half of this block that still has to be read at
     any scroll position, which is what the operator kept when the big
     title went under. The cards compute Math.round(scale * 10) and top
     out at 21, so 30 clears every one of them. It is on this element and
     not on .sfbr__head for the stacking-context reason recorded there. */
  position: relative;
  z-index: var(--sfbr-text-z, 30);

  margin: 2.75vw 0 0;
  font-family: 'Inter', system-ui, -apple-system, sans-serif;
  font-weight: 700;
  font-size: 1.65vw;
  line-height: 1.0307;           /* theirs: .85 x 2.0008vw = 1.7007vw */
  text-transform: uppercase;
  white-space: nowrap;
  color: var(--sfbr-head-ink, #fff);
  opacity: 0;
  /* `translate`, never `transform`. It was the squeeze that owned
     `transform` here; that is gone, but keep them apart anyway — the
     moment anything else wants a transform on this element, folding the
     two together has the entrance wipe it out. */
  translate: 0 12px;
  transition: opacity .9s ease .55s,
              translate .9s cubic-bezier(.16, 1, .3, 1) .55s;
}

.sfbr__lede--snd{
  font-size: 1.24vw;             /* theirs is a bare <sub>, 0.75em */
  margin-top: 1.12vw;
  transition-delay: .65s;
  /* theirs is simply the same ink, smaller — a magenta brand list was
     louder than the reference's third line */
  color: var(--sfbr-ink);
}

.sfbr.is-in .sfbr__lede{ opacity: 1; translate: 0 0; }

/* --------------------------------------------------------------------------
   3 · The ribbon
   -------------------------------------------------------------------------- */

/* THE CARD LAYER IS THE WHOLE STAGE, not the remainder under the heading,
   and that is theirs: their `.artist_list_w` is `position: absolute; inset:
   0` with the text block sitting over it. It matters because the cards are
   anchored to the BOTTOM — give them only the space below the heading and a
   full-size card runs off the foot of the window. Measured at 1354x760: the
   1.6 card is 44vw = 595px, which fits a 760px stage and does not fit the
   570px left under a heading. */
.sfbr__viewport{
  position: absolute;
  inset: 0;
}

.sfbr__track{
  position: relative;
  height: 100%;
  list-style: none;
  margin: 0;
  padding: 0;
  user-select: none;
  -webkit-user-select: none;
  /* so the empty space between cards does not swallow a drag of the page */
  pointer-events: none;
}

/* THE CARD. Every one is the same element at the same size on the SAME
   bottom-left corner, and only `scale` differs. Growing from a shared
   corner is the whole staircase — there is no masonry and no per-card
   height anywhere in this file. */
.sfbr__item{
  position: absolute;
  left: 0;
  bottom: 0;
  width: var(--sfbr-card-w);
  height: var(--sfbr-card-h);
  transform-origin: left bottom;
  will-change: transform, scale, opacity;
  scale: 0;
  opacity: 0;
  --parallax-x: 0%;
  pointer-events: auto;
}

.sfbr__link{
  position: absolute;
  inset: 0;
  display: block;
  overflow: hidden;              /* the frame the picture parallaxes inside */
  border-radius: 12px;           /* the house radius — navbar, hero, section 2 */
  background: #0d0d10;
  text-decoration: none;
  color: inherit;
}

/* THE PICTURE IS 110% OF ITS FRAME. That 10% of slack is the only thing
   --parallax-x has to move into; shrink it and the frame runs out of
   picture at the small end, where the parallax reaches -15%. */
.sfbr__img{
  position: absolute;
  inset: 0;
  width: 110%;
  height: 100%;
  object-fit: cover;

  /* THE PICTURES ARE LIFTED, NOT DARKENED, AND THAT IS WHAT "SAME AS
     SECTION 2" TURNED OUT TO MEAN (operator, 2026-11-12).

     `.sfcg` paints rgba(0,0,0,.34) over its photographs and this band was
     given the identical value first — correctly, and it looked nothing
     like it, because the same overlay lands somewhere else on a different
     picture. Measured in-page, mean luma of the loaded files:

         section 2's four      43..54 at source  ->  29..36 overlaid
         the six badges        18..25 at source  ->  12..17 overlaid

     These are near-black castings lit with a rim; section 2's are studio
     shots on white. Copying the VALUE across doubles the gap instead of
     closing it. Matching the RESULT means going the other way.

     `brightness()` is multiplicative, so pure black maps to pure black —
     the backgrounds stay as black as they were and only the castings, the
     chrome and the rim light come up. A contrast or a lightness lift would
     grey them. Swept in-page over the six real files, mean / range:

         1.00  21.3   18.5..25.5      1.55  32.3   28.2..37.8   <- ours
         1.25  26.3   22.8..31.3      1.70  35.2   31.0..40.8
         1.40  29.3   25.5..34.7      section 2:  33.2  28.6..35.8

     1.55 lands on section 2 to within a point of the mean and inside its
     range at both ends. 1.4% of pixels clip at that lift and they are the
     specular highlights on the chrome, which were already blown.

     THE TWO FILES ARE NOW MATCHED BY RESULT, NOT BY DECLARATION — so if
     either band's photography is ever replaced, re-measure rather than
     copying a number across. That is the whole lesson of this round. */
  filter: brightness(var(--sfbr-lift, 1));

  transform: translate(var(--parallax-x));
  transition: transform .6s cubic-bezier(.33, 1, .68, 1);
  -webkit-user-drag: none;
  pointer-events: none;
}

.sfbr__item:hover .sfbr__img{
  transform: translate(var(--parallax-x)) scale(1.03);
}

/* THE SAME FLAT DARKENING OVERLAY THE CATEGORY GRID CARRIES (operator,
   2026-11-12: "i want you make the image brand same overlay with image
   category"). `.sfcg` declares `--sfcg-overlay: .34` and paints
   rgba(0,0,0,.34) over its pictures; this is that value, on a band two
   screens further down the same page, so the two read as one treatment.

   TWO LITERALS RATHER THAN ONE SHARED TOKEN, the decision this file already
   records for the 12px radius: a custom property substitutes at
   computed-value time on the element where it is DECLARED, so a :root token
   declared in category-grid.css and read from here would resolve by load
   order and fail silently — and both files only load on the front page,
   which is exactly what would hide such a bug. CHANGE BOTH OR NEITHER.

   Two things about where it is painted:

   - ON THE LINK, NOT ON THE PICTURE. The img is 110% of its frame and
     slides on --parallax-x, so an overlay riding with it would travel too
     and leave a lit strip down one edge of every card. The link is the
     frame; `inset: 0` on it is the card, whatever the picture is doing.
   - `:not([data-placeholder])` because the PLACEHOLDER tag is ::after on
     this same selector. A placeholder has no photograph to knock back, so
     it needs no overlay and the two can never collide. */
.sfbr__link:not([data-placeholder])::after{
  content: "";
  position: absolute;
  inset: 0;
  border-radius: inherit;
  background: rgba(0, 0, 0, var(--sfbr-overlay));
  pointer-events: none;
}

/* A brand with no photograph yet. Same convention as .sfbw and the review
   cards: carbon, a magenta bloom, and a tag that says so.
   WHILE THAT TAG IS VISIBLE THIS BAND IS NOT FINISHED. */
/* THE BLOOM WAS HALVED WHEN EVERY CARD BECAME A PLACEHOLDER (2026-11-12).
   It was .42 / .12, pitched for the odd unfinished card among real
   photographs. Twelve of them at that strength is a wall of hot pink that
   reads as a design decision rather than as missing art — which is the
   opposite of what a placeholder is for. At .20 / .06 the staircase, the
   depth and the overlap all still read, and the PLACEHOLDER tag says the
   rest. Put the old values back the day only one or two cards are waiting. */
.sfbr__link[data-placeholder]{
  background-image:
    radial-gradient(120% 110% at 78% 8%,
      rgba(236,30,121,.20) 0%, rgba(236,30,121,.06) 46%, rgba(236,30,121,0) 74%),
    repeating-linear-gradient( 45deg, rgba(255,255,255,.025) 0 2px, transparent 2px 4px),
    repeating-linear-gradient(-45deg, rgba(0,0,0,.35)        0 2px, transparent 2px 4px);
}

/* The tag COUNTER-SCALES off --sfbr-inv, which bike-ribbon.js writes as
   1/cardScale every frame — the same trick the caption uses, except a
   pseudo-element cannot take an inline `scale`, so it reads a property
   instead. Flat values here would be half a pixel on the smallest card and
   nineteen on the biggest, and since 2026-11-12 EVERY card is a placeholder,
   so that is six of them on screen rather than the odd one.

   The offsets are multiplied too, so the inset reads 10px whatever the card
   is doing. */
.sfbr__link[data-placeholder]::after{
  content: "PLACEHOLDER";
  position: absolute;
  right: calc(10px * var(--sfbr-inv, 1));
  bottom: calc(10px * var(--sfbr-inv, 1));
  font-family: "Archivo", system-ui, sans-serif;
  font-stretch: 62.5%;
  font-size: calc(9px * var(--sfbr-inv, 1));
  font-weight: 600;
  letter-spacing: .14em;
  color: var(--sfbr-accent);
}

/* --------------------------------------------------------------------------
   4 · The caption — ABOVE the card, not on it
   Theirs is a sibling of the link, not a child, hanging outside a card that
   is `overflow: visible`. Measured on a card at scale 0.98199: the gap from
   the caption's bottom to the card's top is 0.2495rem.

   `bottom: calc(100% + .25vw)` rather than their literal negative `top`:
   for an absolutely positioned box `bottom: 100%` puts its bottom edge on
   the containing block's top edge, so it follows the card with no number to
   keep in step. A percentage in `top` would NOT — that resolves against the
   containing block's height, not the element's own.

   bike-ribbon.js writes `scale: 1/cardScale` here every frame so the label
   stays the same size on screen whatever the card is doing. `translate` and
   `scale` are separate properties on purpose: the script owns one, the
   stylesheet the other, and they compose without either knowing.
   -------------------------------------------------------------------------- */

.sfbr__tag{
  position: absolute;
  left: 0;
  bottom: calc(100% + .25vw);
  z-index: 2;
  display: flex;
  align-items: center;
  gap: .5vw;
  font-family: "Archivo", system-ui, sans-serif;
  font-stretch: 62.5%;
  font-size: .78vw;
  font-weight: 600;
  letter-spacing: .14em;
  text-transform: uppercase;
  white-space: nowrap;
  color: var(--sfbr-ink);
  transform-origin: bottom left;
  will-change: scale, translate, opacity;
  transition: translate .4s cubic-bezier(.33, 1, .68, 1),
              opacity   .4s cubic-bezier(.33, 1, .68, 1);
  pointer-events: none;

  /* EVERY BRAND IS NAMED, NOT ONLY THE ONE AT THE BIG END (2026-11-13,
     operator: "i think this section not perfet enough").

     IT WAS `translate: 0 100%; opacity: 0` HERE, shown only on hover and
     on `.is-lead` — which is theirs, and theirs is a list of visibly
     different pictures where an unlabelled card still tells you what it
     is. These six are the same photograph in kind: a near-black casting,
     a magenta rim, a badge. At ribbon scale they are not told apart, so
     five unlabelled cards were five dark rectangles and a band that asks
     you to pick your bike named exactly one of them.

     .42 rather than 1 because the lead has to stay plainly the loudest —
     it is the card the ribbon is handing you. The captions already
     counter-scale off --sfbr-inv (bike-ribbon.js writes 1/cardScale every
     frame), so the smallest card's label is the same 9px on screen as the
     biggest one's: the small end was always readable, it was only hidden.

     The translate is gone rather than set to 0 so nothing is left
     animating a property that no longer changes. Put both lines back to
     restore the reference's behaviour exactly. */
  translate: 0 0;
  opacity: var(--sfbr-tag-rest, .42);
}

/* Full strength on the card that is currently biggest, and on hover.
   bike-ribbon.js sets .is-lead. */
.sfbr__item:hover .sfbr__tag,
.sfbr__item.is-lead .sfbr__tag{ opacity: 1; }

.sfbr__dot{
  width: .78vw;
  height: .78vw;
  flex: 0 0 auto;
  border-radius: 50%;
  background: var(--sfbr-accent);
}

/* --------------------------------------------------------------------------
   THE FIGURE SAYS WHAT IT COUNTS (2026-11-13)

   It was a bare `.sfbr__count{ opacity: .6 }`, so the caption read
   "HONDA 27" and 27 was not a quantity of anything. Section 2's badges
   already settled the house wording — "10 parts · from RM 80" — so this is
   that convention two bands further down the same page: the separator and
   the unit in ink, the figure in the accent.

   BOTH HALVES ARE PSEUDO-ELEMENTS, so nothing in the shortcode changed and
   this cost no functions.php edit, no widget write and no cache flush. A
   pseudo-element takes its own `color`, which is the whole reason the
   two-tone works without a span.

   THE ONE THING THAT WOULD FORCE A SHORTCODE CHANGE IS A BRAND WITH
   EXACTLY ONE PRODUCT — CSS cannot pluralise, so it would read "1 parts".
   Counted 2026-11-13: Honda 27, Yamaha 83, Suzuki 6, SYM 3, and Zontes and
   Modenas print no count at all (see the rule below). Nothing is at 1 yet.
   When one is, print the word from superfly_bike_ribbon_shortcode() and
   delete the ::after.
   -------------------------------------------------------------------------- */
.sfbr__count{
  opacity: 1;
  color: var(--sfbr-accent);
}
.sfbr__count::before{
  content: "· ";
  color: var(--sfbr-ink);
  opacity: .35;
}
.sfbr__count::after{
  content: " parts";
  color: var(--sfbr-ink);
  opacity: .6;
}


/* --------------------------------------------------------------------------
   A BRAND WITH NO PRODUCTS IS MARKED, AND IS NOT A LINK (2026-11-13)

   Zontes and Modenas hold ZERO published products. Both are real brand
   archives, so both return 200 — and both are empty, which means a customer
   picking one of the six cards had a one-in-three chance of landing on
   nothing. That is worse than the brand not being on the wall at all.

   Taking them off is the other answer and is one `exclude` attribute away in
   the shortcode. This is the softer one and it is honest: the card still
   says the brand is coming, and it cannot be clicked into an empty shop.

   THE TEST IS THE ABSENCE OF A COUNT, NOT A LIST OF BRAND NAMES.
   superfly_bike_ribbon_shortcode() only prints .sfbr__count when the term
   has products, so `:not(:has(.sfbr__count))` IS that condition — it stops
   firing on its own the day stock is assigned to either brand, with nothing
   to deploy, and it would catch a seventh empty brand added in wp-admin.

   `:has()` is why this is possible at all: there is no other way for a
   rule on the item to depend on a descendant that is missing. Supported
   everywhere this site is used; a browser without it simply gets today's
   behaviour, which is the right way round for a fallback.
   -------------------------------------------------------------------------- */
.sfbr__item:not(:has(.sfbr__count)) .sfbr__link{
  pointer-events: none;
  cursor: default;
}

/* Knocked further back than its neighbours, rim light and all, so it reads
   as not-yet rather than as one of the six you can have. */
.sfbr__item:not(:has(.sfbr__count)){
  --sfbr-lift: 1.15;
  --sfbr-overlay: .72;
}

/* The dot goes hollow — the one glyph already on the caption, so this costs
   no extra element and no extra width. */
.sfbr__item:not(:has(.sfbr__count)) .sfbr__dot{
  background: transparent;
  box-shadow: inset 0 0 0 1.5px var(--sfbr-accent);
}

/* ...and the caption says it in words. On the tag, not on the card: the
   card's own ::after is the PLACEHOLDER tag, which is a different state
   (no photograph) and must still be able to appear on top of this one. */
.sfbr__item:not(:has(.sfbr__count)) .sfbr__tag::after{
  content: "Coming soon";
  opacity: .55;
  letter-spacing: .14em;
}

/* --------------------------------------------------------------------------
   5 · The phone gets a plain scroller
   The whole thing is a scrub against a sticky stage, and a 30vw card on a
   375px screen is 112px. Below 768px the section stops being tall, the
   script stands down, and the six cards become an ordinary swipeable row —
   the same shape .sfbw falls back to, and the same shape theirs does.
   -------------------------------------------------------------------------- */

@media (max-width: 767px){
  .sfbr{
    height: auto;
    padding-bottom: clamp(32px, 8vw, 64px);
  }

  .sfbr__stage{
    position: static;
    height: auto;
    overflow: visible;
  }

  .sfbr__head{
    padding-top: clamp(48px, 12vw, 88px);
  }

  /* Scaled by the same cap correction as the desktop sizes (x .8243), so
     the phone keeps the painted width it had and loses only the extra
     height Anton's caps were adding. These are ours — the phone layout is
     a fallback the reference does not have. */
  /* no font-size here: section 1's clamp is one expression at every
     width, so the phone takes it too. */
  .sfbr__lede     { font-size: 3.63vw; }
  .sfbr__lede--snd{ font-size: 2.73vw; margin-top: 2.46vw; }

  .sfbr__viewport{
    position: static;            /* it is an absolute full-stage layer above */
    inset: auto;
    margin-top: clamp(28px, 7vw, 48px);
    overflow-x: auto;
    overflow-y: hidden;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
  }

  .sfbr__viewport::-webkit-scrollbar{ display: none; }

  .sfbr__track{
    display: flex;
    align-items: flex-end;
    height: auto;
    /* room INSIDE the scroller for the captions, which sit above each
       card — the scroller is overflow-y:hidden and would cut them off */
    padding: 7vw var(--sfbr-gutter) 0;
    gap: 3vw;
    pointer-events: auto;
    width: max-content;
  }

  /* THE REPEATS ARE DESKTOP ONLY. The brands are doubled so the ribbon is
     longer than the screen and the cards can reach full size — on a phone
     the scrub is off and it is a plain swipeable row, where a second
     Honda after the first is simply a duplicate in the list. */
  .sfbr__item[data-sfbr-dup]{ display: none; }

  /* AND THE SURVIVORS GO BACK INTO READING ORDER. The markup is reversed
     and rotated so the brands ARRIVE in the operator's order as the
     ribbon travels; laid out as a plain row that reads backwards and
     rotated, so each card carries its reading position and flex `order`
     puts it back. Honda, Yamaha, Suzuki, XMAX, ADV, SYM. */
  .sfbr__item{ order: var(--sfbr-pos, 0); }

  .sfbr__item{
    position: relative !important;
    left: auto !important;
    bottom: auto !important;
    transform: none !important;
    scale: 1 !important;
    opacity: 1 !important;
    flex: 0 0 auto;
    width: 62vw;
    height: auto;
    aspect-ratio: 1 / 1;          /* square, as on desktop */
  }

  .sfbr__img{ width: 100%; transform: none !important; }

  /* no hover on a phone, so every caption is simply on */
  .sfbr__tag{
    translate: 0 0 !important;
    opacity: 1 !important;
    scale: 1 !important;
    bottom: calc(100% + 1.4vw);
    font-size: 2.8vw;
    gap: 1.6vw;
  }

  .sfbr__dot{ width: 2.4vw; height: 2.4vw; }
}

/* Reduced motion: the scrub is a position, not an animation, so it stays —
   only the easing and the hover drift are dropped. */
@media (prefers-reduced-motion: reduce){
  .sfbr__fat--snd .sfbr__char > span,
  .sfbr__img,
  .sfbr__tag,
  .sfbr__accent{
    transition-duration: .01ms !important;
    animation: none !important;
  }
}
