/*
	THE REVIEW BAND (2026-11-17)
	============================

	Two places, because reviews do two jobs: a compact rating under the
	title INSIDE the buy rail, read before Add to cart rather than
	below the fold; and the full block as its own band BETWEEN the
	product and the related products — explained, then vouched for,
	then alternatives. WooCommerce renders it AFTER the related
	products, which puts it below the exit.

	**THE STORE HAS NO REVIEWS, SO THE EMPTY STATE IS THE ONE THAT
	SHIPS.** `wc/v3/products/reviews` returns `X-WP-Total: 0` and this
	product renders `.woocommerce-noreviews`. The band reads that from
	the page every time — there is no count, no average and no copy
	typed into this stylesheet or its script. The moment a real review
	lands the summary appears on its own.

	NO SCORE, NO HISTOGRAM, NO ZERO in the empty state. "0.0" beside
	five empty stars reads as a product rated BADLY rather than one not
	yet rated, and a histogram of five empty rows is five lines of
	nothing.
*/

.sf-rv{
	margin:0 auto;
	padding:clamp(48px, 5vw, 88px) 0 0;
}

.sf-rv__head{
	display:flex;
	align-items:center;
	justify-content:space-between;
	gap:16px;
	flex-wrap:wrap;
	margin-bottom:24px;
}
/*
	THE TITLE'S TYPE LIVES IN pdp-related.css (2026-11-18), which sets it on
	this heading and on the related band's in one rule -- the product
	category archive's own Inter 700 ladder, with the sheen. Its selector is
	(0,2,0) and the one that used to be here was (0,1,0), so this one lost
	whatever the load order; it is deleted rather than left to look like it
	still decides something.

	WHAT IT WAS: Archivo Black, clamp(28px, 3.2vw, 44px), 700, 1.1, -.02em,
	and accent-1 for the whole heading.
*/

/*
	AND WooCOMMERCE'S OWN "Reviews" HEADING GOES (operator: "i want you to
	remove both .. cause the review section already in middle section").
	`#reviews` is MOVED into this band by pdp-reviews.js, so it arrives with
	its own h2 -- a second, smaller "REVIEWS" with a rule, directly under the
	band's. Hidden rather than removed from the DOM: it is WooCommerce's
	node, it carries the review list's heading semantics, and the script
	already has enough of its markup to worry about.
*/
.sf-rv .woocommerce-Reviews-title{
	display:none;
}

