/* =============================================================
 * SUPERFLY — HOME — THE SINGAPORE DISTRIBUTOR BAND — looks
 * -------------------------------------------------------------
 * Built 2026-11-12 to the illustration card on dozfx.com (their
 * "Orchestrated, not relayed." band): a short statement on the
 * left, and on the right a panel holding two dotted routes — one
 * muted, one live — with a detail row under them and two small
 * labels printed OUTSIDE the panel, bottom left and bottom right.
 *
 * Markup:   assets/html/singapore.html (a readable copy)
 * Movement: assets/js/singapore.js
 *
 * NAMESPACE. Everything is scoped under .sfsg. The prefixes already
 * taken in this folder are sf-acc, sf-bike(s), sf-cart, sf-cat(s),
 * sf-checkout, sf-dealers, sf-drawer, sf-filters, sf-hero, sf-intro,
 * sf-lights, sf-live, sf-livery, sf-login, sf-maskword, sf-mega,
 * sf-navbar, sf-net, sf-pdp, sf-pf, sf-sequence, sf-shop, sf-social,
 * sf-sort, sf-step, plus .sfbr, .sfbw, .sfc, .sfcg, .sfcl, .sfdw,
 * .sfidx, .sfop, .sfrev, .sfsr, .sfv and .sfvp — grep assets/css
 * before adding another. Note .sfsr is the fixed SOCIAL RAIL; .sfsg
 * is not it, and the two sit next to each other alphabetically in
 * every listing, so read the whole prefix.
 *
 * BOX SIZING stated on the root itself, so this band measures the
 * same inside Elementor and in the local harness. CLAUDE.md has the
 * full story of the 80px that goes missing otherwise.
 *
 * NO GSAP, NO LIBRARY. The entrance is one IntersectionObserver and
 * CSS transitions, as .sfdw, .sfcg and .sfbw all are — so the band
 * creates no ScrollTrigger pin, has nothing to fight Lenis, and
 * loads nothing but its own two files. The page still has zero
 * .pin-spacer and this must not be what changes that.
 *
 * WHERE IT DEPARTS FROM THE REFERENCE, AND WHY:
 *
 *   · THE PANEL'S SHELL IS THE HOUSE CARD, NOT THEIR HAIRLINE.
 *     dozfx draws a 1px border; every card on this home page is the
 *     footer wordmark's emboss — no border at all, the light IS the
 *     edge. A bordered panel two bands under .sfdw's borderless ones
 *     reads as a mistake, so the shell is embossed and the hairline
 *     is gone. **The two shadow values are .sfdw__card's exactly**
 *     and are duplicated here as literals for the same reason
 *     .sfop__title's type is: a custom property substitutes 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 both files or neither.
 *
 *   · THE DOTTED RULES STAY. They are the reference's whole visual
 *     signature and .sfdw deliberately dropped them when its cells
 *     became boxes (a rule plus a box is one device too many). Here
 *     they are INSIDE one box, dividing it, which is the job they
 *     were drawn for — and the dotted track is the illustration
 *     itself, not decoration.
 *
 *   · NO FIGURE ROW. Theirs closes with "4 → 1". The equivalent
 *     number here would be "157 → 1", which reads as fewer shops
 *     rather than as one clear contact, so the close is the
 *     distributor's own details instead — the card from the dealer
 *     page, same arrangement, same type.
 * ============================================================= */

.sfsg,
.sfsg *{ box-sizing: border-box }

