FAQ measure

faq-ledger hangs topic labels in a margin against a list. faq-list puts the ask in a header column against a compact list. faq-cards is a wall of bordered boxes with nothing collapsed. faq-spotlight promotes one question to display size and packs the remaining eight into a grid. All four divide the band. faq-measure is the answer to a different question, which is what to do when there is nothing to put beside the questions and the page is a support page rather than a sales page. Take it when the FAQ is the whole page.

• core/details is core, and it is safe at the 6.6 floor. The block landed in WordPress 6.3 and its save() output is unchanged across the matrix. The name attribute that powers exclusive accordions arrived later and is not used here.
• The indent is padding, not margin. core/paragraph supports only top and bottom margins, so a margin-left would be an attribute the block's own save() never writes and the buyer's editor would mark the block invalid the first time it is opened. The step is padding-left instead, which is fully supported and lands on the same pixels.
• The indent closes itself on a phone. It is clamp(0rem, 12vw - 3rem, 10rem), so it is 120px on a wide desktop, about 50px at 820, and exactly zero below roughly 480px, where an indent would be stealing a seventh of the measure from an answer that has none to spare.
• The measure is bounded by the row, not by the viewport. The answer's padding-right: max(0rem, 100% - 36rem) resolves its percentage against the row's own width, so the answer is 36rem wide wherever the row is wider than that and full width wherever it is not. With the indent taken off as well, a 1240px band gives about 68 characters and an 820px one about 77. It was 46rem until the measure was rendered and counted: the indent shrinks faster than the band does, so the widest measure is at 820 and not at 1280, and the answers ran to 100 characters there while reading fine on the desktop they were authored on.
• A question must hold ONE line at 390. The line-height: max(45px, 1.15em) that makes a closed row a 44px tap target applies per line, so a question that wraps on a phone opens a 45px gap inside itself with nothing to flag it. The questions floor at 21px, which puts the budget at about 28 characters; the longest here is 27. Fix a long question by shortening the question, never by loosening the line box.
• The rules are core/separator blocks carrying is-style-wide. Without that class Twenty Twenty-Four narrows a separator to a centred 100px stub, which is a full-width rule that silently is not one.
• The header holds its own measure with a nested constrained group, not with a padding-right on a direct child of the band. The padding trick puts the block's left edge in the wrong place inside a constrained layout, and because the width still comes out right, nothing flags it.
• The first question ships open (showContent: true). A section whose every row is shut shows a visitor nothing about what is inside it, and shows you nothing in a preview either.
• The disclosure marker is the browser's. It cannot be restyled from block attributes, and CSS that no block attribute can express lives in the companion plugin rather than in a pattern, so the triangle stays.

• Open measure. Every row ships open. One idea moves and it is the composition: with all seven answers visible the step repeats down the whole section and the page reads as a document, which is what a support page wants and what a sales page does not. Colours, sizes, indent and copy are identical to the base.

Every pair is your contrast on your base, in the base and in Open measure alike, which is the pair your theme already ships body copy on. The headline and the questions are large text (21px and above at every width) and are claimed at 3:1. The eyebrow and the answers are body text and are held to 4.5:1. The rules are structural marks with no colour of their own and carry no text. Measured per theme against the resolved values, not the authored chains.