/*
	THE LEFTOVER TAB BAR GOES WITH IT. The Product Details block renders a
	`ul.tabs.wc-tabs` whose only tab is "Reviews (0)" and whose panel this
	script empties when it moves the reviews out -- so the block paints a
	stray 28px tab and nothing else.

	THE CLASS IS ADDED BY THE SCRIPT, AND ONLY WHEN EVERY PANEL IS EMPTY.
	Hiding the block from CSS alone would hide a description tab too, on any
	product that still has one.
*/
.wp-block-woocommerce-product-details.is-sf-emptied{
	display:none;
}
.sf-rv__count{
	font-size:14px;
	font-weight:400;
	color:var(--sp-muted, #9a9a98);
}

/* ---- stars ------------------------------------------------------- */
.sf-rv__stars{ display:inline-flex; gap:3px; vertical-align:middle; }
.sf-rv__stars svg{ display:block; }
.sf-rv__on{ fill:var(--wp--preset--color--accent-1, #ec1e79); }
/*
	An outline star, not a grey filled one. A filled grey star reads as
	a DIM star — half-earned — where an outline reads as an empty slot.
	That difference is the whole of the empty state.
*/
.sf-rv__off{
	fill:none;
	stroke:var(--wp--preset--color--accent-1, #ec1e79);
	stroke-width:1.4;
	opacity:.5;
}

/* ---- the rail line ----------------------------------------------- */
.sf-rv-rail{
	display:flex;
	align-items:center;
	gap:8px;
	flex-wrap:wrap;
	margin:-8px 0 20px;
	font-size:14px;
	font-weight:400;
	color:var(--sp-text, #f2f2f4);
}
.sf-rv-rail__link{
	color:var(--wp--preset--color--accent-1, #ec1e79);
	text-decoration:underline;
	text-underline-offset:3px;
}

/* ---- empty state -------------------------------------------------- */
.sf-rv__empty{
	display:grid;
	justify-items:center;
	text-align:center;
	gap:16px;
	padding:clamp(40px, 5vw, 64px) 24px;
	border-top:1px solid var(--sp-line, rgba(242,242,244,.14));
	border-bottom:1px solid var(--sp-line, rgba(242,242,244,.14));
}
.sf-rv__lead{ font-size:clamp(20px, 2vw, 24px); font-weight:500; color:var(--sp-text, #f2f2f4); }
.sf-rv__sub{
	font-size:15px;
	font-weight:400;
	line-height:1.5;
	color:var(--sp-muted, #9a9a98);
	max-width:46ch;
}

/* ---- the button --------------------------------------------------- */
/*
	Magenta fill, near-black label — 4.55:1. White on this magenta is
	4.10:1 and fails.
*/
.sf-rv__btn{
	display:inline-block;
	padding:13px 22px;
	border:0;
	border-radius:var(--sp-radius, 12px);
	cursor:pointer;
	font-family:inherit;
	font-size:14px;
	font-weight:600;
	letter-spacing:.01em;
	color:#101014;
	background:var(--wp--preset--color--accent-1, #ec1e79);
}
.sf-rv__btn--ghost{
	background:transparent;
	color:var(--wp--preset--color--accent-1, #ec1e79);
	border:1px solid var(--wp--preset--color--accent-1, #ec1e79);
}

/* ---- WooCommerce's own reviews, moved in -------------------------- */
/*
	The real `#reviews` node is MOVED into this band, not copied — so
	the comment list, the form, its nonce and every listener on it are
	WooCommerce's own and keep working. `.woocommerce-noreviews` is
	hidden because the empty state above says the same thing better.
*/
.sf-rv .woocommerce-noreviews{ display:none; }
/*
	THE FORM GATING MOVED to the block at the foot of this file (2026-11-18).
	It used to be hidden for the empty state ONLY, and nothing gated the
	other one -- so a product with a single review served every visitor an
	open textarea the width of the page. It is behind the button in both
	states now, and the form is a card at the end of the list.
*/
.sf-rv .comment-reply-title{
	font-size:18px;
	font-weight:600;
	color:var(--sp-text, #f2f2f4);
	display:block;
	margin-bottom:12px;
}

@media (max-width: 760px){
	.sf-rv__head{ gap:12px; }
}

/* ==================================================================
   THE BAND FILLS NOW (2026-11-18)
   ==================================================================

   Operator, looking at the live band: "i think its not perfect UI do you
   have any suggestion cause itss looks too emptyy". It was: a title, the
   score 1,300px away at the far right of its row, one line of apology and
   a screen of carbon — and, once a product had a single review, an open
   1,730px textarea nobody had asked for.

   Three designs went up on localhost (docs/home-concepts/reviews-lab,
   which also holds the two that were not chosen and the measurements)
   and the operator chose the STRIP: the score, the five distribution bars
   and the button in one house panel across the top, with the reviews as
   cards two-up underneath.

   TWO PASSES WERE REJECTED BEFORE IT AND BOTH WERE RIGHT. The first
   clamped its sketches into a narrow DIV, which does not fire viewport
   media queries, so they had never laid out at a phone width at all. The
   second answered the wrong complaint — it removed furniture from a band
   that was being called empty — and rendered the review list outside
   `#reviews`, so none of single-product.css's `#reviews ...` rules matched
   and every proposal was judged looking unstyled.

   NOTHING HERE INVENTS CONTENT. No fake review, no placeholder rating, no
   zero score. Every figure is still read from the page by pdp-reviews.js.

   IT IS ONE COLUMN BELOW 900px, so there is nothing to collapse — the
   two-up grid and the strip are only ever ADDED, which is what makes this
   responsive by construction rather than by a media query somebody has to
   remember to undo.
   ================================================================== */

.sf-rv{
	--rv-gap:     clamp(20px, 2.4vw, 32px);
	--rv-pad:     clamp(18px, 1.8vw, 26px);
	--rv-measure: 68ch;

	/*
		THE HOUSE PANEL, and these three are literals rather than one shared
		token on purpose — the decision this project already records for the
		type ladder. 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. Same values as .sfdw__card and .sfcg__card.
	*/
	--rv-face: #0d0d10;
	--rv-lift: rgba(255, 255, 255, .06);
	--rv-sink: rgba(0, 0, 0, .45);
}

/*
	A hairline closes the head, which is how every other band on this site
	heads itself. The score is NOT here any more — it is in the strip, over
	the bars it belongs to.
*/
.sf-rv .sf-rv__head{
	display:block;
	padding-bottom:20px;
	margin-bottom:var(--rv-gap);
	border-bottom:1px solid var(--sp-line, rgba(242,242,244,.16));
}

.sf-rv .rv-cols{
	display:grid;
	gap:var(--rv-gap);
}

/* ---- the score strip ---------------------------------------------- */
.sf-rv .rv-summary{
	align-self:start;
	padding:var(--rv-pad);
	border-radius:12px;
	background:var(--rv-face);
	box-shadow:-4px -4px 10px var(--rv-lift), 5px 5px 14px var(--rv-sink);
	box-sizing:border-box;
}

.sf-rv .rv-summary__score{
	display:flex;
	align-items:center;
	flex-wrap:wrap;
	gap:6px 12px;
	margin-bottom:18px;
}

.sf-rv .rv-summary__n{
	font-family:var(--sp-title, "Archivo Black", sans-serif);
	font-size:44px;
	line-height:1;
	color:var(--sp-text, #f2f2f4);
}

.sf-rv .rv-summary__c{
	flex-basis:100%;
	font-family:var(--sp-tech, "Chakra Petch", sans-serif);
	font-size:11px;
	font-weight:600;
	letter-spacing:.14em;
	text-transform:uppercase;
	color:var(--sp-muted, #9a9a9f);
}

/*
	FIVE ROWS ALWAYS, INCLUDING THE ZEROES. A chart that draws only the rows
	with something in them is a list, not a distribution — and the empty
	rows are what tell a reader that 5.0 is out of five rather than out of
	nothing.

	THE BARS ARE NOT ALWAYS DRAWN. pdp-reviews.js returns no distribution at
	all when it cannot see every review (pagination, or WooCommerce's own
	total disagreeing with the cards on the page), because a histogram of
	page one labelled as the product is worse than none. The strip is built
	to read correctly without them.
*/
.sf-rv .rv-bars{
	margin:0 0 18px;
	padding:0;
	list-style:none;
	display:grid;
	gap:7px;
}

.sf-rv .rv-bars li{
	display:grid;
	grid-template-columns:1ch 1fr 2ch;
	align-items:center;
	gap:10px;
	font-family:var(--sp-tech, "Chakra Petch", sans-serif);
	font-size:11px;
	font-weight:600;
	color:var(--sp-muted, #9a9a9f);
}

.sf-rv .rv-bars__t{
	height:5px;
	border-radius:999px;
	background:rgba(242,242,244,.10);
	overflow:hidden;
}

.sf-rv .rv-bars__t i{
	display:block;
	height:100%;
	border-radius:999px;
	background:var(--wp--preset--color--accent-1, #ec1e79);
}

.sf-rv .rv-bars__n{ text-align:right; }

.sf-rv .rv-summary .sf-rv__btn{ width:100%; }

@media (min-width: 760px){
	.sf-rv .rv-summary{
		display:grid;
		grid-template-columns:auto minmax(220px, 420px) auto;
		align-items:center;
		column-gap:clamp(24px, 3vw, 56px);
	}

	.sf-rv .rv-summary__score{ margin:0; }
	.sf-rv .rv-bars{ margin:0; }
	.sf-rv .rv-summary .sf-rv__btn{ width:auto; }
}

/* ---- the reviews, as cards ----------------------------------------- */
/*
	(1,3,0) so it beats `.sf-pdp__editorial #reviews .comment_container`,
	which is (1,2,0) and carries the hairline-and-margin version this
	replaces. Tying on specificity and relying on load order would work
	today and break the day the enqueue order changes.
*/
.sf-pdp__editorial .sf-rv #reviews .comment_container{
	padding:var(--rv-pad);
	margin:0;
	border-bottom:0;
	border-radius:12px;
	background:var(--rv-face);
	box-shadow:-4px -4px 10px var(--rv-lift), 5px 5px 14px var(--rv-sink);
}

.sf-pdp__editorial .sf-rv #reviews li.review + li.review{ margin-top:var(--rv-gap); }

/*
	`#reviews` IS THE GRID, and that is what lets the form card be placed
	relative to the list without being inside it — see the `order` below.
*/
.sf-rv #reviews{
	display:grid;
/* 	gap:var(--rv-gap); */
	gap: 8px;
}

.sf-rv #reviews .commentlist{ display:block; }

/*
	AND ITS CLEARFIX HAS TO GO, OR IT EATS THE FIRST CELL.

	 carries the old clearfix pair -- content:" " with
	display:table on ::before and ::after. In a BLOCK container those are
	invisible. **A grid container promotes its own ::before and ::after into
	GRID ITEMS**, so the two-up grid handed cell one to ::before and the
	first review landed in the right-hand column with the second alone on
	the row below. Measured live: review 1 at x731, review 2 at x60.

	NOTHING IN THIS BAND FLOATS, so the clearfix has no work to do either
	way. Hidden rather than reset to content:none so it is obvious what is
	being switched off.

	IT IS STATED AT (2,3,2). WooCommerce sets it as
	`.woocommerce #reviews #comments ol.commentlist::before`, which is
	(2,2,1) -- two ids -- so the obvious `.sf-rv #reviews .commentlist`
	at (1,2,0) lost, served correctly and changed nothing. The computed
	display stayed `table` and the cards stayed staggered.

	THE LOCAL HARNESS COULD NOT SHOW THIS -- its markup is written by hand
	and carries no clearfix, so the stagger only appeared on the live page.
	The general rule is worth keeping: turning a clearfixed element into a
	grid or a flex container gives you two items you did not write.
*/
body.woocommerce .sf-rv #reviews #comments ol.commentlist::before,
body.woocommerce .sf-rv #reviews #comments ol.commentlist::after{ display:none; }

@media (min-width: 900px){
	.sf-rv #reviews .commentlist{
		display:grid;
		grid-template-columns:repeat(2, minmax(0, 1fr));
		gap:var(--rv-gap);
	}

	/* the grid gap is the spacing now; the stacked margin would double it */
	.sf-pdp__editorial .sf-rv #reviews li.review + li.review{ margin-top:0; }
}

/* ---- the invitation, empty state only ------------------------------- */
.sf-rv .rv-invite{
	display:grid;
	gap:var(--rv-gap);
	padding:clamp(22px, 2.4vw, 34px);
	border-radius:12px;
	background:var(--rv-face);
	box-shadow:-4px -4px 10px var(--rv-lift), 5px 5px 14px var(--rv-sink);
	box-sizing:border-box;
}

.sf-rv .rv-invite__lead{
	margin:0 0 10px;
	font-family:var(--sp-title, "Archivo Black", sans-serif);
	font-size:clamp(20px, 2vw, 26px);
	line-height:1.15;
	color:var(--sp-text, #f2f2f4);
}

.sf-rv .rv-invite__sub{
	margin:0 0 20px;
	max-width:42ch;
	font-size:15px;
	line-height:1.55;
	color:var(--sp-muted, #9a9a9f);
}

.sf-rv .rv-prompts{
	margin:0;
	padding:0;
	list-style:none;
	display:grid;
	gap:14px;
}

.sf-rv .rv-prompts li{
	display:grid;
	gap:5px;
	padding-left:14px;
	border-left:2px solid var(--wp--preset--color--accent-1, #ec1e79);
}

.sf-rv .rv-prompts__k{
	font-family:var(--sp-tech, "Chakra Petch", sans-serif);
	font-size:11px;
	font-weight:700;
	letter-spacing:.14em;
	text-transform:uppercase;
	color:var(--sp-text, #f2f2f4);
}

.sf-rv .rv-prompts__v{
	font-size:14px;
	line-height:1.5;
	color:var(--sp-muted, #9a9a9f);
}

@media (min-width: 760px){
	.sf-rv .rv-invite{ grid-template-columns:minmax(0, 1fr) minmax(0, 1fr); }
}

/* ---- the form, a card at the END of the list ------------------------ */
/*
	THE ONE BEHAVIOUR CHANGE, and it is the bulk of what read as empty: the
	form used to be gated for `.is-empty` and NOTHING gated the other state,
	so a product with a single review served every visitor an open textarea
	the width of the page. It is behind the button in both states now.

	IT OPENS AS A CARD IN THE LIST (operator: "add another card like the
	review inside this"), so writing a review looks like ADDING one: same
	panel, same radius, same emboss as the cards either side of it.

	AND IT OPENS LAST (operator: "i want its a last not first"). It was at
	the top first, on the reasoning that the button is up in the strip — but
	the list reads oldest to newest down the page, so the card you are
	adding belongs at the end where yours will appear, and opening at the
	top shoved every existing review down the page on a button press.
*/
.sf-rv #review_form_wrapper{
	display:none;
	order:1;
	margin-top:0;
	padding:clamp(16px, 1.6vw, 20px);
	border-radius:12px;
	background:var(--rv-face);
	box-shadow:-4px -4px 10px var(--rv-lift), 5px 5px 14px var(--rv-sink);
	box-sizing:border-box;
}

.sf-rv.is-writing #review_form_wrapper{ display:block; }

@media (min-width: 900px){
	/*
		A CARD'S WIDTH, NOT THE ROW'S. The form is a sibling of the list
		rather than a cell in it, so left alone it spans the whole measure
		and reads as a form with the cards above it — the thing being
		replaced. Held to one column of the two-up grid it reads as the card
		you are about to add.

		It is CAPPED rather than made a grid item: putting it in the grid
		needs display:contents on the list, and a display:contents that a
		media query later undoes is what collapsed the first pass of this.
	*/
	.sf-rv #review_form_wrapper{ max-width:calc((100% - var(--rv-gap)) / 2); }
}

/*
	THE CARD'S OWN WIDTH IS THE LIST'S, BUT THE FORM INSIDE IT IS MEASURED.
	Letting the fields run the full card is the fault this pass is fixing.
*/
.sf-rv #review_form_wrapper .comment-form,
.sf-rv #review_form_wrapper .comment-form-rating{ max-width:var(--rv-measure); }

/*
	AS CLOSE TO A REVIEW CARD'S SIZE AS A FORM GETS (operator: "the card too
	big"). Matching the width alone left it 330px beside cards of 152 and
	177, because WooCommerce ships the textarea at rows="6", stacks the
	rating label above its stars, and single-product.css gives the submit
	row 20px of its own. Six values came down and it measures 271.

	IT CANNOT ACTUALLY EQUAL ONE, and that is worth saying rather than
	pretending. A disc, a rating row, a field and a submit have a floor of
	about 32 + 20 + 72 + 40 plus the card's padding. Below that something
	real goes, and the first candidate is the rating control — the one part
	of a review that cannot be typed.

	THE TEXTAREA IS SET IN CSS, NOT BY THE rows ATTRIBUTE, because the form
	is WooCommerce's own markup and nothing in this theme writes it. It
	stays resizable, so anyone with more to say drags it.
*/
.sf-rv #review_form_wrapper #review_form .comment-reply-title,
.sf-rv #review_form_wrapper #review_form #reply-title{
	display:flex;
	align-items:center;
	gap:12px;
	margin:0 0 12px;
	font-family:var(--sp-tech, "Chakra Petch", sans-serif);
	font-size:11px;
	font-weight:700;
	letter-spacing:.14em;
	text-transform:uppercase;
	color:var(--sp-text, #f2f2f4);
}

/*
	The heading becomes the card's author line, with a disc where a
	reviewer's initial would be — the same 40px disc (at 32 here)
	`.sf-pdp__editorial #reviews .avatar` draws, restated because this
	element is not inside `.comment_container` and never matches that rule.

	STATED AT (2,2,0) AND (3,1,0). single-product.css sets this element as
	`.sf-pdp__editorial #review_form #reply-title` -- TWO IDS, so (2,1,0) --
	which beats the obvious (1,2,0) and kept it 18px Archivo Black on a
	block, with the disc stacked above the words. That file is id-heavy
	throughout its review-form section; match its ids rather than piling on
	classes.
*/
.sf-rv #review_form_wrapper #review_form .comment-reply-title::before,
.sf-rv #review_form_wrapper #review_form #reply-title::before{
	content:"+";
	flex:none;
	width:32px;
	height:32px;
	border-radius:50%;
	display:grid;
	place-items:center;
	background:rgba(236,30,121,.14);
	color:var(--wp--preset--color--accent-1, #ec1e79);
	font-family:var(--sp-title, "Archivo Black", sans-serif);
	font-size:15px;
	letter-spacing:0;
}

/*
	The rating label and its stars share a row. Stacked they are two lines
	for five characters of content, which is the cheapest 17px in the card.
*/
.sf-pdp__editorial .sf-rv #review_form_wrapper .comment-form-rating{
	display:flex;
	align-items:center;
	flex-wrap:wrap;
	gap:6px 12px;
	margin-bottom:10px;
}

.sf-pdp__editorial .sf-rv #review_form_wrapper .comment-form-rating label{ margin:0; }
.sf-pdp__editorial .sf-rv #review_form_wrapper .comment-form-rating p.stars{ margin:0; }

.sf-pdp__editorial .sf-rv #review_form_wrapper .comment-form-comment{ margin-bottom:0; }
.sf-pdp__editorial .sf-rv #review_form_wrapper .comment-form-comment label{ margin-bottom:6px; }

.sf-pdp__editorial .sf-rv #review_form_wrapper textarea{
	height:72px;
	min-height:72px;
	resize:vertical;
}

.sf-pdp__editorial .sf-rv #review_form_wrapper .form-submit{ margin-top:12px; }
.sf-pdp__editorial .sf-rv #review_form_wrapper .form-submit .submit{ padding:10px 20px; }

/*
	THE OLD EMPTY BLOCK IS NO LONGER EMITTED. pdp-reviews.js builds the
	invitation above instead; `.sf-rv__empty` and `.sf-rv__count`'s rules are
	left in place because restoring either is then one line of script, and
	hidden here so a stale cached script cannot paint both at once.
*/
.sf-rv .rv-cols .sf-rv__empty{ display:none; }

/* ==================================================================== */
/*  THE WRITE BUTTON, AND THE FORM AS A FULL-WIDTH BAR (2026-11-18)      */
/* ==================================================================== */
/*
	Operator, with the strip and the open form side by side: "button write
	a review i want color full #ec1e79 and border radius is 12px, and the
	text Write a review is color white ... then for this i want the height
	follow this [a review card] then the content is not responsive, i want
	its full width or you have another sugestion".

	Added as a block at the foot of the file rather than edited in place:
	every rule it supersedes carries the argument for a decision that was
	right when the card was half a row wide, and deleting this block puts
	all of it back exactly.
*/

/*
	THE BUTTON WAS A GHOST AND ITS RADIUS WAS NEVER 12px.

	Two separate faults, and only one of them was asked about. The strip's
	button was built with `sf-rv__btn--ghost` -- transparent, magenta text,
	a magenta hairline -- which is now gone from pdp-reviews.js, so it takes
	the filled base. And the base asks for `var(--sp-radius, 12px)`, which
	reads as 12 and ISN'T: single-product.css declares `--sp-radius: 2px`
	for the product page, so the fallback never fires and the button painted
	at 2px. **A var() fallback only applies when the token is UNDECLARED**,
	not when it is declared to something you did not expect. It is a literal
	12 here, which is also what the cards, the strip and the form card round
	themselves to.

	WHITE, NOT THE #101014 IT HAD. Asked for by name. It measures 4.55:1 on
	this magenta against the dark ink's 5.2:1 -- still AA at 14px/600, and
	the thing to watch if the type ever gets smaller or lighter.

	`--ghost` IS LEFT IN PLACE AND IS NOW READ BY NOTHING. One line of
	script brings it back.
*/
.sf-rv .sf-rv__btn{
	border-radius: 12px;
	color: #fff;
}

/*
	THE CARD STAYS ONE COLUMN WIDE; ONLY ITS CONTENT GOES FULL WIDTH
	(operator, 2026-11-18, correcting the first cut: "no i mean full width
	the content not the card").

	SO THERE WERE TWO CAPS AND ONLY THE INNER ONE WAS WRONG. The card is
	held to one column of the two-up list by the rule above, which is what
	makes writing a review look like adding a card to it -- that stands. The
	FIELDS inside were capped again at `--rv-measure` (68ch = 654px) in a
	card 794px wide, which is the ~105px of dead space down the right the
	operator screenshotted at 1780. That one goes.

	THE FIRST CUT TOOK THE CARD FULL WIDTH TOO and laid the fields out in
	three columns across it. It is reverted whole. What it bought was the
	height -- 444 to 320 for a guest, ~306 to 198 for a signed-in operator,
	against a review card 147 -- and that is the trade if it is ever wanted
	back: **the textarea cannot be both the full width of this card and
	beside the rating.** Half a row leaves a stacked form nowhere to go but
	down. It is in git, one block.

	WHAT IS LEFT IS THE WIDTH FIX ALONE: every field now fills the card, so
	the textarea measures the card inner width rather than stopping 105px
	short of it.
*/
.sf-rv #review_form_wrapper .comment-form,
.sf-rv #review_form_wrapper .comment-form-rating{ max-width: none; }

/*
	AND IT IS SHORTER (operator, 2026-11-18: "Shorten it", with the card
	still one column wide and its fields still filling it).

	THE PAIRS ARE WHAT DO IT, not smaller fields. Nothing here shrinks the
	textarea: it is the one control a reviewer types into, and 72px is
	already two lines. Two rows are folded into one instead --

	    the card heading  <->  the rating      (both forms)
	    the cookie line   <->  the submit      (a guest's form only)

	-- which is 44 and 36 of a form that was 405 and 267. The heading is
	moved into the form by pdp-reviews.js for the first pair; the note on it
	there says why it is the heading that moves and never the rating.

	MEASURED AT 1780, the card 794 wide either way:

	                          before   after
	    logged out              445     338
	    logged in (operator)    307     228
	    a review card           147     147

	EVERY ITEM IS PLACED EXPLICITLY, row and column. Auto-placement is
	sparse and walks forward only, so it cannot put the rating back up on
	the heading's row -- and the guest-only fields would shift every row
	below them when they exist. Explicit placement costs nothing when an
	item is absent: `row-gap` is `normal` here (= 0) and the space between
	rows is each item's own margin, so an empty track is 0 tall and brings
	no gap with it. That is what lets one set of rules serve both forms.

	BELOW 700px NONE OF THIS APPLIES. The pairs need about 400px of measure
	-- the heading is ~134 and the rating ~250 -- and a phone card is 318
	inside. It stacks there, as it did.
*/
@media (min-width: 700px){
	/* the heading, now the form's first child, and the rating beside it */
	.sf-rv #review_form_wrapper form#commentform > .comment-reply-title{
		grid-column: 1;
		grid-row: 1;
		margin: 0;
		align-self: center;
	}
	.sf-rv #review_form_wrapper form#commentform > .comment-form-rating{
		grid-column: 2;
		grid-row: 1;
		margin: 0;
		justify-content: flex-end;
	}

	.sf-rv #review_form_wrapper form#commentform > .comment-notes{
		grid-column: 1 / -1;
		grid-row: 2;
	}
	.sf-rv #review_form_wrapper form#commentform > .comment-form-comment{
		grid-column: 1 / -1;
		grid-row: 3;
	}
	.sf-rv #review_form_wrapper form#commentform > .comment-form-author{
		grid-column: 1;
		grid-row: 4;
	}
	.sf-rv #review_form_wrapper form#commentform > .comment-form-email{
		grid-column: 2;
		grid-row: 4;
	}

	/* the consent line and the button close the card on one row */
	.sf-rv #review_form_wrapper form#commentform > .comment-form-cookies-consent{
		grid-column: 1;
		grid-row: 5;
		align-self: center;
		margin: 0;
	}
	.sf-rv #review_form_wrapper form#commentform > .form-submit{
		grid-column: 2;
		grid-row: 5;
		align-self: center;
		margin: 0;
	}

	/* 10px between rows was the WooCommerce default coming through */
	.sf-rv #review_form_wrapper form#commentform > *{ margin-bottom: 8px; }
	.sf-rv #review_form_wrapper form#commentform > .comment-form-cookies-consent,
	.sf-rv #review_form_wrapper form#commentform > .form-submit{ margin-bottom: 0; }
}

/*
	THE RATING STARS ARE THE ACCENT, NOT WHITE (operator, 2026-11-18: "why
	not pink , why must white ?").

	NOTHING HAD EVER CHOSEN WHITE. No rule on this site styles `p.stars` at
	all -- the glyphs were taking `color` by inheritance from the card's body
	text, five ancestors up, and `rgb(242,242,244)` is just `--sp-text`
	arriving by default. Every OTHER rating on the product page is already
	magenta: the rail's stars (`--sp-accent` in single-product.css), the
	strip's average and each review card's row. The form was the one that
	had been missed.

	THE FILLED/EMPTY SIGNAL IS THE GLYPH, NOT THE COLOUR, which is what makes
	one declaration safe here. WooCommerce draws this control as five <a>s
	with an icon-font `::before`, and swaps the CHARACTER for the state:

	    e021   outline   -- the rest state, and every star past the one
	                         hovered or chosen
	    e020   solid     -- `p.stars:hover a`, and `.selected a:not(.active)`

	So magenta outlines at rest and magenta solids once picked. Colouring
	them cannot make the control read as pre-filled, which is the thing to
	check before recolouring a rating.

	:hover AND :focus ARE PINNED TO THE SAME MAGENTA ON PURPOSE. These are
	`<a href="#">`, so the site's own link-hover colour reaches them -- which
	is why the operator's screenshot showed four white stars and the one
	under the cursor pink. Left alone, the hovered star would still be a
	different shade from the four beside it.
*/
.sf-rv #review_form_wrapper .comment-form-rating p.stars a,
.sf-rv #review_form_wrapper .comment-form-rating p.stars a:hover,
.sf-rv #review_form_wrapper .comment-form-rating p.stars a:focus{
	color: var(--sp-accent, #ec1e79);
}

/*
	THE STARS SIT ON THE LABEL'S LINE (operator, 2026-11-18: "i want same
	row", with the rating row cropped).

	THEY WERE ALREADY IN ONE FLEX ROW -- that is not what was wrong. The row
	is `align-items: center` and the LABEL was centred correctly; the stars
	were 5px high of centre, which reads as the label sitting low beside
	them. Measured: label box 16px tall centred on 359, stars box 34px tall
	centred on 354, in a row 44 tall.

	34px FOR FIVE 24px GLYPHS IS BASELINE LEADING, NOT THE STARS.
	WooCommerce draws each star as an `inline-block` of 1em, so `p.stars` is
	a LINE BOX: its height is the glyphs plus the strut's descender space,
	and an inline-block sits on the baseline rather than filling the box. No
	amount of `align-items` on the parent fixes a child whose own box is
	taller than its content.

	Making `p.stars` a flex row takes the box to exactly the 24px of the
	stars, and the row then centres it on the label for free. **The 3px gap
	is not decoration**: WooCommerce separates the five <a>s with whitespace
	in the markup, which flex discards, so without it the stars would close
	up by about 3px each and the control would change shape.

	The sibling selectors WooCommerce fills the stars with (`a:hover ~ a`)
	do not care about display, so the hover and selected states are
	untouched.
*/
/*
	AND IT NEEDS TWO IDS. `margin: 0` was already set on this element by a
	(1,4,1) rule above and was LOSING: WooCommerce ships
	`#review_form #respond p{ margin: 0 0 10px }` -- **two ids** -- so the
	stars kept a 10px bottom margin, and `align-items: center` centres the
	MARGIN box, which is what put them 5px high. That is the whole of the
	offset; the flex box above only made it visible by taking the box down
	to 24px. single-product.css says the same thing about this corner of the
	page: its review-form section is id-heavy, so match the ids rather than
	piling on classes.
*/
.sf-rv #review_form #respond p.stars{
	display: flex;
	align-items: center;
	gap: 3px;
	line-height: 1;
	margin: 0;
}

/*
	THE STRIP'S BUTTON IS AS WIDE AS ITS WORDS (operator: "its like not nice
	if the button is too width").

	IT WAS NOT THE BUTTON'S WIDTH, IT WAS THE TRACK'S. The strip is a
	three-column grid -- score, bars, button -- and the last column is
	`auto`, so it absorbs everything the first two leave: 461px at 1780. A
	grid item stretches to its track by default, so the button filled it.
	Measured 461 wide for 14px of label.

	`justify-self: end` RATHER THAN A WIDTH. The button shrinks to its own
	padding and parks on the strip's right edge, which is the card's edge --
	so it lines up with the bars' counts above it and needs no number that
	would have to be re-pitched when the label changes. Measured after: 161
	wide, right edge on the strip's.

	THE PHONE KEEPS THE FULL-WIDTH BUTTON. Below 760px the strip is stacked
	and `.sf-rv .rv-summary .sf-rv__btn` is `width: 100%` -- a full-width tap
	target is right there, and this rule is inside the same breakpoint that
	turns it off.
*/
@media (min-width: 760px){
	.sf-rv .rv-summary .sf-rv__btn{ justify-self: end; }
}

/*
	ONE BUTTON STYLE FOR THE BAND, AND NO PINK ON A FIELD (operator,
	2026-11-18: "remove focus border pink and remove border pink .. and for
	the button submit i want you used color #ec1e79 and border radius is 12px
	.. then for write a review button text i want uppercase , and please match
	the font style with all the button").

	THE THREE BUTTONS ON THIS PAGE DISAGREED ON SIX THINGS. Measured live:

	| | family | size | weight | tracking | case | radius |
	|---|---|---|---|---|---|---|
	| Add to cart (the rail) | Chakra Petch | 12 | 500 | .1em | upper | 60px |
	| Submit | Chakra Petch | 10 | 500 | .1em | upper | **2px** |
	| Write a review | **Archivo** | 14 | 600 | .01em | **mixed** | 12px |

	ADD TO CART IS THE ONE TO MATCH -- it is the page's primary button and
	the other two are the strays. So both band buttons take its type exactly:
	Chakra Petch 500 / 12px / .1em / uppercase. **Only its radius is not
	copied**: 60px is the rail's own pill, and the operator asked for 12 here,
	which is the radius this band's cards, the strip and the form card all
	carry.

	THE SUBMIT WAS 2px BECAUSE OF `--sp-radius` AGAIN. single-product.css
	declares it as 2px for the whole product page, so `border-radius:
	var(--sp-radius)` reads as a house value and paints a square corner --
	the same trap the write button's `var(--sp-radius, 12px)` fell into
	earlier today. A literal 12 here.

	BOTH ARE SIZED, NOT PADDED, so they cannot drift apart when a label
	changes: 44px tall, inline-flex and centred. The write button was 42
	from its padding alone.
*/
.sf-rv .sf-rv__btn,
.sf-rv #review_form #respond .submit{
	display: inline-flex;
	align-items: center;
	justify-content: center;
	height: 44px;
	padding: 0 24px;
	border: 0;
	border-radius: 12px;
	background: var(--sp-accent, #ec1e79);
	color: #fff;
	font-family: var(--sp-tech, "Chakra Petch", sans-serif);
	font-size: 12px;
	font-weight: 500;
	letter-spacing: .1em;
	text-transform: uppercase;
	cursor: pointer;
}

/*
	NO PINK ON A FIELD, FOCUSED OR NOT.

	single-product.css rings every review input and the textarea with
	`outline: 2px solid var(--sp-accent)` on focus, and the write button
	focuses the textarea the moment the form opens -- so the card's first
	frame is a magenta box, which is what the operator screenshotted. The
	ring is gone and the field's own hairline brightens instead, from .16 to
	.45 of the ink.

	IT IS NOT 'NO FOCUS STATE', AND IT MUST NOT BECOME ONE. Someone filling
	this form on a keyboard needs to see which field they are in; the edge
	brightening IS the indicator, and it is the quietest one that still says
	so. If it ever reads as too quiet, raise the alpha -- do not reach back
	for a coloured ring.

	TWO IDS, because the rule it supersedes is `.sf-pdp__editorial
	#review_form input:focus` at (1,2,1). This corner of the page is id-heavy
	throughout.
*/
.sf-rv #review_form #respond input:focus,
.sf-rv #review_form #respond textarea:focus{
	outline: none;
	border-color: rgba(242, 242, 244, .45);
}

/*
	TWO RATINGS IN THE RAIL, AND ONLY ONE OF THEM IS OURS (operator,
	2026-11-18: "why have 2 section review ?").

	The product template already carries WooCommerce's own
	`woocommerce/product-rating` block ABOVE the title -- stars plus
	"(2 customer reviews)" -- and the reviews-band pass then injected
	`.sf-rv-rail` UNDER the title from pdp-reviews.js without noticing it.
	Two ratings, 60px apart, saying the same thing.

	OURS IS THE ONE KEPT: it prints the average as a NUMBER (3.5, which the
	block only carries in its aria text), it sits under the title where the
	price follows it, and its link goes to the band's own `#sf-reviews`.

	HIDDEN WITH `:has()`, NOT FLATLY. The block is server-rendered and ours
	is injected by script, so a flat `display: none` would leave a product
	page with NO rating at all the day that script fails to run. This hides
	the block only once ours is actually in the rail; a browser without
	`:has()` keeps both, which is the right way round for a fallback.

	TO SWAP THEM instead -- keep the template block and drop ours -- delete
	the `railLine()` call in pdp-reviews.js rather than inverting this rule:
	the block is the robust one, and the only thing it loses is the number.
*/
.sf-pdp__rail:has(.sf-rv-rail) .wp-block-woocommerce-product-rating{
	display: none;
}

/*
	AIR UNDER THE TITLE (operator, 2026-11-18: "for review please added gap
	under the title"). The rail line sat hard against the product title --
	it is the title's own `margin-bottom: 0` that puts it there, so the gap
	belongs on this element rather than on the heading, which the price
	block below also measures from.
*/
/*
	20, UP FROM 10 (operator, 2026-11-19: of the title / rating / price
	block, "not nice" -- the spacing being one of the three things named).
	Measured down the rail: title -> this line 10px, this line -> price
	20, price -> button 24. The first gap was the one out of step, so the
	line read as part of the heading rather than as its own fact.

	20 rather than splitting the difference, because adjacent margins
	collapse: the price block carries 19.2px of its own, so the gap BELOW
	this line is 20 whatever is set here. Matching it above gives
	20 / 20 / 24 down the block.
*/
.sf-pdp__rail .sf-rv-rail{
	margin-top: 20px;
}

/*
	**THE WHOLE RATING LINE IS THIS COMPONENT'S, AND THAT IS WHY THESE
	RULES MOVED HERE.** They were written in pdp-rail.css first, and that
	file loads BEFORE this one in `superfly_pdp_components_assets()` --
	so an identical (0,2,0) selector there lost to the rule above on
	source order and computed 10px with everything else correct. The link
	rules below had no competing rule and did work, but half a component
	in another file is how the next one of these starts.
*/

/*
	AND THE REVIEW LINK WAS THE SECOND LOUDEST THING ON THE PAGE. It is
	Archivo 14px regular -- the same size and weight as the body copy --
	but UNDERLINED, and nothing else in the rail is. On a product with no
	reviews yet, "Be the first to review" was competing with the name
	twenty pixels above it.

	It keeps the underline on hover, so it still reads as a link when
	someone goes looking for it. Not scoped to a width: it is wrong at
	every size.
*/
.sf-pdp__rail .sf-rv-rail a {
	text-decoration: none;
	color: var(--sp-muted, #9a9a9f);
}

.sf-pdp__rail .sf-rv-rail a:hover,
.sf-pdp__rail .sf-rv-rail a:focus-visible {
	text-decoration: underline;
	color: var(--sp-text, #f2f2f4);
}

/* ------------------------------------------------------------------ */
/*  The invitation card is set on the buy rail's scale                 */
/* ------------------------------------------------------------------ */
/*
	Operator, 2026-11-19, with the empty-state card on screen and the buy
	rail's type freshly listed: "i want same font size like all of this".

	MEASURED SIDE BY SIDE, the card had drifted from the rail in three
	places and matched it in two:

	    rail body        Archivo 14px w400, .017em, muted
	    card sentence    Archivo 15px w400, 0       <- size AND tracking
	    card question    Archivo 14px w400, 0       <- tracking
	    rail label FITS  Chakra Petch 11px w600, .145em, uppercase
	    card FIT/FEEL    Chakra Petch 11px w700, .14em   <- weight
	    rail button      Chakra Petch 12px w500, .1em, uppercase
	    card button      the same -- already right

	So the card is now the rail's own scale: one reading size, one label
	weight, and the same tracking on anything set as a sentence.

	**THE HEADING IS LEFT ALONE AND THAT IS A JUDGEMENT, NOT AN
	OVERSIGHT.** `.rv-invite__lead` is Archivo Black 20px -- the same FACE
	as the product name, which is the rail's only other use of it, but
	there is no 20px equivalent over there to match it to: the rail's
	headings are 12px Chakra Petch labels, and setting a sentence like
	"Be the first to rate this part." in a tracked-out 12px label would be
	wrong. It is a card heading, not a page heading, so it is smaller than
	the product name and larger than everything around it.
*/
.sf-rv .rv-invite__sub {
	font-size: 14px;
	letter-spacing: .017em;
}

.sf-rv .rv-prompts__v {
	letter-spacing: .017em;
}

/*
	600, down from 700. The size and the tracking already matched the
	rail's FITS label to within a hundredth of an em; only the weight was
	out, which is why this reads as nearly-right rather than wrong.
*/
.sf-rv .rv-prompts__k {
	font-weight: 600;
}