.sfsg{
	--sfsg-accent: var(--wp--preset--color--accent-1, #ec1e79);
	--sfsg-page:   var(--wp--preset--color--base, #171717);
	--sfsg-ink:    var(--wp--preset--color--contrast, #f2f2f4);
	--sfsg-dim:    rgba(242,242,244,.64);
	--sfsg-faint:  rgba(242,242,244,.46);
	--sfsg-rule:   rgba(242,242,244,.18);

	/* .sfdw__card's, value for value — see the note above. */
	--sfsg-card: var(--sfsg-page);
	--sfsg-lift: rgba(255,255,255,.10);
	--sfsg-sink: rgba(0,0,0,.70);

	/* 12px, THE HOUSE RADIUS — the navbar bar, the hero panel, the
	   video panel, section 2's cards and section 5's all carry it.
	   This token exists to be read, never re-pitched on its own. */
	--sfsg-radius: 12px;

	/* Inter for the statement and the name, Chakra Petch for the
	   small tracked-out labels. The arrangement every band on this
	   page has settled on; a third family here would read as a seam. */
	--sfsg-display: "Inter", system-ui, -apple-system, sans-serif;
	--sfsg-tech:    "Chakra Petch", ui-monospace, monospace;

	/* SECTION 2's AND SECTION 5's GUTTER, 80px at the top end. It is
	   deliberately NOT the navbar logo's 44 — the bands around this
	   one sit at 80 and an 80/44 run reads as a mistake. Do not
	   "align" it without asking. */
	--sfsg-gutter: clamp(20px, 4.2vw, 80px);

	/*
		THE FIXED SOCIAL RAIL — the seventh band in this project to
		need clearing it. .sfsr is 46px wide (40 below 782px) on the
		left edge of every page at z-index 90, vertically centred, so
		everything in the left column passes behind it as you scroll.
		58 is the house clearance: .sfidx uses it for its row numbers,
		.sfcg for its heading, .sfbw for its brand words, .sfdw for
		its head.

		A max() against the gutter rather than a media query, so it is
		0 on a desktop and disappears on its own if the gutter ever
		passes 58.

		IT IS ON THE LEFT COLUMN ONLY, never on padding-inline — that
		sets BOTH sides, and a phone would pay 38px of clearance on
		the right where there is no rail. .sfdw records what that cost
		when its cells became boxes.

		CHECK IT BY MEASURING THE TEXT, NOT THE ELEMENT. The clearance
		is padding inside the box, so a rect on the column still reads
		20 and looks like a collision after the fix. Use a Range over
		the line's contents.
	*/
	--sfsg-rail-clear: max(0px, 58px - var(--sfsg-gutter));

	/*
		AND THE PANEL NEEDS ITS OWN SUM, which this file said it did
		not until it was looked at on a phone. The claim was that the
		panel's text starts at its own padding and so already clears:
		at 375 that padding is 18px inside a 20px gutter, so the text
		lands at 38 against a rail ending at 40 — two pixels under it,
		measured, with the "H" of the name and the "B" of the address
		both clipped.

		It is a different sum from the head's because the text starts
		at the card's padding rather than at the section's content
		edge, so it needs less. The max() makes it a no-op the moment
		the normal padding already does the job: 28px at 1440, 38 at
		375, which puts the panel's text on the same 58 the headline
		sits at.

		46px is the rail's DESKTOP width; it is 40 below 782px, so
		using the wider figure throughout buys 6px of slack on a
		phone rather than cutting it fine. .sfdw__card does the same.

		IT IS NOT ON THE KNOB. That is decoration, and a decoration
		passing behind the rail is what the rail does on every page —
		.sfcg lets photographs pass under it for the same reason.
		Only text has to clear.
	*/
	--sfsg-card-pad:    clamp(18px, 1.9vw, 28px);
	--sfsg-rail-w:      46px;
	--sfsg-card-indent: max(
		var(--sfsg-card-pad),
		calc(var(--sfsg-rail-w) + 12px - var(--sfsg-gutter))
	);

	position: relative;

	/*
		THE BOTTOM IS SHORTER THAN THE TOP, and this is the only band
		on the page where that is true.

		Every other band carries clamp(72px, 7.5vw, 128px) on both
		edges, and this one did too: 108px at 1440 under a caption row
		16px tall, with the footer starting immediately after it. The
		operator saw it as empty space, and they were right — the
		house value is pitched for a band that has another band under
		it, and the footer brings its own air. Measured at 1440: the
		footer's top edge sits exactly on this section's bottom edge,
		so the two paddings simply add up.

		**AND THE TOP CAME DOWN TOO, an hour later** — operator:
		"reduce more a space .. maybe margin bottom for second last
		section and space margin top for last section".

		The note here used to say the top kept the house value because
		the dealer wall above is a band like any other. That was
		wrong twice over: this band is the page's LAST, so the dealer
		wall's bottom edge now only ever meets this one — and more to
		the point, **air between two bands is the SUM of their two
		paddings**, which is easy to miss when you are reading one
		file. 108 + 108 was 216px at 1440 between a caption row and an
		eyebrow, both 10-11px labels.

		**THIS IS HALF OF A PAIR.** `dealer-wall.css` carries the same
		value on its bottom, written the same way and pointing back
		here. Change one and check the other, or the gap goes
		lopsided — and if a band is ever inserted between them, both
		revert to the house clamp(72px, 7.5vw, 128px).
	*/
	padding-top: clamp(40px, 3.6vw, 64px);
	padding-bottom: clamp(48px, 4.4vw, 72px);
	padding-inline: var(--sfsg-gutter);   /* symmetric — see above */

	/* ONE SURFACE FOR THE HOME PAGE. Both diagonals are needed — the
	   light one is the sheen on the tow, the dark one the shadow
	   under it, and with one alone it reads as corduroy. Copy both
	   halves or the band shows a seam against its neighbours. */
	background-color: var(--sfsg-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(--sfsg-ink);
	font-family: var(--sfsg-display);
}


/* -------------------------------------------------------------
 * 1. THE TWO COLUMNS
 * ----------------------------------------------------------- */

/*
	The statement takes about four tenths and the panel the rest,
	which is the reference's own split (their text block runs to
	about 38% of the band before the card begins). Below 1024px they
	stack, statement first.

	`minmax(0, …)` on both tracks: without it a long unbreakable
	string in the panel — the distributor's name is 29 characters
	with no good break — can push a grid track past its share and
	give the page a horizontal scrollbar. This project has lost a
	round to a sideways scroll before.
*/
.sfsg__wrap{
	display: grid;
	grid-template-columns: minmax(0, 1fr);
	gap: clamp(36px, 4vw, 56px);
	align-items: start;
}

@media (min-width: 1024px){
	.sfsg__wrap{
		grid-template-columns: minmax(0, .72fr) minmax(0, 1fr);
		column-gap: clamp(40px, 4.6vw, 88px);
	}

	/* The two small labels under the panel belong to the panel, so
	   they sit in its column rather than under the whole band. */
	.sfsg__caption{ grid-column: 2 }
}

/*
	THE LEFT TRACK WIDENS AT THE TOP STEP, AND THE TITLE IS WHY.

	The ladder jumps 72px -> 112px at 1900, which is a 56% increase in
	one step, while the column only grows with the viewport. Measured
	at .72fr: the widest line came out 688px against a 686px column —
	**two pixels over**, which is not a margin, it is a coincidence.

	It reports NOTHING. The line is already on its own row, so it does
	not re-wrap; it simply paints 2px into the 88px column gap, and
	`scrollWidth === clientWidth` stays true because there is room in
	the gap to spill into. The page looks fine and the measure is
	wrong, which is the failure this project has recorded from three
	other bands.

	.85fr gives the title 759px at 1900, so "SINGAPORE." — the longest
	word, and the one that decides this — clears by about 70px. The
	panel still has 893px, more than it has at any other width.

	**REDO THAT SUM IF EITHER LINE IS REWRITTEN**, measuring a Range
	over the line rather than the element's box: the <h2> reports the
	column's width whatever the type inside it is doing.
*/
@media (min-width: 1900px){
	.sfsg__wrap{
		grid-template-columns: minmax(0, .85fr) minmax(0, 1fr);
	}
}


/* -------------------------------------------------------------
 * 2. THE STATEMENT
 * ----------------------------------------------------------- */

.sfsg__say{
	/* The statement's text sits on the section's content edge, so it
	   carries the FULL house clearance. The panel's own blocks carry
	   the smaller --sfsg-card-indent, for the reason written beside
	   that token — they both clear the rail, by different sums. */
	padding-left: var(--sfsg-rail-clear);
}

.sfsg__eyebrow{
	margin: 0 0 clamp(14px, 1.4vw, 20px);
	font-family: var(--sfsg-tech);
	font-size: 11px;
	font-weight: 500;
	letter-spacing: .16em;
	text-transform: uppercase;
	color: var(--sfsg-accent);
}

/*
	SECTION 2's TITLE TYPE, AND UPPERCASE WITH IT — operator,
	2026-11-12: "i want that title is long like section dealer and have
	effect".

	**THIS BAND IS NOW IN THE SHARED SET, which is SIX files**:
	home-opening, category-grid, video-panel, bike-ribbon, dealer-wall
	and this one. The family, the weight, the stepped ladder, the
	leading, the tracking and the case are `.sfcg__title`'s value for
	value. **CHANGE ALL SIX OR NONE** — `.sfop__title` carries the note
	on why they are literals rather than one shared token, and that
	reasoning is exactly why a seventh copy is a liability rather than
	a convenience.

	IT WAS SMALLER AND MIXED CASE FOR A FEW HOURS on the day it was
	built, and the argument then was that a statement beside an
	illustration is a caption to it rather than the page's big title.
	That was overruled on sight: the band's left column was 303px
	shorter than its panel, measured on the live page, and a small
	headline is what left the hole.

	THE LADDER IS STEPPED, NOT A CLAMP, because section 2's is — the
	steps and their breakpoints are sohub.digital's own, and the
	leading and tracking are ratios so only the size moves.

	**THE COLUMN IS THE CONSTRAINT HERE, NOT THE BAND.** Everywhere
	else in that set the title has the full measure; this one has about
	four tenths of it, so the 112px step at 1900 is working in a 691px
	column. The lines are written as two spans and cannot re-break
	between themselves, but each CAN wrap inside itself, and the
	longest word is what decides it: "SINGAPORE." is 10 characters, and
	it is what would overflow first. Re-measure it at 1024, 1440 and
	1900 before rewriting either line, and never add a <br> — the
	measure does the breaking, and `.sfv` already recorded what a <br>
	does to a word-splitting section.
*/
.sfsg__title{
	margin: 0 0 clamp(16px, 1.6vw, 22px);
	font-family: var(--sfsg-display);
	font-size: 30px;
	font-weight: 700;
	line-height: 1;
	letter-spacing: -.075em;
	text-transform: uppercase;
	color: var(--sfsg-ink);
}

@media (min-width:  768px){ .sfsg__title{ font-size:  48px } }
@media (min-width: 1024px){ .sfsg__title{ font-size:  60px } }
@media (min-width: 1280px){ .sfsg__title{ font-size:  72px } }
@media (min-width: 1900px){ .sfsg__title{ font-size: 112px } }

.sfsg__title .sfsg__line{ display: block }

/*
	THE SHEEN, THE "effect" THAT WAS ASKED FOR — ported from
	`.sfdw__wi.is-sheen`, which is itself `.sfcg__word`: the same ink ->
	magenta -> ink gradient clipped to the glyphs and looping for ever,
	so it reads as a light passing through the word rather than as a
	second colour.

	TWO THINGS IN IT ARE LOAD-BEARING and both are recorded elsewhere
	in this project from other bands:

	  · `background-clip: text` must be written as BOTH longhands or
	    Blink paints a solid magenta band with invisible type inside
	    it. The -webkit- one is not optional;
	  · the negative-margin / positive-padding pair gives the last
	    glyph the room the background box would otherwise clip.

	IT RIDES ON `.sfsg__wi`, THE WORD THE SPLITTER ALREADY BUILDS, so
	the sheen word takes part in the reveal like every other word. That
	is why it is named by a data attribute on the line rather than
	wrapped in a span in the markup — see the note in singapore.js.
*/
.sfsg__wi.is-sheen{
	margin-right: -.12em;
	padding-right: .12em;

	color: transparent;
	background-image: linear-gradient(90deg,
		var(--sfsg-ink)    0%,
		var(--sfsg-accent) 48%,
		var(--sfsg-ink)   100%);
	background-size: 220% 220%;
	-webkit-background-clip: text;
	background-clip: text;
	animation: sfsgSheen 5s ease infinite;
}

@keyframes sfsgSheen{
	0%   { background-position: 10% 0 }
	50%  { background-position: 91% 100% }
	100% { background-position: 10% 0 }
}

/* The loop is decoration, so it stops where motion is unwelcome — the
   word keeps the gradient, it simply holds still. */
@media (prefers-reduced-motion: reduce){
	.sfsg__wi.is-sheen{ animation: none }
}

/*
	THE WORD REVEAL. Each word sits in its own overflow:hidden mask
	and rises from 130%. Ported from .sfdw, minus the rotation and
	the blur: this headline is a third of that one's size, and both
	read as mush under 32px.

	THE PADDING / MARGIN PAIR ON THE MASK IS LOAD-BEARING — without
	it the box shaves the descenders off a word sitting still, and
	"Singapore." has two. navbar.css, bike-wall.css and dealer-wall.css
	all record the same trick.
*/
.sfsg__wd{
	display: inline-block;
	overflow: hidden;
	vertical-align: top;
	padding: .16em .08em .22em;
	margin:  -.16em -.08em -.22em;
}

.sfsg__wi{
	display: inline-block;
	transform-origin: 0 100%;
	transition:
		transform 1s cubic-bezier(.16,1,.3,1),
		opacity  .7s cubic-bezier(.22,1,.36,1);
	transition-delay: calc(var(--i, 0) * 55ms);
}

/*
	THE FAILURE MODE MUST BE "ALREADY REVEALED". Every start state in
	this file is scoped to .sfsg--js, which singapore.js adds as its
	first act — so with no JS, with the script blocked, or with the
	observer never firing (which is exactly what Claude's pane does),
	the band is simply finished rather than blank.
*/
.sfsg--js:not(.is-in) .sfsg__wi{
	transform: translate3d(0, 130%, 0);
	opacity: 0;
}

.sfsg__lede{
	max-width: 34ch;
	margin: 0;
	font-size: clamp(14px, 1.05vw, 17px);
	font-weight: 500;
	line-height: 1.62;
	color: var(--sfsg-dim);
}

.sfsg--js:not(.is-in) .sfsg__lede{
	opacity: 0;
	transform: translateY(14px);
}

.sfsg__lede{
	transition: opacity .7s ease .22s, transform .8s cubic-bezier(.2,.8,.2,1) .22s;
}


/* -------------------------------------------------------------
 * 3. THE PANEL
 * ----------------------------------------------------------- */

.sfsg__panel{
	position: relative;
	border: 0;
	border-radius: var(--sfsg-radius);
	background-color: var(--sfsg-card);

	/* Raised: light edge up-left, dark edge down-right, no border —
	   exactly as .sfdw__card and the footer's carved wordmark have
	   it. DO NOT PUT THE WEAVE ON IT: the card is flat #171717 on a
	   woven #171717 page, and that difference is the only thing
	   separating panel from page where the light does not reach. */
	box-shadow:
		-4px -4px  8px var(--sfsg-lift),
		 5px  5px 12px var(--sfsg-sink);
}

.sfsg--js:not(.is-in) .sfsg__panel{
	opacity: 0;
	transform: translateY(22px);
}

.sfsg__panel{
	transition: opacity .8s ease .1s, transform .9s cubic-bezier(.2,.8,.2,1) .1s;
}

/*
	THE KNOB IS GONE — operator, 2026-11-12: "i want you to delete that
	circle", with a screenshot of it.

	It was a 38px disc hung half off the panel's top-left corner,
	carrying the same emboss, which is the device the reference uses to
	stop its panel reading as a plain rectangle. Removed outright
	rather than left dormant, with the `.sfsg__bar-l` padding that
	existed only to clear it; both are in git.

	NOTHING ELSE DEPENDED ON IT. It was decoration, aria-hidden, and
	the only rule that referred to it was that padding — so the bar's
	left label now simply starts on the panel's own indent, which is
	where everything else in the panel starts.
*/

/* ---- the panel's header row ---- */

.sfsg__bar{
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 16px;
	padding: clamp(16px, 1.7vw, 22px) var(--sfsg-card-pad);
	padding-left: var(--sfsg-card-indent);

	/*
		THE DOTTED RULE, dozfx's own: a repeating radial-gradient of
		dots on a 5px pitch, 1px tall. Not a dashed border — a dash is
		a line with gaps in it and reads as a border somebody drew; a
		row of dots reads as a measuring edge, which is the whole
		point of the device.

		It is drawn as a background on the padding box rather than as
		a border-bottom so it runs the FULL width of the panel,
		including under the padding, the way theirs does.
	*/
	background-image: radial-gradient(circle, var(--sfsg-rule) 0 .8px, transparent .8px);
	background-size: 5px 1px;
	background-position: 0 100%;
	background-repeat: repeat-x;
}

.sfsg__bar-l,
.sfsg__bar-r{
	margin: 0;
	font-family: var(--sfsg-tech);
	font-size: 10px;
	font-weight: 600;
	letter-spacing: .16em;
	text-transform: uppercase;
}

.sfsg__bar-l{ color: var(--sfsg-ink) }

/* The reference prints its right-hand label in the accent. It is the
   only accent in the panel's chrome, so it is what marks this as a
   diagram rather than a text box — keep it. */
.sfsg__bar-r{ color: var(--sfsg-accent) }



/* -------------------------------------------------------------
 * 4. THE TWO ROUTES — the illustration
 * ----------------------------------------------------------- */

.sfsg__routes{
	display: flex;
	flex-direction: column;
	gap: clamp(26px, 2.8vw, 40px);
	padding: clamp(24px, 2.6vw, 36px) var(--sfsg-card-pad);
	padding-left: var(--sfsg-card-indent);

	/* the same dotted rule, closing the block */
	background-image: radial-gradient(circle, var(--sfsg-rule) 0 .8px, transparent .8px);
	background-size: 5px 1px;
	background-position: 0 100%;
	background-repeat: repeat-x;
}

.sfsg__route-k{
	margin: 0 0 clamp(14px, 1.5vw, 20px);
	font-family: var(--sfsg-tech);
	font-size: 10px;
	font-weight: 600;
	letter-spacing: .15em;
	text-transform: uppercase;
	color: var(--sfsg-faint);
}

.sfsg__route--live .sfsg__route-k{ color: var(--sfsg-ink) }

/*
	THE TRACK. A dotted line with nodes sitting on it, each node
	placed by its own --p percentage from the markup — so the shape
	of a route is edited where the route is written, not here.

	The line is a ::before rather than a border so it can be clipped
	open on the entrance (see .is-in below) without the nodes moving.

	THE TRACK IS `position: relative` AND THE NODES ARE ABSOLUTE at
	`left: var(--p)` with a -50% translate, which is what puts the
	first node's CENTRE on 0% and the last node's on 100% — i.e. both
	hang half outside the line's ends, as the reference's do. The row
	therefore needs no horizontal padding of its own and the line can
	run the full measure.
*/
.sfsg__track{
	position: relative;
	height: 14px;
	margin-bottom: 14px;
}

.sfsg__track::before{
	content: "";
	position: absolute;
	inset: 50% 0 auto 0;
	height: 1px;
	transform: translateY(-50%);
	background-image: radial-gradient(circle, var(--sfsg-faint) 0 .9px, transparent .9px);
	background-size: 6px 1px;
	background-repeat: repeat-x;

	/* the entrance: the line draws left to right */
	transform-origin: 0 50%;
	transition: clip-path 1.1s cubic-bezier(.16,1,.3,1) .25s;
}

.sfsg__route--live .sfsg__track::before{
	background-image: radial-gradient(circle, var(--sfsg-accent) 0 .9px, transparent .9px);
}

.sfsg--js:not(.is-in) .sfsg__track::before{ clip-path: inset(0 100% 0 0) }
.sfsg__track::before{ clip-path: inset(0 0 0 0) }

.sfsg__dot{
	position: absolute;
	top: 50%;
	left: var(--p, 0%);
	width: 9px;
	height: 9px;
	margin: -4.5px 0 0 -4.5px;
	border-radius: 50%;
	border: 1px solid var(--sfsg-faint);
	background: var(--sfsg-card);
	transition: transform .5s cubic-bezier(.2,1.4,.4,1), opacity .4s ease;
}

.sfsg__route--live .sfsg__dot{
	border-color: var(--sfsg-accent);
	background: var(--sfsg-accent);
}

/* The one node the row is about — their orchestration layer, our
   distributor. It is the only filled, oversized node in the panel,
   so it is what the eye lands on. */
.sfsg__dot--big{
	width: 17px;
	height: 17px;
	margin: -8.5px 0 0 -8.5px;
}

/*
	THE NODES POP IN AFTER THE LINE REACHES THEM, which is what makes
	the two read as one movement rather than two. The delay is a
	function of --p, so a node moved in the markup re-times itself.
	The line's own transition is 1.1s after a .25s wait; .9 of --p
	keeps every node inside that window.
*/
.sfsg__dot{ transition-delay: calc(.25s + (var(--p) / 100) * .9s) }

.sfsg--js:not(.is-in) .sfsg__dot{
	transform: scale(0);
	opacity: 0;
}

/* ---- the labels under the track ---- */

/*
	Three cells, each aligned to the node it belongs to: the first
	node is at 0% so its label starts at the left edge, the big one
	is at 50% so its label is centred, the last is at 100% so its
	label ends at the right edge. Move a node's --p and the label
	stops pointing at it — they are a pair.
*/
.sfsg__legend{
	display: grid;
	grid-template-columns: repeat(3, minmax(0, 1fr));
	align-items: start;
	gap: 10px;
	margin: 0;
	font-size: 12.5px;
	font-weight: 500;
	line-height: 1.35;
	color: var(--sfsg-faint);
}

.sfsg__legend span:nth-child(1){ text-align: left }
.sfsg__legend span:nth-child(2){ text-align: center }
.sfsg__legend span:nth-child(3){ text-align: right }

.sfsg__route--live .sfsg__legend{ color: var(--sfsg-dim) }

.sfsg__route--live .sfsg__legend span:nth-child(2){
	font-weight: 700;
	color: var(--sfsg-ink);
}


/* -------------------------------------------------------------
 * 5. THE DISTRIBUTOR'S CARD
 * ----------------------------------------------------------- */

/*
	THIS IS THE DEALER PAGE'S OWN CARD, re-set at this band's sizes:
	name in uppercase display type, phone on the right, a magenta
	role line under it, the address in the muted ink. Somebody who
	has been to /dealer-distributor/ should recognise it.

	THE NAME IS UPPERCASED BY CSS AND MIXED CASE IN THE MARKUP, which
	is what .sf-dealers__name does — so a screen reader and the page
	source both carry the company's name as it is written, and the
	shouting is a presentation choice that reverts in one line.

	That is deliberately the OPPOSITE of the rule bike-wall.css
	carries, where the case distinguishes a make from a model badge
	and so belongs in the words. Nothing here turns on case.
*/
.sfsg__card{
	padding: clamp(20px, 2.2vw, 30px) var(--sfsg-card-pad);
	padding-left: var(--sfsg-card-indent);
}

.sfsg__card-top{
	display: flex;
	align-items: baseline;
	justify-content: space-between;
	gap: clamp(14px, 1.6vw, 28px);
	margin: 0 0 10px;
}

.sfsg__name{
	margin: 0;
	font-family: var(--sfsg-display);
	font-size: clamp(17px, 1.65vw, 26px);
	font-weight: 700;
	line-height: 1.12;
	letter-spacing: -.02em;
	text-transform: uppercase;
	color: var(--sfsg-ink);
}

/*
	THE PHONE IS A REAL `tel:` LINK and is the only interactive thing
	in the band. The href is digits and a leading + — "+65-6275 6656"
	dials as +6562756656 — while the visible text keeps the operator's
	own formatting, which is the courtesy the dealer list extends to
	Malaysian numbers.

	`white-space: nowrap` because a phone number broken across two
	lines is not a phone number.
*/
.sfsg__tel{
	display: inline-flex;
	align-items: center;
	gap: 8px;
	flex: none;
	white-space: nowrap;
	font-family: var(--sfsg-display);
	font-size: clamp(13px, .95vw, 15px);
	font-weight: 700;
	letter-spacing: -.01em;
	text-decoration: none;
	color: var(--sfsg-ink);
	transition: color .25s ease;
}

.sfsg__tel:hover,
.sfsg__tel:focus-visible{ color: var(--sfsg-accent) }

/* The two glyphs are inline SVG, not Font Awesome: this band must
   render identically in the local harness, which loads no icon font,
   and two paths are cheaper than a dependency. They inherit
   currentColor, so the phone's hover carries its icon with it. */
.sfsg__i{
	width: 1em;
	height: 1em;
	flex: none;
	fill: currentColor;
}

.sfsg__meta{
	display: flex;
	align-items: center;
	gap: 7px;
	margin: 0 0 10px;
	font-family: var(--sfsg-tech);
	font-size: 11px;
	font-weight: 600;
	letter-spacing: .15em;
	text-transform: uppercase;
	color: var(--sfsg-accent);
}

.sfsg__meta .sfsg__i{ width: 1.15em; height: 1.15em }

.sfsg__addr{
	margin: 0;
	max-width: 52ch;
	font-size: clamp(13px, .95vw, 15px);
	font-weight: 500;
	line-height: 1.5;
	color: var(--sfsg-faint);
}


/* -------------------------------------------------------------
 * 6. THE TWO LABELS UNDER THE PANEL
 * ----------------------------------------------------------- */

/* Outside the panel, not in it — the reference prints the same pair
   in the page's own margin, which is what makes the panel read as a
   figure with a caption rather than as a box with a footer. */
.sfsg__caption{
	display: flex;
	align-items: baseline;
	justify-content: space-between;
	gap: 16px;
	margin: clamp(14px, 1.4vw, 20px) 0 0;
	padding-inline: clamp(2px, .4vw, 6px);
	font-family: var(--sfsg-tech);
	font-size: 10px;
	font-weight: 600;
	letter-spacing: .16em;
	text-transform: uppercase;
	color: var(--sfsg-faint);
}

.sfsg__caption span:last-child{ text-align: right }


/* -------------------------------------------------------------
 * 7. PHONES
 * ----------------------------------------------------------- */

@media (max-width: 699px){
	/*
		THE LEGEND STOPS POINTING AT NODES AND BECOMES A SENTENCE.
		Three equal cells at this width give each label about a third
		of 300px, and "HKL Lim Team Motorsport" takes four lines in
		it. As a flowed row with arrows between the parts it says the
		same thing in one or two lines and still reads as a route.

		The arrow is a ::before on every span but the first, so it
		follows the number of labels rather than needing its own
		markup — and it is decoration, so it is not announced.
	*/
	.sfsg__legend{
		display: flex;
		flex-wrap: wrap;
		align-items: baseline;
		gap: 4px 8px;
		font-size: 12px;
	}

	.sfsg__legend span{ text-align: left !important }

	.sfsg__legend span + span::before{
		content: "\2192";
		margin-right: 8px;
		color: var(--sfsg-faint);
	}

	/* The name and the phone stop sharing a line: at 335px the name
	   wraps to three lines and the number is pushed against the right
	   edge of the card with 20px of ragged air beside it. */
	.sfsg__card-top{
		flex-direction: column;
		align-items: flex-start;
		gap: 10px;
	}

	/* Two tracked-out labels at opposite ends of a 335px line leave
	   about 60px each and both wrap. The second one is the one that
	   can go: the first names the country, which is the point. */
	.sfsg__caption span:last-child{ display: none }
}


/* -------------------------------------------------------------
 * 8. REDUCED MOTION
 * ----------------------------------------------------------- */

/*
	Everything here is an entrance, so under reduced motion the band
	is simply finished — the same end state the no-JS path gives. The
	rules are cleared rather than shortened: a 0s transition on a
	clip-path still repaints, and there is nothing to be gained from
	it.
*/
@media (prefers-reduced-motion: reduce){
	.sfsg--js:not(.is-in) .sfsg__wi,
	.sfsg--js:not(.is-in) .sfsg__lede,
	.sfsg--js:not(.is-in) .sfsg__panel,
	.sfsg--js:not(.is-in) .sfsg__dot{
		transform: none;
		opacity: 1;
	}

	.sfsg--js:not(.is-in) .sfsg__track::before{ clip-path: inset(0 0 0 0) }

	.sfsg__wi,
	.sfsg__lede,
	.sfsg__panel,
	.sfsg__dot,
	.sfsg__track::before{ transition: none }
}
