/* Every value here is a token from brand/design-system.md.
   A colour that is not in that file is a colour nobody approved. */
:root{
  --ground:#1C043D; --ground-lo:#0C0120; --white:#FFFFFF; --ink:#1A1726;
  --accent:#A991EE; --accent-ink:#64499F; --fill:#573B90; --fill-dark:#937BD6;
  --grey-dark:#A09EAB; --grey-lite:#5A5764;
  --s1:4px; --s2:8px; --s3:16px; --s4:24px; --s5:40px; --s6:64px; --s7:104px;
  /* THE SCALE IS WHY THE PAGE LOOKED MONOLITHIC. Every step used to be 1.25x
     the last, so a headline was only a little louder than a paragraph and no
     block ever announced itself. The steps below open up at the top and stay
     put at the bottom: body text is untouched, display sizes grow, and the
     four largest are fluid so a phone is not shouted at. */
  /* THE FLOORS ARE SET FROM THE SMALL END NOW, AND THE ARITHMETIC IS WHY.
     Every display size used to bottom out on its own minimum long before a
     phone got narrow: 5.6vw at 320px is 18px and the floor was 34px, so a
     320px phone was handed exactly the same headline as a 600px one and the
     scale did nothing at all across the whole phone range.
     Each step below is a straight line through two measured points, 320px and
     1280px, written the way CSS can express one: font = intercept + slope x vw,
     fenced at both ends. slope = (max - min) / (1280 - 320), and the intercept
     is min - slope x 320, so the line passes through the small end exactly.
         --xxl  27px at 320  ->  58px at 1280   slope 31/960 = 3.2292vw
         --xl   22px at 320  ->  40px at 1280   slope 18/960 = 1.8750vw
         --lg   18px at 320  ->  28px at 1280   slope 10/960 = 1.0417vw
         --md   17px at 320  ->  20px at 1280   slope  3/960 = 0.3125vw
     Body stays 16px at every width. It is the one size that must not shrink.
     THE 320px COLUMN IS 272px WIDE, which is what picked those floors: at 27px
     a Hebrew headline fits about 20 characters a line there, so the longest
     one on the site lands in 3 lines instead of 4 and the shortest - the
     Injury headline - stops wrapping at all. */
  --xs:14px; --sm:16px;
  /* 🔴 THE PHONE END OF THE SCALE WAS REBUILT ON 22 SEPTEMBER, AND THE
     DESKTOP END IS UNTOUCHED. Every top value below is the one that was there;
     only the 320px floors move, so nothing changes at 1280 or above.
     WHAT WAS WRONG. Rendered at 390px the site used TEN type sizes and SIX of
     the nine steps between them were under 1.10 - differences nobody can see,
     maintained by ten separate declarations. The middle of the ladder did
     nothing at all: a lead paragraph was 1.2px bigger than body text (17.22
     against 16) and a card heading was 2.7px bigger than the text inside the
     card (18.73 against 16). Three display sizes sat inside 1.15 of each other
     and three body sizes inside 1.09.
     It was a scale built for a 1280px screen and squeezed into a 342px column
     without being rebuilt for it. The locked ratio is 1.25.
     THE FLOORS NOW, AND THE ARITHMETIC. Each is a straight line through two
     measured points, 320px and 1280px: slope = (max - min) / 960, intercept =
     min - slope x 320.
         --md   19px at 320  ->  20px at 1280   slope  1/960 = 0.10417vw
         --lg   22.5        ->  28              slope 5.5/960 = 0.57292vw
         --xl   27          ->  40              slope  13/960 = 1.35417vw
         --xxl  30          ->  58              slope  28/960 = 2.91667vw
     The top step's floor is 30 and not 32, and one measurement set it: the
     Injury headline is 17 characters, it sits in a 240px column inside its own
     card at 320px, and check-mobile allows a 17-character heading exactly one
     line. At 32px it took two.
     At 390 that renders 14 / 16 / 19.1 / 22.9 / 28.0 / 32.0 - SIX sizes where
     there were ten. At 320 it is 14 / 16 / 19 / 22.5 / 27 / 30. */
  --md:clamp(19px, calc(18.67px + 0.10417vw), 20px);
  --lg:clamp(22.5px, calc(20.67px + 0.57292vw), 28px);
  --xl:clamp(27px, calc(22.67px + 1.35417vw), 40px);
  --xxl:clamp(30px, calc(20.67px + 2.91667vw), 58px);
  /* THE READING MEASURE, IN PIXELS AND NOT IN ch, BECAUSE ch LIES IN HEBREW.
     One ch is the width of the digit zero, and Hebrew letters are far wider
     than English ones relative to it: measured on this site at 16px, the same
     568px column holds 72 Hebrew characters and 93 English ones. So a single
     66ch cap gave Hebrew a comfortable 68 and English 93 - a third past the
     75 where the eye starts losing its place coming back to the next line.
     The two numbers below are the WORST paragraph on the site in each script,
     not an average, because an average passes while one page still fails:
         Hebrew   the Injury page ran 81 characters a line in a 512px column,
                  so the column comes down to 464px and the same text runs 73
         English  the Injury page ran 73 in a 448px column, which already fits
     Both are held from the top only. Below about 700px the screen is narrower
     than the cap, the cap stops applying, and a phone simply gets what fits. */
  --measure:29rem;
}
:root[lang="en"]{--measure:28rem}
/* THE WIDTH THE OPENING BLOCK'S MARK IS ALLOWED, AND WHY IT IS DECLARED RATHER
   THAN MEASURED. The two flanks of that row have to be EQUAL or the words stop
   sitting on the page's centre, and a `1fr` track is only equal to its twin
   while neither of them has a minimum bigger than its share. The Hebrew mark is
   the bird and the name at about 148px; the English one is the full lockup and
   is twice that, and at 1280 it overflowed its own flank by 108px and pushed
   the page sideways on every English screen. A declared reserve is equal by
   construction and the artwork is capped to it. */
:root{--lede-flank:9.5rem}
:root[lang="en"]{--lede-flank:15rem}
*{box-sizing:border-box}
body{
  margin:0; background:var(--white); color:var(--ink); overflow-x:clip;
  /* One face carries everything. Decision 0035: Frank Ruhl Libre is the
     presentation page's chrome, not brand typography, and it had leaked in
     here on the wordmark and every h1. */
  font-family:"Assistant",system-ui,sans-serif; font-size:var(--sm); line-height:1.65;
}
/* Logical properties only. `dir` decides what start and end mean, and every
   later page inherits whatever is set here. */
.skip{position:absolute;inset-inline-start:-9999px}
.skip:focus{inset-inline-start:var(--s3);top:var(--s3);background:var(--ink);
   color:var(--white);padding:var(--s2) var(--s3);z-index:9;border-radius:8px;
   outline:2px solid var(--accent);outline-offset:2px}
/* THE HEADER IS LIGHT, AS ELEM'S IS, AND THE SEAM IS SOLVED A SECOND WAY.
   The complaint was that the navigation sits ON the hero rather than above it.
   Nothing overlapped: the header was white, the top of the Home photograph is
   white studio background, and two whites with a hairline between them read as
   one surface. A hairline between two whites is invisible; three pixels of the
   brand fill along the bottom of this bar is not, and it costs no height. */
.hd{display:flex;align-items:center;justify-content:space-between;gap:var(--s3) var(--s4);
    flex-wrap:wrap;background:var(--white);color:var(--ink);
    border-block-end:3px solid var(--fill);
    /* Wider than the 820px reading column on purpose. At 820 the brand, five
       menu items and the language link did not fit on one line and the link
       dropped to a second row, which made the band look accidental. */
    padding:var(--s3) max(var(--s4), calc(50vw - 560px))}
/* min-width:0 on both, or the flex default (min-width:auto) refuses to let the
   descriptor wrap and the header runs off the side of a 360px phone. The
   English descriptor is the long one: it is what overflows first. */
/* No gap between a bird and a name any more: the lockup file holds both, with
   the overlap the artwork actually has. The descriptor sits under it. */
/* 🔴 THE MARK IN THE BAR IS PURPLE, Admin 15 September. The lockup is drawn in
   currentColor, so the colour of this link IS the colour of the bird and the
   name. `ground` is the deep brand purple and measures 18.52:1 on this white,
   which is the same colour the hero and the footer already give it - the bar
   was the one place it stood in ink. */
.brand{display:flex;flex-direction:column;align-items:flex-start;gap:var(--s1);
       text-decoration:none;color:var(--ground);min-width:0;min-height:44px}
/* 🔴 BALANCED, AND ONE LINE ON A DESKTOP, 22 September.
   At 1280 the English descriptor wrapped to two lines inside a 286px brand
   column and took the whole bar from 90px to 107px, so an English page sat
   17px lower than its Hebrew twin on every screen of the site. It misses by a
   few pixels, so it is held on one line above 64rem where there is room.
   On a phone it must wrap - there is no room - and `balance` is what stops it
   breaking as "...for post-" / "trauma", a hyphenated compound split across
   two lines with one word alone on the second. */
.brand-d{color:var(--grey-lite);font-size:var(--xs);line-height:1.2;
         text-wrap:balance}
@media (min-width:64rem){.brand-d{white-space:nowrap;text-wrap:auto}}
/* 🔴 40px ABOVE 64rem, 22 September: the masthead carried the smallest mark
   on the site (34px, and 26 below the breakpoint) while the footer carried the
   largest at 40. Five mark sizes are in use; these two are the pair that a
   reader compares, and they were the wrong way round. */
.brand svg{height:34px;width:auto;max-width:100%;flex:none}
@media (min-width:64rem){.brand svg{height:40px}}
/* No mirror rule. The English lockup file already has the bird flying right
   (decision 0036), so turning it again here would fly it backwards. */

/* EXPERIENCE.md sets a 44px minimum for anything you tap. A link the height of
   its own text is a link a thumb misses, and the language switch is the one
   people reach for first. */
/* 44px in BOTH directions. Height alone left "בית" a narrow sliver, and a thumb
   misses a target that is tall and thin just as easily as a small one.
   Weight 400: design-system.md gives 600 to the tagline and 400 to interface
   words, and a menu is interface. */
/* 🔴 600 RATHER THAN 400, AND IT IS A DEPARTURE FROM A LOCKED DOCUMENT.
   design-system.md is locked and gives `Body, UI, labels: Assistant 400`, with
   600 reserved for the tagline. Admin asked on 15 September for a bolder bar.
   The weight is one the system already owns, so nothing new is introduced; what
   changes is which role gets it. Recorded as decision 0053 so the foundation
   document and the site do not quietly disagree, and so the next person reading
   `400` in the locked file knows why the bar does not match it.
   THE SIZE IS FIXED AT --sm RATHER THAN INHERITED. The bar is interface and
   does not grow with the page's reading size: at --md the four Hebrew links
   plus the action ran past the row on a 1024px laptop. */
nav a,.nav-go{text-decoration:none}
/* NO UNDERLINE IN THE BAR, AND IT IS NOT A STYLE PREFERENCE THAT WEAKENS
   ANYTHING. An underline exists to mark a link inside RUNNING TEXT, where there
   is nothing else to tell a link from a word. In a navigation bar every item is
   a link and position already says so, which is why WCAG's own technique for
   identifying links by more than colour is scoped to text blocks. Six underlined
   items in a row read as six mistakes.
   THE CURRENT PAGE STILL HAS ITS RULE, in ink and three pixels of brand purple,
   and focus still draws a visible outline. Nothing that was carrying meaning has
   been taken away. */
nav a{color:var(--accent-ink);font-weight:600;font-size:var(--sm);
      display:inline-flex;align-items:center;
      justify-content:center;min-height:44px;min-width:44px;padding-inline:var(--s2)}
.nv ul{display:flex;flex-wrap:wrap;gap:var(--s2) var(--s4);list-style:none;margin:0;padding:0}
/* The page you are on is named by aria-current for a screen reader; this is the
   same fact said in ink, for everyone else. accentInk and not accent: the
   design system gives accent to dark grounds only, and this line sits on white,
   where accent has no recorded ratio. A marker nobody can see is not a marker. */
/* THE CURRENT PAGE, IN INK WITH A SOLID PURPLE RULE UNDER IT. Three pixels and
   not two: the bar's own bottom edge is three, and a marker thinner than the
   border it sits above reads as a hairline rather than a statement. */
/* 🔴 2px AND CLOSER TO THE WORD, 22 September. At 3px it was the same weight
   as the bar's own bottom edge and sat 23px above it, so the page you are on
   was marked by what read as one rule drawn twice. Thinner than the band's
   edge and tucked under the word, it reads as a marker on a word rather than
   as a second border on the bar. */
.nv a[aria-current="page"]{color:var(--ink);text-decoration:none;
   padding-block-end:var(--s2);
   border-block-end:2px solid var(--fill)}
/* CALM MEANS NOTHING JUMPS. The hover is a ground behind the word rather than a
   colour change on it, so the row does not flicker as a pointer crosses it, and
   the word itself never moves. */
.nv a:hover{background:color-mix(in srgb, var(--accent) 14%, transparent);
   border-radius:8px}
/* THE LAST ITEM IS THE ACTION, and it is the one thing ELEM's bar does that we
   can copy outright. Theirs is a donate button; ours cannot be, because no
   donate button, bank detail, giving link or QR code ships in version 1. So the
   action is the page that holds both doors instead.
   fillDark carries groundLo rather than white: on this pale purple, white
   measures about 2.7:1 and dark ink measures well past the bar. The pill
   against the band behind it is 4.9:1, past the 3:1 a control needs to be seen
   as a control at all. */
/* 🔴 THE ACTION IS ITS OWN ELEMENT NOW, NOT `li:last-child`. It used to be the
   fifth item in the list of pages, styled by position; Admin moved it out of
   the list on 15 September. A selector meaning "the last one happens to be the
   button" breaks the moment a page is added, and it also told a screen reader
   that the call to action was a page like the other four.
   THE ORDER ON SCREEN IS THE DOM ORDER, so the action finishes the row in both
   languages with no physical left or right written anywhere.
   `fill` carries white at 8.63:1. The pill against the white band behind it is
   4.9:1, past the 3:1 a control needs to be seen as a control at all. */
.nav-go{display:inline-flex;align-items:center;justify-content:center;
   min-height:44px;padding-inline:var(--s5);flex:none;
   background:var(--fill);color:var(--white);font-weight:700;font-size:var(--sm);
   border-radius:999px;text-decoration:none}
.nav-go:hover{background:var(--ground)}
/* 🔴 THE ACTION KEEPS ITS COLOUR ON ITS OWN PAGE. Admin, 16 September: on
   /support/ it turned the deep ground purple and read as an ordinary item that
   happened to be dark. That rule was inherited from the days when this was the
   fifth link in the list of pages, where marking the current one is right - a
   page you are on is worth saying. A CALL TO ACTION IS NOT A PAGE. It is the
   same offer on every screen and it has to look identical on every screen,
   including the one it leads to.
   THE CURRENT-PAGE FACT IS NOT LOST, it is spoken instead of painted:
   `aria-current="page"` is still on the element, so a screen reader still
   announces it. Only the colour stops changing. */
.nav-go[aria-current="page"]{background:var(--fill)}
.nav-go[aria-current="page"]:hover{background:var(--ground)}
/* 🔴 THE LANGUAGE LINK IS SET LIKE THE FOUR, Admin 15 September. It was an
   outlined pill with a flag in it, which made two pill-shaped things sit side
   by side and the eye could not tell which one was the action. It inherits
   `nav a` entirely now and adds nothing, which is the point.
   The flag went with the pill: it was a picture of a country standing in for a
   language, and the link goes to English rather than to the United States. */
.lg a:hover{background:color-mix(in srgb, var(--accent) 14%, transparent);
   border-radius:8px}
/* THE FLAG IS MICRO, AND SITS WITH THE WORD RATHER THAN BESIDE IT. Admin asked
   on 16 September for a small one. 16px wide against a 16px word: any larger
   and two blocks of colour compete with the purple button next to them, which
   is the thing on this bar that is supposed to be seen first.
   THE OUTLINE IS NOT DECORATION. Both flags are mostly white, and on this white
   bar the outer edge simply disappears without it. Drawn INSIDE the box, so it
   costs no width. */
.lg a{gap:var(--s2)}
.lg svg{inline-size:16px;block-size:11.2px;flex:none;border-radius:2px;
        outline:1px solid color-mix(in srgb, var(--ink) 25%, transparent);
        outline-offset:-1px}
/* 🔴 ONE SPINE, 22 September. THIS IS THE LARGEST CHANGE IN THE FILE AND IT IS
   THE ANSWER TO "IT DOES NOT LOOK PROFESSIONAL".
   `main` used to be a narrow centred column: 512px inside a 1280px window, so
   its first letter sat 408px from the edge while the bar's logo sat at 80 and
   the hero's headline at 150. Measured going down the Hebrew home page at 1280,
   the distance from the reading edge changed ELEVEN times, and two headings on
   one page started 174px apart. Nothing on a page began where anything else
   began, and that - not colour, not type - is what read as unfinished.
   THE PAGE NOW HAS ONE RAIL AND THE SAME EXPRESSION DRAWS IT EVERYWHERE:
   the bar (line 76), the footer (213), every full-bleed band (811), the hero
   and this column. 80px at 1280, 240px at 1600, the ordinary gutter below that.
   THE MEASURE IS NOT LOST. Running text is capped at `--measure` inside the
   rail, which is what the narrow column was really for; components opt out and
   take the full rail, which is what the -150px breakouts were really for. Both
   are listed below, and the eight `margin-inline:-150px` rules that used to
   fake this are gone. */
main{max-width:none;margin:0 auto;
     padding:var(--s6) max(var(--s4), calc(50vw - 560px))}
/* The reading measure, inside the rail. A paragraph never runs the full rail;
   a card set always does. `:not([class])` is what separates a list that is
   prose from a list that is a component - `.steps`, `.kit`, `.gear` and
   `.stages` are all `ul`/`ol`/`dl`, and capping them by tag put the equipment
   grid into one column and made the Treatment page 1,013px longer. */
/* 🔴 THE CAP IS NOT BEHIND A BREAKPOINT ANY MORE, 22 September. It was gated
   at 48rem because below that the column is narrower than the cap and it can
   never bind - which is true of a phone held UPRIGHT and false of one held
   sideways. At 568x320 the rail gives a 520px column, the cap was not applying,
   and English body text ran 75 to 82 characters a line against the 75 the
   standard allows. Ungated it is a no-op on every portrait phone and it binds
   on every landscape one. */
main > section > :is(p,blockquote,figure),
main > section > :is(ul,ol,dl):not([class]),
main > section > .stages{max-width:var(--measure)}
@media (min-width:48rem){
  /* The quotation-beside-a-picture block is the one component that must NOT
     take the whole rail: its picture is square, so every pixel of extra width
     becomes a pixel of extra height. */
  main > section > .beside{max-width:820px}
}
/* A SHORT RULE ABOVE EVERY SECTION HEADING. The site had one shape - heading,
   paragraphs, heading, paragraphs - and no way to see where one idea stopped.
   This is the smallest mark that does the job: static, in an approved colour,
   decorative so it carries no contrast duty of its own, and hidden from screen
   readers because a heading already announces the boundary. */
main > section > h2::before{content:"";display:block;inline-size:48px;block-size:3px;
   background:var(--fill-dark);margin-block-end:var(--s3);border-radius:2px}
.op > h2::before{display:none}
/* A long word in either script must break rather than push the page sideways. */
h1,p{overflow-wrap:break-word}
h1{font-weight:800;font-size:var(--xxl);line-height:1.25;margin:0 0 var(--s4)}
/* ── THE FOOTER ───────────────────────────────────────────────────────────
   Admin, 8 September: the brand purple, with the mark. It was a hairline and
   six lines of grey type, which read as the end of a document rather than the
   foot of an organisation's website.
   The identity sits on the side the language reads FROM and the contact details
   on the far side, and the two swap over in English on their own: this is a
   flex row with `justify-content:space-between`, and `dir` decides which end is
   which. There is no physical left or right in these rules. */
/* 🔴 IT WAS LAID OUT AS IF IT HAD TWO COLUMNS AND IT HAS ONE, 22 September.
   The contact column only renders when `site.contact` has a value and none is
   supplied, so `justify-content:space-between` had a single child to divide a
   1600px band between: 843px of empty purple at 1280, and half the band's
   height was padding. It was also the same height on a 390px phone as on a
   1600px desktop, because nothing in it ever reflowed.
   A row of two, where the second is the registry line, uses the width the band
   actually has. When the contact details arrive the flex row takes over again
   and nothing here has to change. */
.ft{background:var(--ground);color:var(--white);border-block-start:0;
    padding:var(--s5) max(var(--s4), calc(50vw - 560px));font-size:var(--sm)}
.ft-in{display:flex;flex-wrap:wrap;gap:var(--s4) var(--s6);
       justify-content:space-between;align-items:flex-start}
.ft-id{min-width:0}
/* The last line keeps no bottom margin, or the band is 8px deeper below its
   text than above it on every page. */
.ft p{margin:0 0 var(--s2)}
.ft-id > p:last-child{margin-block-end:0}
/* 🔴 34px, NOT 40px, 22 September. The mark in the footer was BIGGER than the
   mark in the masthead (34px, and 26px below 64rem), so the brand was at its
   largest where a reader has finished and at its smallest where they arrive.
   The bar leads at 40 and the footer answers at 34. */
.ft-mark{line-height:0;margin:0 0 var(--s3)}
.ft-mark svg{height:34px;width:auto;max-width:100%}
/* The brand line is the loud one and the certificate quotation under it is
   quiet, which is the same order the header uses. accent on ground measures
   8.06:1; white on ground measures 18.52:1. */
.ft-b{color:var(--white);font-weight:700;font-size:var(--md);margin:0 0 var(--s2)}
.ft-id p:not(.ft-b){color:var(--accent)}
.ft-n{font-size:var(--xs)}
.ft-c{min-width:0}
.ft-h{font-weight:700;color:var(--white);font-size:var(--md);margin:0 0 var(--s3)}
.ft-c dl{display:grid;gap:var(--s3);margin:0}
.ft-c dt{font-size:var(--xs);color:var(--accent);margin:0 0 2px}
.ft-c dd{margin:0;color:var(--white);font-weight:600}
.ft-c a{color:var(--white);text-decoration:underline;text-underline-offset:3px;
        display:inline-flex;align-items:center;min-height:44px}
.ft a:focus-visible{outline-color:var(--accent)}
/* THE FOCUS RING, PER GROUND. accentInk is the voice on light and it measures
   1.7:1 on groundLo, so a keyboard user could not see where they were in the
   hero, the trust strip or the THERE column. Those three set their own. This is
   WCAG 2.4.11 and 1.4.11: a focus indicator has to reach 3:1 against what is
   behind it, and "behind it" changes three times on this page. */
a:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
.op a:focus-visible,
.strip a:focus-visible,
.side:first-child a:focus-visible{outline-color:var(--accent)}
/* [FR-21](https://github.com/Agency18/ram-association/blob/main/archive/planning/prds/prd-ram-association-2026-08-26/prd.md): nothing moves. There is no transition to disable, and this is here so
   that adding one later is a deliberate act rather than an oversight. */
@media (prefers-reduced-motion:reduce){*{animation:none!important;transition:none!important}}

/* ── HOME ──────────────────────────────────────────────────────────────────
   Nine sections, not a routing page. A reader who never clicks anything else
   must still have felt it, understood the problem, seen the answer and
   believed the organisation. Wireframe: archive/work-products/epic-3/issue-47-wireframes/home.md
   Every colour below is a token above, which is a token from design-system.md. */

/* HOME IS WIDER THAN THE MEASURE, AND THE MEASURE IS STILL KEPT.
   Two things on Home need width the reading measure does not give: THERE and
   HERE only read as a pair when they sit side by side, and the three governance
   cards only read as one set when they share one row.
   Review on PR #85 measured what was actually shipping: `min(76ch,860px)`
   resolved to 598px in Hebrew, so the 860px cap never applied, the third card
   fell to a second row at every desktop width, and the running text sat at 76ch
   when design-system.md locks the measure at 66. The old comment claimed the
   text was capped. It was not. A comment that describes something the file does
   not do is worse than no comment.
   So: the PAGE widens, and the TEXT is capped, which is what the old comment
   promised. Bands opt out by being listed below. */
.home main{max-width:none;min-width:0}
@media (min-width:48rem){
  /* The home page's own opt-outs. Everything here is a component rather than
     running text, so it takes the rail rather than the measure. */
  .home main > section > :is(.cards,.split,.strip,.roster,.stat-grid,.helpline,.lede){max-width:none}
  .home main > section.films > :is(ul,p){max-width:none}
  main > section > :is(.steps,.limits,.kit,.people,.gear,.doors,.signs,.form-wrap,.manifest,.flow,.pillars,.cycle){max-width:none}
}
section{margin:0 0 var(--s7)}
/* 🔴 THE SAME GAP AS EVERY OTHER SEAM, 22 September. The last section closed
   at 64px where all eight before it closed at 104, so the page met the footer
   in a hurry. The pages that end on an onward link close at 64 + `main`'s own
   padding, which is the same number; this makes all ten match. */
section:last-of-type{margin-block-end:var(--s7)}
/* 🔴 ONE GAP AND ONE LEADING, IN BOTH SCRIPTS, 22 September. English carried
   `margin-block-end:var(--s5)` and `line-height:1.2` from a language-scoped
   block at the end of the file while Hebrew kept 24px and 1.3, so the same
   heading was 52px tall in one language and 48px in the other and stood a
   different distance from its own first sentence. The locked value is 1.25 and
   neither language was on it. Both are now, once, here. */
h2{font-weight:800;font-size:var(--xl);line-height:1.25;margin:0 0 var(--s5);
   overflow-wrap:break-word;text-wrap:balance}
/* h3 HAD NO SIZE OF ITS OWN, so three headings on the Treatment page took the
   browser's default 1.17em - 18.72px, a number from no scale on this site -
   and they were the only text on the page that did not move when the scale
   changed. Every level is on the scale now. */
/* 🔴 SPACE ABOVE IT, 22 September. `margin:0 0 16px` gave a sub-heading its
   only top space from the paragraph above it - also 16px - so it sat dead
   centre between two blocks and belonged to neither. Three of them do this on
   the Treatment page alone. 40 above against 16 below is 2.5:1, which is the
   whole of what "this heading starts what follows" means typographically.
   `:first-child` keeps the first one tight to the block that opens. */
h3{font-weight:800;font-size:var(--lg);line-height:1.25;
   margin:var(--s5) 0 var(--s3);overflow-wrap:break-word}
h3:first-child{margin-block-start:0}
p{margin:0 0 var(--s3)}

/* THE OPENING. Pride first, cost second: reversing the order produces pity,
   which decision 0021 forbids. The eyebrow carries the pride, the h1 the cost. */
/* THE HERO: THE PICTURE *IS* THE SECTION, AND NOTHING IS LAID OVER IT.
   Admin asked for the purple mask gone and the words in the brand's own
   colours. The photograph allows exactly that, which the previous version did
   not know because it never opened the file. It only reasoned about the worst
   picture imaginable and then darkened this one to survive it.
   It is a studio shot - a man in a purple chair, the shadow of a fighter cast
   behind him - and its background measures, in all four corners, within two
   points of pure white on all three channels. That is white. So the SECTION is white, the photograph dissolves
   into it with no seam, and the type is the deep brand purple:
       ground     #1C043D on white   18.52:1
       accent-ink #64499F on white    7.01:1
   Both clear the 4.5:1 the standard asks with room, and neither needs a scrim.
   WHERE THE WORDS SIT IS MEASURED, NOT GUESSED. The file was sampled on a
   40x22 grid: across the whole right HALF the darkest cell is 0.49 luminance,
   which still gives the deep purple 9.50:1. Hebrew starts on the right, and the
   right of this frame is the empty half. English starts on the left, where the
   man is, so the picture is mirrored there and the subject stays off the type.
   BELOW 768px THE PICTURE CANNOT HOLD TEXT AT ALL - the man and the shadow fill
   the frame - so the words sit above it on the section's own white and the
   photograph runs full width underneath, uncropped. Same white, no seam.
   scripts/check-hero-contrast.mjs reads the pixels actually behind the actual
   rendered text, so a picture swapped in later cannot break this quietly. */
/* FULL BLEED: the picture runs to both edges of the window, not to the edges of
   the text column. `main` is a centred 820px column, so the section is pulled
   out to the window width and then padded back in by exactly half the leftover,
   which puts the first word of the hero on the same line as the first word of
   every section below it.
   body gets overflow-x:clip rather than hidden: 100vw counts the scrollbar and
   the content box does not, so the pull-out is a few pixels wider than the page
   on any machine that draws a real scrollbar. clip removes those pixels without
   making body a scroll container, which hidden would, breaking anchor jumps. */
.op{position:relative;isolation:isolate;background:var(--white);color:var(--ground);
    display:flex;flex-direction:column;
    margin-inline:calc(50% - 50vw);margin-block-start:calc(var(--s6) * -1);
    /* 🔴 THE RAIL, 22 September. This was `50vw - 410px`, a third number in a
       file that already had two, and it put the headline 258px inside the
       first paragraph of the page on Treatment and Transparency. Same
       expression as the bar, the footer, the bands and `main`. */
    padding:var(--s6) max(var(--s4), calc(50vw - 560px));overflow:hidden}
.op .hero-img{order:2;width:100%;height:auto;max-height:none;
                margin:var(--s5) 0 0;border-radius:0}
/* The eligibility line takes the DEEP purple, and check-hero-contrast is the
   reason. The pale accent is a dark-ground colour: 2.59:1 on this white. The
   mid purple accent-ink clears the white easily at 7.01:1 - and then the check
   measured it where it actually lands, on the grey of the fighter's shadow,
   and got 3.89:1. Reasoning about the section's background would never have
   found that, because the section's background is not what is behind the word.
   The deep purple holds 9.50:1 on the same pixels. */
.op .lede-scope{color:var(--ground)}
/* 🔴 AT EVERY WIDTH, 22 September. This rule lived inside the phone query, so
   on a desktop the last paragraph in a hero kept its own 24px bottom margin on
   top of the band's 104px padding: 104 above the words and 128 below them, on
   Treatment and Transparency. A band that is deeper at the foot than at the
   head reads as a band that has sagged. */
.op > :last-child{margin-block-end:0}
/* 🔴 64rem, NOT 1024px, 22 September, AND THIS ONE IS AN ACCESSIBILITY FAULT
   RATHER THAN A MATTER OF LOOKS.
   The same breakpoint was written two ways in this file: four queries counted
   CSS pixels and eight counted rem. A pixel query ignores the reader's own
   text size; a rem query follows it. At a browser default of 20px - an
   ordinary setting, not zoom - 64rem becomes 1280px while 1024px stays 1024,
   so between those two widths half the desktop rules applied and half the
   phone rules applied at the same time.
   REPRODUCED, not reasoned about: browser default 20px, window 1100px, and the
   home headline is cut off at the window edge with the donate button sliced in
   half. Hero 527px -> 440px, `.op h1` max-width 450.9 -> 293.8, section gap
   104 -> 64, all at once.
   Every query in this file is now in rem, so they move together.

   1024, NOT 768. At 768 the padding collapses to the ordinary gutter, the text
   column spans the whole window and the headline lands on the man in the chair:
   1.28:1, found by check-hero-contrast and not by looking. Below 1024 the words
   go above the picture instead, which is the arrangement that needs no scrim. */
@media (min-width:64rem){
  /* A FIFTH SHORTER, at Admin's request on 7 September, and the words 30px
     nearer the edge the language reads from. The height is content-driven
     rather than set, so it comes off the four things that make it: the block
     padding, the lockup, and the space under the lockup and the headline.
     Measured at 1280px: 649px before, 521px after, which is 19.7%. */
  /* THE SECTION TAKES THE PICTURE'S OWN SHAPE, so nothing is ever cropped.
     "The navbar is covering the hero image" was the picture being cut along its
     TOP edge: the section was 503px at 1280 and the file's own shape wants 724,
     so object-fit:cover trimmed 221px, and the trim happened right under the
     bar. Nothing overlapped - the header ends at 87px and the hero begins at
     87px, measured. A picture cut flush against a band reads as a picture the
     band is sitting on top of, which is the same complaint either way.
     With the ratio declared, cover has nothing left to crop. */
  /* SHORTER THAN THE PICTURE'S OWN SHAPE, and the picture still whole. Admin,
     7 September: the hero was too tall. Declaring the file's ratio fixed the
     cropping but bought the crop back as height - 724px at 1280.
     So the section is now DELIBERATELY WIDER than the file, and object-fit
     switches from cover to contain: the picture is limited by the height, sits
     centred, and what is left at either side is the section's own ground. On
     this photograph that ground is white and so is the studio background, so
     the seam does not exist. 613px instead of 724, and not a pixel cropped. */
  /* The ground either side of the picture is mixed a touch off pure white, to
     the two-point-darker white the studio background actually is. At #FFFFFF a
     faint vertical seam showed where the file ended. */
  /* 🔴 A FLOOR, NOT A FIXED SHAPE, AND A CLIPPED LINE IS WHY. `aspect-ratio`
     with `overflow:hidden` gave this band the picture's proportions and then
     CUT OFF anything that did not fit. When Admin's three-line body landed on
     16 September the English dedication ran 17px past the bottom edge and
     simply vanished - at 1100px and at 1280px, on a live page, with every
     check green. Nothing was measuring it.
     `min-block-size` is the same number and lets the band grow instead. The
     picture is `contain` and anchored to the bottom, so the extra height turns
     into white above it and nothing is ever cropped. scripts/check-mobile.mjs
     now refuses a hero that clips its own words. */
  .op{background:color-mix(in srgb, var(--white) 99%, var(--ink));
      /* 🔴 A CEILING, 22 September. `47.9167vw` alone has no maximum, so the
         opening grew with the window for ever: 613px at 1280, 767 at 1600,
         920 at 1920 and 1227 at 2560. Bar plus hero is 112% of a 1920x900
         screen and 146% of a 2560 one - a reader sees a photograph and a
         headline and no sign the page continues. check-mobile refuses more
         than 92% of the screen on a phone and nothing was checking a desktop.
         78vh leaves a sixth of the screen for whatever comes next, which is
         the same proportion the phone bound works out to. */
      min-block-size:min(47.9167vw, 78vh);justify-content:center;
      /* 50px nearer the reading edge again, Admin 7 September.
         AND DOWN A SECOND STEP when the dedication gained its 40px of air:
         652px against the 646px bound at 1280x800. The gap Admin asked for is
         the thing a reader sees; 32px of padding around the outside of the
         block is not, so that is what pays for it.
         THE BLOCK PADDING CAME DOWN A STEP on 16 September. With six blocks of
         words in the opening, the English hero stood at 679px against a 646px
         bound at 1280x800 - check-mobile counts the bar and the hero together
         and refuses more than 92% of the screen, because a reader who sees only
         those has no sign the page goes on. 48px of air around the block is the
         cheapest thing in it: it costs nothing a reader is reading. */
      /* 🔴 THE RAIL, 22 September. `50vw - 490px` put the h1 50px inside the
         logo at 1280 and 70px inside it at 1600 - the two largest objects on
         the first screen, on different spines. */
      padding:var(--s4) max(var(--s4), calc(50vw - 560px))}
  .op .hero-mark svg{height:clamp(42px,4.7vw,60px)}
  /* Anchored left and bottom, not centred. A wide window crops the top, which
     is empty studio white, instead of the man's feet. A tall one crops the
     right, which is the empty half, instead of the man. The English page
     mirrors the whole element afterwards, so left-anchored source still puts
     him on the far side from the words. */
  .op .hero-img{position:absolute;inset:0;width:100%;height:100%;
                  object-fit:contain;object-position:center bottom;margin:0;z-index:-1}
  /* WIDE ENOUGH THAT THE HEADLINE STAYS SHORT. At min(50%,32rem) the English
     h1 wrapped to seven lines, the section grew to 1120px, and object-fit:cover
     then cropped 35% off the picture - taking exactly the empty half the words
     were sitting in. A hero that grows taller than its picture's own aspect
     eats its own background. Wider column, slightly smaller display size in
     the hero only, and the section stays under the picture's natural height. */
  /* WIDER AGAIN, AND THE SAME ARGUMENT AS BEFORE. The note above says a hero
     that grows taller than its picture's aspect eats its own background; the
     fix then was a wider column and it is the fix now. Admin's three-line body
     put the English opening at 807px against a 646px bound at 1280x800, and
     almost all of that was WRAPPING: the headline ran three lines and each body
     line ran two. At 40rem the headline is two lines and the body lines are
     one each. The words did not get smaller and nothing was cut. */
  .op > :not(.hero-img){align-self:start;max-width:min(64%,40rem)}
  .op h1{font-size:clamp(30px,3.4vw,46px)}
  /* 🔴 THE PROMISE IS ONE LINE, AND A `ch` CAP WAS BREAKING IT INTO THREE.
     `.hero-h2` carries max-width:24ch, which is right in a narrow column and
     absurd inside a 40rem one: the English promise measured 96px where a single
     line is 35, and those 61px were most of what pushed this hero past its
     bound. The column itself is the measure up here. `ch` is the width of a
     zero and this file has been caught by it once before, in Hebrew, where it
     lies by a third. */
  /* 34rem AND NOT `none`. Lifting the 24ch cap stopped the promise wrapping to
     three lines; letting it run the full 40rem column sent its last words onto
     the man, where check-hero-contrast read them at 1.04:1 - purple on the dark
     chair. The number is the width the sentence actually needs at this size,
     with nothing to spare for the photograph. */
  /* TWO NUMBERS THAT HAVE TO AGREE, AND EACH WAS FOUND BY MEASURING.
     THE CAP KEEPS IT OFF THE MAN. At the full 40rem column the sentence's last
     words landed on the dark chair and check-hero-contrast read 1.04:1.
     THE SIZE KEEPS IT ON ONE LINE INSIDE THAT CAP. At 28px it wrapped to two
     instead, which put the hero back to 679px against a 646px bound. 26px is
     the size at which the English promise fits 34rem on a single line. The
     Hebrew sentence is shorter and was never near either edge. */
  .op .hero-h2{max-width:34rem;font-size:clamp(22px,1.9vw,26px)}
  /* 30% over the hero size on the pages that open with words alone, Admin
     7 September. With no picture behind it the headline is the whole opening. */
  .op.plain h1{font-size:clamp(39px,4.4vw,60px)}
  /* 15% over the hero size, Admin 7 September. */
  /* 15% over the last step, Admin 7 September. */
  .op.scene h1{font-size:clamp(39px,4.5vw,61px)}
  /* 🔴 THE MIRROR IS FOR A PHOTOGRAPH THE WORDS SIT ON, AND `.duo` IS NOT ONE.
     Admin, 16 September: the English pages should carry their pictures the same
     way the Hebrew ones do. Measured, and the giving page was the odd one out.
     Home and Injury lay their words OVER a full-bleed photograph, and the words
     change sides with `dir`. Flipping the picture is what keeps the man on the
     far side from them in both languages, which is the only reason this rule
     exists.
     THE GIVING PAGE IS A DIFFERENT SHAPE. Its picture is its own element in its
     own grid column, and the grid already swaps the columns over in English
     because `dir` decides which column is first. Flipping the image on top of
     that is a SECOND mirror: two soldiers carrying a stretcher had their rifles
     on the wrong shoulders, in a photograph of real people. One flip too many. */
  /* 🔴 THE HOME HERO IS NOT FLIPPED ANY MORE. Admin, 18 September: "be sure
     you serve the image as I uploaded it without any flips." The mirror was
     put here for `hero.jpg`, which is a cut-out with the man against one edge
     and nothing else in the frame, so flipping it changed only which side he
     stood on. `hero-en.jpg` is a composition: a man and the shadow of a
     fighter thrown to one side of him. Mirrored, that is a different picture
     from the one the client approved, and he noticed inside an hour.
     The Injury hero keeps the flip; it is the same kind of picture as before
     and nobody has asked for it to change. */
  html[lang="en"] .op:not(.duo) .hero-img{transform:scaleX(-1)}
  html[lang="en"] .home .op .hero-img{transform:none}
  /* THE GUTTER HAS TO BE THE PICTURE'S OWN WHITE, NOT PURE WHITE.
     `object-fit:contain` pillarboxes a picture narrower than the section, and
     the section was painting #FFFFFF behind it while both studio photographs
     are 248,251,255. At the old framing the gutters were 90px and nobody saw
     the seam; the English hero is framed taller now, so they are ~140px a side
     and the join shows as a vertical line down the page. Same colour, no join.
     Only the English home hero: it is the only one framed this way. */
  /* 🔴 ONE VALUE, BOTH LANGUAGES, AND IT IS SAMPLED FROM THE PHOTOGRAPH
     RATHER THAN CHOSEN. 22 September.
     This was behind `html[lang="en"]`, so the English band matched the studio
     white in `hero-en.jpg` exactly and had no seam, while the Hebrew band sat
     at `white 99% + ink` and drew a faint rectangle round its own picture:
     at 1280 the colour changed at x=98 and back at x=1182, which is the
     letterbox `object-fit:contain` leaves either side of the file.
     🔴 IT IS THE ONE COLOUR IN THIS FILE THAT IS NOT A LOCKED TOKEN OR A MIX
     OF THEM, and design-system.md section 5 says a colour that is not a token
     is a colour nobody approved. It cannot be mixed from the palette: the
     studio white leans BLUE (248,251,255 - green above red) and every colour
     in the palette leans purple, which pulls green down. So it is either this
     value or a visible box round the photograph.
     It is recorded here rather than added to `:root`, because it is not a
     brand colour - it is a measurement of an asset, and if the asset is ever
     replaced this number is replaced with it. ADMIN HAS TO RULE ON IT. */
  .home .op:not(.duo){background:rgb(248 251 255)}
  /* AND UNFLIPPED, THE MAN STANDS WHERE THE ENGLISH WORDS DO.
     That is the cost of not flipping, and it is arithmetic, not opinion: he
     occupies 36% to 60% of his own frame, English reads from the left, and the
     hero column runs to 40rem. Full-bleed, the headline and all three body
     lines crossed his black shirt and measured 1.00:1 - the text and what is
     behind it the same colour.
     So the picture stops being a full-bleed backdrop and becomes a band on the
     far side. 55%: the man then starts at 1 - (0.64 x 0.55) = 65% of the width,
     and the words stop at 62%. That holds at every width because both numbers
     are fractions of the same width, which is the point of writing it this way
     rather than in pixels.
     WHAT IT COSTS: the picture is smaller than it was flipped. Nothing is
     cropped - he keeps his shadow, which is the whole idea of the photograph. */
  html[lang="en"] .home .op:not(.duo) .hero-img{inset-inline-start:auto;
             inline-size:55%;object-position:right bottom}
}
/* THE SECOND HERO IS THE SAME SHAPE AND THE OPPOSITE PROBLEM.
   The Home picture is a studio cut-out on white, so the words sit straight on
   it. The Injury picture is a street: a father carrying two children, with the
   shadow of a loaded fighter on the wall beside them. It is mid-tone edge to
   edge, and it was measured before anything was drawn:
       white words on it, at worst        1.56:1
       deep purple words on it, at worst  1.90:1
   Both need 4.5:1. NO TEXT COLOUR SURVIVES THAT PICTURE BARE, so this hero
   carries a ground of its own and the words are white on it.
   THE GROUND IS A GRADIENT FROM THE BOTTOM, NOT A WASH OVER THE WHOLE FRAME.
   The wash was what Admin rejected on Home and it was right to reject: it flattens
   the photograph into a texture. Rising from the bottom, it darkens the pavement
   - the part of this frame carrying no meaning - and leaves the faces and the
   whole of the shadow untouched. The words sit in the part it darkens.
   Because the ground is guaranteed rather than borrowed from the photograph,
   this hero holds its words at EVERY width, where the Home one waits for 1024. */
/* 15% shorter, Admin 7 September: 760px to 646px at 1280. */
/* THE INJURY HERO ONLY LAYS WORDS ON THE PICTURE WHERE THERE IS ROOM.
   The picture's own shape is 1600x905, so at 360px wide it is 204px tall. A
   headline needs about 120 of those and the darkening at the bottom is worth 53,
   which is how it measured 1.94:1 - unreadable, and found by the render check
   rather than by looking at it.
   So below 1024 the picture keeps its whole self at the top and the headline
   sits under it on white, which is the same arrangement the Home hero uses at
   that width and needs no ground at all. Above it, the words go back on the
   picture. */
.op.scene{background:var(--white);color:var(--ink)}
.op.scene .hero-img{order:2;width:100%;height:auto;margin:var(--s5) 0 0}
.scene-words{padding:0;max-width:none}
@media (min-width:64rem){
  /* A CARD, AND NO BANDS. Admin, 7 September: the contain fit left black holes
     at either side, because the section was deliberately wider than the file.
     So the section takes the FILE'S OWN shape again - 1600x905 - which means
     contain and cover are the same thing and there is nothing left over to
     fill. It insets a gutter from each window edge and rounds its corners,
     which is what turns a full-bleed band into a card. */
  .op.scene{background:var(--ground-lo);color:var(--white);
            justify-content:flex-end;aspect-ratio:1600/905;min-height:0;
            /* 80% of the window rather than all of it less a gutter, which
               is 20% smaller in both directions at once. The section still
               carries the file's own ratio, so contain and cover stay the same
               thing and nothing is cropped at any size. */
            /* 🔴 THE CARD SITS ON THE RAIL, 22 September. It was inset to 80%
               of the window, which is a fifth edge on a page that already had
               four: the card's own edge landed at 128px from the window at
               1280 while the bar, the footer and every band landed at 80.
               `main` IS the rail now, so zero is the rail. The words are then
               inset by the card's own padding, the way every other card on
               this site insets its contents - a component on the rail with
               padding inside it is a structure; a component at 40vw is a
               number somebody picked. */
            margin-inline:0;
            border-radius:8px;padding:var(--s6) var(--s5)}
  /* The headline kept a 40px bottom margin on top of the card's 64px padding,
     so it floated 104px off an edge the gradient says it should sit near. */
  .op.scene .scene-words > :last-child{margin-block-end:0}
  /* Same trade as the Home hero: a wider box, contain rather than cover, 616px
     instead of 724 and the street scene entire. Here the ground either side is
     groundLo, which the gradient already covers, so it reads as the frame it is. */
  .op.scene .hero-img{order:0;position:absolute;inset:0;width:100%;height:100%;
                        object-fit:cover;margin:0;z-index:-2}
  .op.scene > :not(.hero-img){align-self:start}
  .op.scene :is(h1,h2,p){color:var(--white)}
  .op.scene::after{content:"";position:absolute;inset:0;z-index:-1;
     background:linear-gradient(to top,
       color-mix(in srgb, var(--ground-lo) 88%, transparent) 0%,
       color-mix(in srgb, var(--ground-lo) 62%, transparent) 26%,
       color-mix(in srgb, var(--ground-lo) 15%, transparent) 58%,
       color-mix(in srgb, var(--ground-lo) 15%, transparent) 100%)}
  .op.scene .scene-words{max-width:min(64%,42rem)}
}
@media (min-width:64rem){
  .op.scene .scene-words{max-width:min(64%,42rem)}
}
/* TWO COLUMNS, EDGE TO EDGE: the words on the side the language starts from,
   the picture on the other. Admin, 7 September, for the How-to-help opening.
   This is the third shape a hero can take on this site and the reason there are
   three: the Home picture is a cut-out on white and carries the words itself;
   the Injury picture is a scene and needs a ground under them; this picture is
   a close crop of hands on a stretcher, and cropping it wider to fit words on
   top would lose the hands, which are the whole photograph. Beside is the
   arrangement that keeps the picture whole AND the words on plain white, so
   nothing is laid over anything and no contrast question arises at all.
   The words sit in grid column 1, which `dir` puts on the right in Hebrew and
   the left in English, so the picture is always on the far side from the
   reading edge without a single physical left or right in this file. */
/* aspect-ratio:auto, AND THE 330px OF NOTHING THAT NEEDED IT. `.op` declares
   the Home photograph's own shape, 2400/1150, from 1024px up. This hero
   inherits that class, so on a 1920px screen the section was told to be 920px
   tall while its capped picture stopped at 590 and its words at 285: a third
   of a screen of empty white under the photograph, growing with the window.
   The picture and the words size this one, the way they already do below
   1024px. `.op.plain` opts out of the same inherited shape for the same
   reason. */
.op.duo{display:grid;grid-template-columns:1fr 1fr;gap:0;align-items:stretch;
        background:var(--white);color:var(--ink);padding:0;overflow:hidden;
        aspect-ratio:auto;min-height:min(46vh,400px);
        margin-inline:calc(50% - 50vw);margin-block-start:calc(var(--s6) * -1)}
/* A HEIGHT, RATHER THAN THE FILE'S OWN ASPECT. height:100% inside a grid row
   that sizes itself resolves to auto, so this 1202x1600 picture was setting the
   row to 852px and the section with it. Named height, 30% less, cover crop. */
/* ALL FOUR CORNERS, AND ROUNDED. Admin, 8 September. It was a cover crop in a
   named-height box, which is how a 1202x1600 picture was made to fill half a
   hero: the top and the bottom of it were simply not on the page. inline-size
   and block-size go back to auto so the file's own shape decides, a height cap
   keeps the hero from growing with it, and contain guarantees that a cap can
   never crop. Centred in its half, with a gutter, so it reads as a card resting
   in the section rather than as a panel bolted to the edge. */
.op.duo .hero-img{grid-column:2;grid-row:1;position:static;order:0;
                    inline-size:auto;block-size:auto;
                    max-block-size:520px;max-inline-size:calc(100% - var(--s5) * 2);
                    object-fit:contain;object-position:center;
                    justify-self:center;align-self:center;
                    margin-block:var(--s5);border-radius:8px}
.op.duo .duo-words{grid-column:1;grid-row:1;align-self:center;max-width:none;
                   padding-block:var(--s6);
                   padding-inline-start:max(var(--s4), calc(50vw - 560px));
                   padding-inline-end:var(--s5)}
.op.duo .duo-words > :last-child{margin-block-end:0}
/* Under 52rem there is no second column worth having: half of 52rem is 26rem,
   and a headline this size in either script needs more than that. So it stacks,
   words first, picture under them at a crop that keeps the hands. */
@media (max-width:52rem){
  .op.duo{grid-template-columns:1fr;min-height:0}
  /* 🔴 THE SMALLEST PICTURE ON THE SITE WAS THE OPENING OF THE GIVING PAGE.
     22 September: a 320px height cap and `object-fit:contain` left it 226px
     wide and centred, with 82px of white each side, on a white ground with no
     band behind it - a thumbnail where every other page has an opening. It
     takes the column, at the same crop. */
  .op.duo .hero-img{grid-column:1;grid-row:2;aspect-ratio:3/2;
                      inline-size:100%;max-inline-size:none;max-block-size:none;
                      object-fit:cover;margin-block:0 var(--s5)}
  .op.duo .duo-words{grid-column:1;grid-row:1;padding:var(--s5) var(--s4)}
}
/* A HERO WITH NO PICTURE IN IT still has to look like a hero. Treatment and
   Transparency open with words alone, and the picture rules above would have
   given them a 613px empty box shaped like a photograph. This is the brand band
   instead: the same purple as the details stripe, full width, sized by what is
   written in it. */
.op.plain{background:var(--ground);color:var(--white);aspect-ratio:auto;
          min-height:0;padding-block:var(--s6)}
.op.plain .lede{color:var(--white)}
.op.plain .lede-scope{color:var(--accent)}
@media (min-width:64rem){
  .op.plain{aspect-ratio:auto;padding-block:var(--s7)}
  .op.plain > :not(.hero-img){max-width:34rem}
}
/* NAMED .steps, NOT .stages, BECAUSE .stages WAS ALREADY TAKEN - it is the
   plain bulleted list used on the Injury and Transparency pages, and giving it
   a grid with a 19rem minimum pushed those lists 32px past the edge of a 320px
   phone. Found by check-viewport, which is the only reason it is not shipping.
   THE FOUR STAGES ARE A SEQUENCE, so they are numbered, and the number is the
   only decoration on the page that carries information. Each card names the
   stage, what it is for in one line, WHO RUNS IT, and then how it works.
   Pulling the provider onto its own line is not styling: FR-26a requires the
   person operating each stage to be stated wherever treatment is described, and
   a sentence buried mid-paragraph is a sentence a skimming reader never sees. */
.steps{list-style:none;display:grid;gap:var(--s4);padding:0;max-width:none;
        margin:var(--s5) 0 var(--s4);
        /* min() so the floor can never exceed the container: a bare 19rem
           minimum is a hard 304px, and a 320px phone has 272px to give. */
        grid-template-columns:repeat(auto-fit,minmax(min(19rem,100%),1fr))}
/* Two across, which needs more than a 66ch reading column: four cards in one
   column is a list with boxes round it, not a sequence you can see.
   🔴 THE -150px THAT USED TO BE HERE IS GONE, 22 September. It existed to pull
   a component out of a 512px column, and the column is the full rail now. The
   card set simply takes the width it is given, and its edge is the same edge
   the heading above it uses - which the pull-out could never be, because -150
   is a guess and the rail is an expression. */
.steps li{border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
           border-radius:8px;padding:var(--s5) var(--s4);min-width:0;
           background:color-mix(in srgb, var(--accent) 8%, var(--white))}
.step-n{margin:0 0 var(--s3)}
.step-n span{display:inline-flex;align-items:center;justify-content:center;
   inline-size:42px;block-size:42px;border-radius:50%;
   background:var(--ground);color:var(--white);font-weight:800;font-size:var(--md)}
.steps h3{margin:0 0 var(--s2);font-size:var(--lg);line-height:1.25}
.step-lead{font-weight:700;margin:0 0 var(--s3)}
.step-who{margin:0 0 var(--s3);font-weight:700;color:var(--accent-ink);
   font-size:var(--sm);line-height:1.4;
   border-inline-start:3px solid var(--fill-dark);padding-inline-start:var(--s3)}
.steps li > p:last-child{margin-block-end:0}

/* THE LIMITS, SET APART ON PURPOSE. This is the section that says what the
   programme will not do and when a person must be sent elsewhere. On most
   charity sites that paragraph is the one nobody finds; here it is the only
   bordered block on the page, so a donor reading fast still lands on it. */
.limits{border:1px solid color-mix(in srgb, var(--fill) 45%, transparent);
        border-inline-start:4px solid var(--fill);border-radius:8px;
        padding:var(--s5) var(--s4);max-width:none;
        background:color-mix(in srgb, var(--accent) 8%, var(--white))}
.limits p:last-child{margin-block-end:0}
.eyebrow{font-weight:600;font-size:var(--md);letter-spacing:.04em;
         color:var(--fill-dark);margin:0 0 var(--s3)}
.op h1{margin:0 0 var(--s5);max-width:22ch}
/* The certificate sentence, quoted. It is smaller than the human line and it
   is never absent from the same page: positioning.md section 1. */
/* THE COLOUR FOLLOWS THE GROUND, and it did not, which shipped a page nobody
   could read.
   `.cert` and `.lede` were written for the dark opening band, so their colours
   were `accent` and `white`. Used inside an ordinary white section on the
   Injury page they gave 2.63:1 where the law requires 4.5, and 1.00:1 - WHITE
   TEXT ON WHITE - for the eligibility sentence, the one that tells a police
   officer or a bereaved partner that Shahaf is for them.
   check-contrast.mjs passed both: it measures a hand-written list of pairs, and
   only a person knows which ground a class lands on. That is the thing a person
   gets wrong. scripts/check-rendered-contrast.mjs now measures what actually
   renders, and it is what found these.
   So the DEFAULT is the light-ground colour, because most of the site is light,
   and the dark bands override it. Getting it the wrong way round is what made
   the failure silent. */
.cert{color:var(--accent-ink);font-size:var(--sm);line-height:1.5;margin:0;max-width:52ch}
.strip .cert,.side:first-child .cert{color:var(--accent)}

/* THE ONWARD LINK. A link, never a button: this site ships no JavaScript and a
   thing that looks like a button but navigates is a lie about what it does. */
/* THE ONWARD LINK IS A BUTTON NOW, at Admin's request on 7 September. Still an
   anchor, still navigates, still no JavaScript anywhere on this site - what
   changed is that it looks like the thing it has always been. fill carries white
   at 8.63:1; on the dark bands it flips to fillDark carrying groundLo, because
   fill against groundLo is not separable from it. */
/* 🔴 ONE ONWARD BUTTON, 22 September. There were three sizes of the same
   control, and two of them appeared within 500px of each other on the home
   page: `.on a` at 44px tall with 24px of side padding and 16px type, `.btn`
   at 48-53px with 40px and 20px. A reader met the small one four times and the
   large one twice on one scroll. `.btn`'s box is the one that wins, because it
   is the one Admin approved in the hero and the one the two gates use.
   THE SELECTOR IS SCOPED SO IT CANNOT EAT `.btn-line`. `.on a` used to beat
   `.btn-line` on specificity and paint it solid, so the transparency page
   asked for a primary and a secondary and drew two identical purple pills. */
/* 🔴 THE LAST THING ON FOUR OF THE FIVE PAGES WAS A 93px PILL FLOATING IN
   WHITE, 22 September - 64px of nothing above it, 64px below, then the dark
   footer. The home page closes properly and the other four dribbled out. On
   the giving page, whose whole job is to convert, the last thing a reader met
   was a small "About" pill.
   NO NEW WORDS AND NO NEW SECTION. The onward link the page already ends with
   is given the ground treatment the site already uses, so the page lands on a
   band that meets the footer instead of trailing off. On a long page with no
   other change of ground - Injury and Treatment run four to seven screens of
   unbroken white - this is also the change of ground a thumb needs to know
   where it is.
   `:has()` keeps `main`'s own bottom padding out of the way, or a strip of
   white reappears between the band and the footer. */
main:has(> .on:last-child){padding-block-end:0}
main > .on:last-child{
  margin-block:var(--s7) 0;margin-inline:calc(50% - 50vw);
  padding:var(--s6) max(var(--s4), calc(50vw - 560px));
  background:color-mix(in srgb, var(--accent) 8%, var(--white));
  border-block-start:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
  /* Two pills and the separator between them were three inline things with a
     literal `·` floating between 48px buttons. A row with a gap is the same
     arrangement said properly. */
  display:flex;flex-wrap:wrap;align-items:center;gap:var(--s3)}
.on{margin:var(--s5) 0 0}
.on a:not(.btn){background:var(--fill);color:var(--white);font-weight:700;
      text-decoration:none;border-radius:999px;padding:var(--s2) var(--s5);
      font-size:var(--md);
      /* The same invisible 2px `.btn` spends on its outline, so a filled pill
         and an outlined one are the same object and not two objects 4px
         apart. */
      border:2px solid transparent;
      display:inline-flex;align-items:center;min-height:48px;min-width:44px}
.on a::after{content:"\00a0›"}
/* 🔴 THE DARK-GROUND VARIANT IS ONE VARIANT NOW. The same button was white
   with a purple border on the trust strip and lilac with no border in the
   films band - two dark bands 1.9 screens apart on one page. `fillDark`
   carrying `groundLo` is the measured pair and it is the one that stays. */
.strip .on a,.side:first-child .on a,.op .on a,
.strip .on a.btn,.strip-on a.btn{background:var(--fill-dark);color:var(--ground-lo);
   border-color:var(--fill-dark)}
/* 🔴 THE `[dir="rtl"]` OVERRIDES ARE GONE, AND THEY WERE POINTING BACKWARDS.
   22 September, proved by rendering both glyphs in an RTL line. U+2039 and
   U+203A are MIRRORED characters: the browser draws each one the other way
   round inside a right-to-left run. The base rule's `›` therefore already
   draws as `‹` in Hebrew - forward, the way the reader is going - and the
   override's `‹` drew as `›`, pointing back the way they came. It was on the
   main action of every Hebrew page. */

/* THE FOUR STAGES. Numbered because they are a sequence and the order is the
   argument, not decoration. */
.stages{margin:0;padding-inline-start:var(--s4)}
.stages li{margin-block-end:var(--s2);font-weight:600}

/* A QUOTATION BESIDE ITS PICTURE. Admin, 6 September: Yuval's three lines sit
   next to an image of him, the lines on one side and the picture on the other.
   Two equal columns on a wide screen, stacked with the words FIRST on a phone,
   because the words are the content and the picture is the support.
   The picture is not in the markup until the file exists, and this rule is
   written so one column alone looks deliberate rather than broken: with a
   single child, auto-fit collapses the track and the quotation simply sits at
   its natural width. imagery-rules.md requires exactly that. */
/* SIDE BY SIDE, and it was not. auto-fit with an 18rem minimum needs 600px to
   make two tracks; the Injury column is 66ch, about 470px, so it silently
   collapsed to one and the picture sat above the words instead of beside them.
   Two explicit tracks above 34rem, the picture in track 1 - which `dir` puts on
   the right in Hebrew, which is the side Admin asked for - and one track below,
   where two columns of this width would be worse than none. */
.beside{display:grid;grid-template-columns:1fr;
        gap:var(--s4);align-items:center;margin:var(--s4) 0 var(--s5)}
/* THE WORDS FIRST ON A PHONE, WHICH IS WHAT THIS BLOCK IS FOR. Its own comment
   below says the quotation is the content and the picture is the support, and
   then the markup put the picture first, so a phone reader met a full-width
   portrait before the three lines it exists to carry. The picture stays first
   in the source because above 34rem it belongs in the starting column; `order`
   moves it below the words only where the block is a single column. */
@media (max-width:33.99rem){
  .beside > img{order:1}
}
@media (min-width:34rem){
  /* The picture a quarter wider than it was, and the words squared up to it:
     stretched to the same height, first line level with its top edge and the
     attribution level with its bottom. */
  /* DANIEL IS 20% SMALLER THAN YUVAL WAS HERE: 1.06fr x 0.8 = 0.85. Admin, 7
     September - the portrait was too big for this column once the two men
     swapped pages, and his three lines need more room than Yuval's did because
     "קיבוץ בארי (7 לאוקטובר)" is half again the length of "186 ימים בחאן יונס". */
  .beside{grid-template-columns:minmax(0,.85fr) minmax(0,1.15fr);align-items:stretch}
  /* 🔴 `space-between` PUSHED THE ATTRIBUTION TO THE FLOOR, 22 September.
     The column's height is set by the square photograph beside it, so on the
     Hebrew home page three lines of quotation ended at y=265 and the name
     began at y=507: 242px of empty column inside one block, growing every
     time the window got wider. Centred, the same slack sits above and below
     the pair, where it reads as air rather than as a gap. */
  .beside .quote{display:flex;flex-direction:column;justify-content:center;
                 gap:var(--s5)}
  /* Sized to the picture beside it rather than to body copy: at 20px the three
     lines filled a third of the column's height and the block read as a caption
     that had drifted, not as a quotation set against a portrait. */
  /* 15% down from the last step, Admin 7 September: 1.15 x 0.85 = 0.98. */
  .beside blockquote p{font-size:var(--lg);line-height:1.45}
  /* BETWEEN TWO COLUMNS AND THE BREAKOUT THERE IS A NARROW BAND, and Daniel's
     longest line broke in it: from 34rem the block splits in two, but it does
     not take 150px from either margin until 58rem, so around 860px the words sit
     in about 257px at 27px type. One step down for that band only. Measured at
     560, 700 and 860: one line each, all three. */
  @media (max-width:57.99rem){
    .beside blockquote p{font-size:var(--md)}
  }
  /* THE HOME BLOCK IS SIZED TO DANIEL'S LINES, NOT YUVAL'S. Yuval's longest is
     "186 ימים בחאן יונס"; Daniel's is "קיבוץ בארי (7 לאוקטובר)", half again as
     long, and in a 0.75fr column at 35px it broke after the opening bracket -
     which in a right-to-left line leaves the bracket stranded at the end of one
     row and its number at the start of the next. Even columns, and the type at
     the plain step rather than a quarter over it. Three lines that each land
     whole is the point of the block. */
  /* Yuval's three lines are short, so the home block gives the picture the
     larger share and the type the bigger step. It was the other way round while
     Daniel was here, for exactly the opposite reason. */
  .home .beside{grid-template-columns:minmax(0,1.15fr) minmax(0,.85fr)}
  .home .beside blockquote p{font-size:calc(var(--lg) * 1.15)}
  /* AND THE SAME STEP DOWN FOR THE HOME BLOCK, WRITTEN AFTER the rule it has to
     beat rather than before it. .home .beside blockquote p outranks the plain
     .beside version, so the band override further up never reached this page:
     equal specificity to itself, and the later one wins. Same trap as the
     .founder columns and the align-items declared twice - three times now that
     a media query has been mistaken for extra weight. */
  @media (max-width:57.99rem){
    .home .beside blockquote p{font-size:var(--md)}
  }
}
/* THE BLOCK BREAKS OUT OF THE READING COLUMN. This page's column is 66ch, about
   470px, and once the picture took a quarter more of it his first line -
   "186 ימים בחאן יונס." - no longer fit on one line and broke after the place
   name. Three short lines that each land whole is the whole point of the
   quotation. Above 58rem there is room either side to take it, so it takes it. */
/* 🔴 THE PULL-OUT IS GONE, 22 September: `main` is the rail, and this block is
   capped at 820px instead, because its picture is square and every pixel of
   width it gains becomes a pixel of height. */
.beside img{display:block;width:100%;height:auto;aspect-ratio:1;object-fit:cover;border-radius:2px}
.beside .quote{margin:0}
/* The unit under the name. A second line, quieter than the name and on the same
   grey-lite the attribution already uses, which check-contrast has measured on
   white at 7.04:1. */
/* The counted word in the brand purple, Admin 7 September. accentInk on white
   is 7.01:1, so the colour carries a real distinction rather than a decorative
   one, and the number stays ink so the eye still lands on the count first. */
.hl{color:var(--accent-ink)}
.unit{display:block;font-size:var(--xs);font-weight:400;margin-block-start:2px}
/* HIS OWN WORDS. Set apart from our prose so a reader can see at a glance where
   we stop speaking and he starts, and larger than body text because it is the
   thing on the page most worth reading. The rule is the same fill the other
   quotation uses, measured at 8.63:1 on white. No new colour. */
.his-words{border-inline-start:3px solid var(--fill);padding-inline-start:var(--s3);
           margin:var(--s4) 0;font-size:var(--md);line-height:1.55;color:var(--ink)}
.his-words p{margin:0 0 var(--s3)}
.his-words p:last-child{margin-block-end:0}
/* THE FACTS A SCEPTIC CHECKS FIRST. A description list, not a table: these are
   label-and-value pairs, and a table would promise columns that do not exist.
   Every value is selectable text so the registry number can be pasted straight
   into a registry search. Nothing here is an image, deliberately.
   Colours are `ink` on white for the value and `grey-lite` on white for the
   label. Both pairs are already measured in check-contrast.mjs, so this block
   adds layout and no new colour. */
/* THE FILM STRIP, DIRECTLY UNDER THE HERO. Admin, 7 September: bigger than the
   card it replaces, purple, and the films play in place. Decision 0044 carries
   the reasoning and what it costs.
   Full bleed and padded back to the reading column, so its first word lines up
   with the first word of every section below it - the same trick the details
   stripe uses, and the reason the two bands read as a pair. */
.films{background:var(--ground);color:var(--white);
       margin-inline:calc(50% - 50vw);
       padding:var(--s6) max(var(--s4), calc(50vw - 560px))}
.films-l{font-size:var(--xl);font-weight:800;line-height:1.2;margin:0 0 var(--s5);
         max-width:22ch}
.films ul{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(19rem,100%),1fr));
          gap:var(--s4);list-style:none;margin:0;padding:0}
.films li{min-width:0}
.films li > a{display:block;border-radius:8px;overflow:hidden;text-decoration:none;
         color:var(--white);background:var(--ground-lo);
         border:1px solid color-mix(in srgb, var(--fill-dark) 55%, transparent)}
.films .poster{position:relative;display:block;line-height:0}
.films img{display:block;width:100%;height:auto;aspect-ratio:16/9;object-fit:cover}
.films .play{position:absolute;inset-block-start:50%;inset-inline-start:50%;
             inline-size:56px;block-size:56px}
[dir="ltr"] .films .play{transform:translate(-50%,-50%)}
[dir="rtl"] .films .play{transform:translate(50%,-50%) scaleX(-1)}
/* THE `.film` AND `.film-l` RULES THAT SAT HERE ARE GONE, and one of them was
   doing damage. They styled a `<video class="film">` from the version of
   decision 0046 that expected us to serve the files ourselves. No such element
   exists now - `.film` is the <details> that reveals the YouTube player - and
   the old rule's `aspect-ratio:16/9` was still applying to it: with the
   pictures removed, the closed tile held a 200px empty box, which
   check-no-images found and decision 0009 forbids. A dead rule that still
   matches something is worse than a dead rule.
   The live tile rules are at the end of this file, under ONE TILE DESIGN. */
.films .on{margin:var(--s5) 0 0}
.films .on a{background:var(--fill-dark);color:var(--ground-lo)}
/* THE PEOPLE, as people. A portrait beside a name, a role and what there is to
   say - not a definition list of posts. Fixed square portrait so five pictures
   shot at five crops still line up; the text column takes what is left. */
.people{list-style:none;display:grid;gap:var(--s5);padding:0;max-width:none;
        margin:var(--s5) 0 var(--s4)}
.people li{display:grid;grid-template-columns:auto minmax(0,1fr);
           gap:var(--s4);align-items:start}
.people img{display:block;inline-size:112px;block-size:112px;height:auto;
            aspect-ratio:1;object-fit:cover;border-radius:50%;
            border:3px solid color-mix(in srgb, var(--fill-dark) 55%, transparent)}
.p-name{font-size:var(--md);font-weight:800;line-height:1.2;margin:0}
.p-role{color:var(--grey-lite);font-size:var(--sm);margin:0 0 var(--s3)}
.people p:last-child{margin-block-end:0}
@media (max-width:30rem){
  .people li{grid-template-columns:1fr}
}

/* TECHNOLOGY AND THERAPY, in the four groups the programme actually has rather
   than as one list of eight machines. The number, what the group is for, WHO
   OPERATES IT, and only then the equipment - which is the order FR-26a needs
   and also the order a reader needs. */
.kit-lede{font-size:var(--lg);font-weight:800;line-height:1.25;margin:0 0 var(--s3);
          max-width:26ch}
/* margin-BLOCK, not the margin shorthand. The shorthand sets all four sides, so
   it silently reset the -150px breakout set for this class at 58rem and the four
   cards stacked one per row in a 470px column. Third time this file has been
   bitten by a later rule quietly undoing an earlier one. */
.kit{list-style:none;display:grid;gap:var(--s4);padding:0;max-width:none;
     margin-block:var(--s5) var(--s4);
     grid-template-columns:repeat(auto-fit,minmax(min(19rem,100%),1fr))}
.kit > li{border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
          border-radius:8px;padding:var(--s5) var(--s4);min-width:0;
          background:color-mix(in srgb, var(--accent) 8%, var(--white))}
.kit-n{margin:0 0 var(--s3)}
.kit-n span{display:inline-flex;align-items:center;justify-content:center;
   inline-size:38px;block-size:38px;border-radius:50%;
   background:var(--ground);color:var(--white);font-weight:800;font-size:var(--sm)}
.kit h3{margin:0 0 var(--s2);font-size:var(--md);line-height:1.25}
.kit-who{margin:0 0 var(--s3);font-weight:700;color:var(--accent-ink);
   font-size:var(--xs);line-height:1.4;
   border-inline-start:3px solid var(--fill-dark);padding-inline-start:var(--s3)}
.kit ul{list-style:none;margin:0;padding:0;display:grid;gap:var(--s3)}
.kit ul li{font-size:var(--sm);line-height:1.5;color:var(--grey-lite)}
.kit ul strong{color:var(--ink);font-weight:700}

/* THE FACES, ROUND AND LARGER THAN THE ROSTER ON THE TRANSPARENCY PAGE, with
   the name and the role under each. Admin, 7 September. Fixed square ratio so
   five portraits shot at five different crops still line up as one row. */
/* 8rem, so five portraits sit on one row rather than four and a straggler:
   5 x 128 + 4 x 24 of gap is 736, inside the 760 this column gives them. */
.roster{display:grid;grid-template-columns:repeat(auto-fit,minmax(8rem,1fr));
        gap:var(--s5) var(--s4);list-style:none;margin:var(--s6) 0 var(--s4);
        padding:0;max-width:none;text-align:center}
/* 🔴 ONE BASELINE, 22 September. The five captions ran 2, 3, 2, 3 and 5 lines,
   so the row bottoms differed by 60px and the role lines never formed a row at
   all. Three explicit rows - picture, name, role - make the name start on one
   line for all five and the role start on one line for all five, whatever each
   one wraps to. */
.roster li{min-width:0;display:grid;grid-template-rows:auto auto 1fr;
           align-content:start;gap:var(--s2)}
/* height:auto is not optional here. The img tags carry width="1600" height="1600"
   - correct, and what stops the page jumping while pictures load - but the
   height attribute maps to a real CSS height, which beats aspect-ratio. Without
   this line every portrait rendered 157px wide and 1600px tall. */
.roster img{display:block;width:100%;height:auto;max-width:140px;aspect-ratio:1;object-fit:cover;
            border-radius:50%;margin:0 auto var(--s3);
            border:3px solid color-mix(in srgb, var(--fill-dark) 55%, transparent)}
.roster strong{display:block;font-size:var(--sm);font-weight:700;line-height:1.3}
.roster span{display:block;color:var(--grey-lite);font-size:var(--xs);line-height:1.45;
             margin-block-start:2px}
.facts{display:grid;grid-template-columns:repeat(auto-fit,minmax(15rem,1fr));
       gap:var(--s3) var(--s4);margin:0 0 var(--s4);max-width:none}
.facts>div{min-width:0}
.facts dt{font-size:var(--xs);color:var(--grey-lite);margin:0 0 2px}
/* THE REGISTERED NAME KEEPS BOTH ITS SPACES. It is quoted verbatim from the
   certificate and it genuinely has two, but HTML collapses runs of whitespace,
   so the promised word-for-word spelling changed on screen. `pre-wrap` keeps
   them without touching the characters in the source, so the name is still
   selectable and pasteable exactly as registered. Raised in review on the Transparency pull request. */
.facts dd{margin:0;color:var(--ink);font-weight:600;line-height:1.4;
          overflow-wrap:anywhere;white-space:pre-wrap}
.facts dd strong{font-weight:800}
/* THE ROSTER PORTRAITS, ALL THE SAME SIZE. Admin, 7 September: on Transparency
   everybody including the founder is shown at one size, because that page is a
   roster and a roster with one big portrait in it is not one. Small, round and
   beside the name rather than above it, so five of them read as a list of
   people and not as a gallery. */
.face{width:44px;height:44px;border-radius:50%;object-fit:cover;
      margin-inline-end:var(--s2);vertical-align:middle}
.facts dd{display:flex;align-items:center;gap:0}

/* THE REGISTERED PURPOSE, QUOTED. It is the certificate's own sentence and not
   ours, so it is set apart the way Yuval's quotation is: a rule beside it, no
   quotation marks. The translation under it is italic because it is a rendering
   and not a legal name. */
.purpose{border-inline-start:3px solid var(--fill);padding-inline-start:var(--s3);
         margin:0 0 var(--s3)}
/* 🔴 THE QUOTATION IS CAPPED, 22 September. It had no width of its own, so in
   the full-bleed formal band it ran 1,101px - ONE HEBREW LINE OF 134
   CHARACTERS, and 103 a line in English, against a locked measure of 66. It is
   the most official paragraph on the site and it was the least readable. */
.purpose p{margin:0 0 var(--s2);max-width:var(--measure)}
/* 🔴 NO FAUX ITALIC, 22 September. Assistant ships no italic, so `font-style`
   made the browser slant the upright - a synthetic oblique, on the one English
   block that used it and nowhere in Hebrew. The distinction it was carrying
   (this is a rendering, not the legal name) is already carried by the grey. */
.purpose .trans{color:var(--grey-lite)}

/* THE HERO AND PAGE IMAGES. Full width of the reading column, never taller
   than a phone screen, so the picture sets a mood without pushing the words
   below the fold. width and height are on every img so the browser reserves the
   space before the file arrives and nothing jumps as the page loads. */
/* <picture> IS A WRAPPER WITH NO BOX OF ITS OWN. A hero that has a phone crop
   wraps its img in one, and every `.op > .hero-img` rule in this file stopped
   matching the moment it did - the desktop hero lost its absolute positioning
   and check-hero-contrast found it by measuring 2 pieces of text where it had
   measured 10. Those rules are descendant selectors now, and this keeps the
   wrapper from adding a layout box between them. */
.hero-pic{display:contents}
.hero-img{display:block;width:100%;height:auto;max-height:52vh;object-fit:cover;
          border-radius:2px;margin:0 0 var(--s4)}

/* THE FOUNDER'S BLOCK, ON HOME ONLY. Admin, 6 September: his photograph is
   larger than the rest of the team's and sits above them, with the manifesto
   beside it. On Transparency he is the same size as everybody else, because
   that page is a roster and a roster with one big portrait in it is not one.
   Stacks with the PICTURE FIRST on a phone, which is the one place a portrait
   should lead: it is the face that makes the words worth reading.
   The photograph is not in the markup until the file exists, and with a single
   child the manifesto simply sits at its natural width. */
/* BOTH COLUMNS END TOGETHER, at Admin's request on 7 September. The grid
   already stretched the picture's CELL to the height of the words; the picture
   inside it kept its own aspect and left a gap under itself. height:100% with
   cover fills the cell, so the bottom of the photograph and the bottom of the
   manifesto are the same line, which is what makes the block read as one thing
   rather than two things that happen to be side by side. */
/* THE GAP IS 30px WIDER, so the manifesto never runs up against the picture:
   15px off the words, 15px off the photograph, which is what Admin asked for.
   align-items was declared twice in this rule and the second one won, so the
   stretch that makes both columns end together was being undone a line after it
   was written. One declaration now. */
/* The picture takes the smaller share now. Uncropped it keeps its own square
   shape, so a half-width column left a tall band of white beside seven
   paragraphs; a narrower one shortens the picture and lengthens the words, and
   the two ends come closer together without cutting anything off. */
/* ONE COLUMN BY DEFAULT, AND TWO THINGS WENT WRONG WITHOUT IT.
   auto-fit with a 13rem minimum made two tracks from 416px upward, long before
   there was room for two. Measured at 600px the picture cell was 248 wide and
   796 tall, because height:100% with cover stretches it to the manifesto's
   height: 3.2x as tall as it is wide, and Ram occupies x 18%-74% of his frame,
   so anything past 1.75x starts cutting him. At 768px the same split left the
   manifesto 248px wide, which is 36 characters a line - a column of fragments
   rather than a manifesto. The two-column arrangement waits for the width that
   can carry it, below. */
.founder{display:grid;grid-template-columns:minmax(0,1fr);
         align-items:stretch;
         gap:calc(var(--s4) + 30px);margin:0 0 var(--s5)}
/* THE WHOLE PICTURE, UNCROPPED. This supersedes the 7 September note above it:
   filling the cell made the two columns end on the same line and took the top
   and bottom off the photograph to do it. Admin asked for it uncut, so it keeps
   its own shape and the columns end where each one ends. */
/* ENDS TOGETHER *AND* UNCUT, which earlier looked like a choice between two
   things and is not. contain fits the whole photograph inside a cell stretched
   to the height of the manifesto: the columns end on the same line because the
   cell does, and nothing is cropped because contain never crops. The space
   contain leaves above and below is white, and so is the studio background
   behind Ram, so there is nothing to see. */
/* 🔴 AND A CAP, BECAUSE THE TWO LANGUAGES WRITE DIFFERENT LENGTHS. `height:100%`
   ties the picture to the manifesto beside it, and Ram's English runs longer:
   measured at 1280px the same portrait was 553px tall in Hebrew and 812px in
   English, which is not the same page in two languages, it is two different
   designs. Admin asked on 16 September for the assets to sit the same way in
   both. The cap is the Hebrew height rounded up; whichever column is longer,
   the picture now stops at the same place. */
.founder img{display:block;width:100%;height:100%;max-block-size:560px;
             object-fit:cover;object-position:46% center;border-radius:2px}
/* THESE LIVE HERE, NOT UP WITH THE OTHER BREAKPOINTS, and that placement is
   the whole reason they work. A media query carries no extra specificity, so
   the plain .founder rule above - later in the file - was quietly winning and
   the columns stayed a 50/50 split however the query was written.
   The sum that used to be written here - 300px of picture against 616px of
   text, a cell 1.40x as tall as it is wide - described a text column that is
   no longer 616px. It is superseded by the sum below, which is the same
   arithmetic on the numbers the file now uses. */
/* TWO COLUMNS ONLY WHERE TWO COLUMNS FIT, WHICH IS NOT 768px.
   At 48rem the picture took its full 320px and the manifesto got whatever was
   left: 176px, which is 25 characters a line - a column of word fragments, and
   worse than no second column at all. The pair needs 320 + 54 of gap + a
   readable measure, so it waits for 58rem, where the block also breaks out of
   the reading column and has 970px to divide.
   Below that the picture sits above the words at its own size, which is the
   arrangement a phone already uses.
   THE TEXT COLUMN TAKES THE MEASURE, NOT WHATEVER IS LEFT OVER. At 1fr it took
   the whole 616px the pull-out gave it, which in English is 92 characters a
   line - a third past the 75 where the eye starts losing its place coming back
   to the next line, and the worst measure anywhere on the site. The pair is
   centred in what is left, so the space shows up evenly on both sides of the
   block rather than as one ragged margin.
   THE PICTURE COLUMN GREW WITH IT. Ram occupies x 18%-74% of his frame, so a
   cover crop keeps all of him while the cell stays under 1.75x as tall as it
   is wide. A narrower text column makes the manifesto taller: about 258,000
   square pixels of type in a 464px column is 556px tall, and 320 x 556 is
   1.74x, inside the 1.75 by a hair. That hair is why the picture column is
   320px and not the 300px it used to be. */
.founder img{max-inline-size:320px}
.founder p{max-width:var(--measure)}
@media (min-width:58rem){
  /* 🔴 -75px GONE and `center` WITH IT, 22 September. At 1600 the pull-out put
     the photograph 34px PAST the section heading's own edge on one side and
     the manifesto 336px short of it on the other, because `center` divides
     whatever slack is left rather than landing on the rail. Two explicit
     columns land on it by construction.
     ALIGNED TO THE MIDDLE, not to the top: in English the portrait stops 237px
     above the end of his own words (4px in Hebrew), and a picture that ends a
     quarter of a screen early reads as a picture that failed to load. */
  .founder{grid-template-columns:320px minmax(0,var(--measure));
           justify-content:start;align-items:center}
  .founder img{max-inline-size:none}
}
.founder-name{font-size:var(--lg);font-weight:800;line-height:1.2;margin:0}
.founder-role{color:var(--grey-lite);font-size:var(--sm);margin:0 0 var(--s3)}
.founder p{margin:0 0 var(--s3)}
.founder p:last-child{margin-block-end:0}

/* THE TEAM, ONE PER ROW WITH A PORTRAIT BESIDE THE WORDS. Used on Transparency,
   where every member including the founder is the same size. */
.member{display:grid;grid-template-columns:minmax(0,7rem) minmax(0,1fr);
        gap:var(--s3);align-items:start;margin:0 0 var(--s4)}
.member img{display:block;width:100%;height:auto;border-radius:2px}
.member h3{font-size:var(--md);margin:0 0 2px}
.member p{margin:0;color:var(--ink)}
.member .role{color:var(--grey-lite);font-size:var(--sm)}
@media (max-width:26rem){ .member{grid-template-columns:1fr} }

/* THE THREE-CARD BANDS. Words first: each card reads in monochrome, because
   design-system.md gives colour a supporting role and never the only one.
   They stack on a phone and never scroll sideways. */
.cards{display:grid;grid-template-columns:repeat(auto-fit,minmax(15rem,1fr));
       gap:var(--s3);list-style:none;margin:0;padding:0}
/* The outline border is GONE, not darkened. grey-dark on white measures
   2.63:1 and ת"י 5568 asks 3:1 of a graphic that carries meaning. The top rule
   in fill measures 8.63:1 and already separates one card from the next, so the
   fix is one fewer line rather than a heavier one. */
.cards li{display:flex;flex-direction:column;gap:var(--s1);
          border-block-start:4px solid var(--fill);
          padding:var(--s3) 0 0;min-width:0}
.cards strong{font-weight:800;font-size:var(--md)}
.cards span{color:var(--grey-lite);font-size:var(--xs);line-height:1.5}

/* THE INVITATION. An invitation, not a confession: a donor funding a launch
   knows exactly what they are funding. */
.invite{font-size:var(--lg);line-height:1.4;margin:var(--s4) 0 0}

/* THE LINE IN THE OTHER SCRIPT. Real content, not a language-switch label. */
/* greyLite, not greyDark. greyDark on white is 2.63:1 and this rule separates
   the other-script passage from the page, which makes it a graphic that carries
   meaning. Third time that colour has been reached for as a hairline. */
.other{border-block-start:1px solid var(--grey-lite);padding-block-start:var(--s4);
       color:var(--grey-lite);font-size:var(--xs)}
.other a{color:var(--accent-ink);display:inline-flex;align-items:center;min-height:44px}

/* ── THE HERO H2 ──────────────────────────────────────────────────────────
   Decision 0037: the hero must make a reader UNDERSTAND the project as well as
   feel it. Without this line the only explanatory text in the hero is the
   certificate sentence, which is written for the Registrar and is set small.
   It sits between the headline and that sentence, and it is read, not scanned. */
.h2{font-size:var(--lg);line-height:1.4;font-weight:600;color:var(--white);
    margin:0 0 var(--s4);max-width:34ch}

/* ── THE TRUST STRIP ──────────────────────────────────────────────────────
   Decision 0037: "a bold strip with all", not a full section. Every checkable
   fact in one band a reader takes in at a glance. If it ever needs a paragraph
   it belongs on the Transparency page instead. */
/* A QUARTER OF A SECTION. Admin, 7 September: this belongs directly under the
   hero and it is a stripe, not a block. Its padding comes down from s6 to s3,
   the label and the value sit on one line instead of two, and the whole band is
   about a quarter the height it was. Same purple, same content, same link. */
/* 🔴 `groundLo`, NOT `ground`, 22 September. This band, the films band and the
   footer were all the same dark purple full-bleed, so a reader scrolling past
   this one at 55% of the home page met what looked like the footer and had no
   reason to keep going. Same palette, one less false ending: the deeper of the
   two darks belongs to the band that is not the end of anything. */
.strip{background:var(--ground-lo);color:var(--white);
       margin-inline:calc(50% - 50vw);
       padding:var(--s3) max(var(--s4), calc(50vw - 560px))}
/* Label and value on one line rather than stacked: that alone is most of the
   height. The mark keeps its own line above them. */
.strip dl > div{display:flex;flex-wrap:wrap;align-items:baseline;gap:0 var(--s2)}
.strip dt{margin-block-end:0}
.strip-mark{display:flex;align-items:center;gap:var(--s2) var(--s3);flex-wrap:wrap;
            margin:0 0 var(--s4);font-size:var(--md)}
.strip-mark svg{height:30px;width:auto;flex:none}
/* 🔴 THE WORDMARK FACED TWO DIRECTIONS ON ONE ENGLISH PAGE, 22 September.
   The bar and the footer use the English lockup, where the bird flies right
   and sits after the name (decision 0036). This band uses the standalone mark,
   of which there is only one file, so it flew LEFT and sat before the name -
   the Hebrew arrangement, on an English page, between two correct ones.
   NO NEW ASSET. The row is already a flex row, so `order` moves the mark past
   the name and `scaleX(-1)` turns the bird the way the English lockup already
   turns it. Both are things the brand has approved; neither invents anything. */
html[lang="en"] .strip-mark > *{order:1}
html[lang="en"] .strip-mark svg{order:2;transform:scaleX(-1)}
html[lang="en"] .strip-mark span{order:3}
.strip-mark strong{font-weight:800}
.strip-mark span{color:var(--accent);font-size:var(--sm)}
.strip dl{display:grid;grid-template-columns:repeat(auto-fit,minmax(15rem,1fr));
          gap:var(--s3) var(--s4);margin:0}
.strip dt{font-size:var(--xs);color:var(--accent);margin-block-end:2px}
/* The registry number must be selectable so a reader can paste it into a
   registry search. Nothing here is an image. */
.strip dd{margin:0;font-weight:600;font-size:var(--sm);line-height:1.4}
.strip-on{margin:var(--s3) 0 0}
.strip-on a{color:var(--accent);font-weight:700;display:inline-flex;
            align-items:center;min-height:44px}
.strip-on a::after{content:"\00a0›"}

/* The hero body text. Between the H2 and the certificate sentence: larger than
   the legal line because it is meant to be read, smaller than the H2 because it
   is not the claim. It carries the registered eligibility terms, so nobody
   eligible reads the hero and concludes the site is not for them. */
/* 🔴 THE 44ch CAP IS SCOPED TO THE HERO, 22 September. Outside it the cap
   resolved to 433px inside a 464px column, so the page's opening paragraph had
   a ragged edge 31px short of every other block and nothing else shared it.
   Inside the hero the cap is doing real work and stays. */
.lede{font-size:var(--md);line-height:1.5;color:var(--ink);margin:0 0 var(--s4)}
.op .lede{max-width:44ch}
.strip .lede,.side:first-child .lede{color:var(--white)}
/* The registered description is the longest item in the strip and it is a
   quotation, so it takes the full width rather than fighting for a column. */
.strip .wide{grid-column:1/-1}

/* THE QUOTATION. Yuval's own account of his service, set apart so it reads as
   his words and not as our claim. No quotation marks: the indent and the rule
   do that job, and typed quotes in Hebrew fight the gershayim in the name. */
.quote{margin:var(--s5) 0;padding-inline-start:var(--s4);
       border-inline-start:3px solid var(--fill)}
.quote blockquote{margin:0}
.quote p{font-size:var(--lg);line-height:1.35;font-weight:600;margin:0 0 var(--s1)}
.quote figcaption{margin-block-start:var(--s3);color:var(--grey-lite);
                  font-size:var(--xs)}

/* THE THEATRES. Four words, side by side, reading as a record rather than a
   list. They are places, never one person's deployments: no durations and
   nobody to identify, which is what decision 0009 requires. */
.places{font-size:calc(var(--md) * 1.2);font-weight:700;
        display:flex;flex-wrap:wrap;gap:var(--s2) var(--s4);list-style:none;
        margin:0 0 var(--s4);padding:0}
.places li{font-weight:800;font-size:var(--lg);color:var(--accent-ink);
           line-height:1.2}

.cost strong{font-weight:800}


/* THERE AND HERE. The whole argument is the pair, so they sit side by side on a
   wide screen and stack in that order on a phone. The dark side is THERE. */
.split{display:grid;grid-template-columns:repeat(auto-fit,minmax(17rem,1fr));
       gap:var(--s4);margin:var(--s4) 0 var(--s5)}
/* ── TWO HAIRLINES AND TWO PALE GROUNDS, 22 September ─────────────────────
   There were SIX hairline strengths (fill at 18, 20, 22, 25, 35 and 45 per
   cent) and FIVE pale grounds (accent at 6, 8, 12, 14 and 16), none of them
   distinguishable from its neighbours and two of them - the press band at 6%
   and the statistics band at 14% - stacked 40px apart, where a 4% step in
   lightness reads as a printing fault rather than as a distinction.
   THE SET IS NOW: `fill 22%` for a hairline on light, `fill 45%` for the edge
   of a control; `accent 8%` for a card fill, `accent 14%` for a full-bleed
   band. Four values, each with a job. */

/* 🔴 THE SAME FURNITURE AS EVERY OTHER CARD, 22 September. On the giving page
   a square-cornered card with a solid grey edge sat 40px above a rounded card
   with a pale lilac edge, both the same width and both padded the same - two
   card systems, stacked. */
.side{padding:var(--s4);min-width:0;border-radius:8px}
.side:first-child{background:var(--ground-lo);color:var(--white)}
.side:last-child{background:var(--white);border:1px solid var(--grey-lite)}
/* --xl, not --xxl. At 58px "To volunteer" broke across two lines inside its own
   door, and check-mobile refused it: a 12-character heading has no business on
   two lines. It also removes something the first review was right about - a
   label set larger than the page's own h1 is a label pretending to be a level.
   (Written without the pull request number, because a three-digit reference
   with a hash in front of it is a valid hex colour and check-site reads it as
   one. Fourth time this file has tripped that rule with prose.) */
/* 🔴 `--lg`, NOT `--xl`, 22 September. `--xl` IS the h2 step, so on the giving
   page "דרכים לתמוך" (the section) and "לתרום" (a card inside it) were both
   40px at weight 800 and differed only in colour. Colour is not hierarchy.
   28px against 40 is 1.43 - one clear step, the same one every other h3 takes. */
.side-n{font-size:var(--lg);font-weight:800;line-height:1.15;margin:0 0 var(--s3)}

/* TWO DOORS OF EQUAL WEIGHT, WHICH THE DEFAULT SPLIT IS NOT.
   `.side:first-child` is dark and filled and `.side:last-child` is white with a
   hairline, and on Home that difference IS the argument: THERE against HERE.
   On How to help the two are a CHOICE between two different people, and giving
   one a filled dark panel tells a volunteer that giving is the real ask.
   Raised in review, and it contradicted what the page claims to do.
   Both sides take the light treatment here, so neither leads. */
.doors .side:first-child,
.doors .side:last-child{background:var(--white);border:1px solid var(--grey-lite);color:var(--ink)}
.doors .side:first-child .side-n{color:var(--accent-ink)}
.side:first-child .side-n{color:var(--accent)}
.side:last-child .side-n{color:var(--accent-ink)}
.side-l{font-size:var(--md);font-weight:600;margin:0 0 var(--s4);line-height:1.4}
.side-note{font-size:var(--xs);margin:0}
.side:first-child .side-note{color:var(--accent)}
/* Links out, never a player. Nothing on this site moves without being asked. */
.watch-list{list-style:none;margin:0 0 var(--s3);padding:0}
/* The films no longer use this list;    never reach a tile again, which is exactly what it did: equal specificity to
      collapsed into a 60px sliver inside its own tile. */
.side .watch-list a{color:var(--white);font-weight:700;display:inline-flex;align-items:center;
              min-height:44px;text-decoration:underline;text-underline-offset:4px}
.watch-list a::after{content:"\00a0\2197"}

/* THE LOCKUP IN THE HERO. It sits where the eyebrow was, at a size that reads
   as a statement rather than as navigation. currentColor resolves to white on
   this ground, so no fill is set here and the artwork stays one file. */
/* 🔴 THE LOCKUP IS GONE FROM THE HOME OPENING, Admin 22 September, and the h1
   takes the weight it was carrying. `.hero-mark` stays defined because the
   Injury opening still uses it; only Home stopped calling it.
   THE SIZE IS THE POINT. The lockup ran to 72px, so removing it and leaving the
   h1 at its old step would have made the page open smaller, not cleaner. The
   home h1 now takes the display step, which is the same clamp the lockup had,
   and the descriptor reads as the masthead it actually is. */
/* 🔴 THE TRACKING MOVED TO ENGLISH, 22 September. The file's own note says
   negative tracking is "never applied to Hebrew at any size", and this rule is
   not behind `html[lang="en"]`, so the Hebrew home headline shipped at
   -0.87px per letter at 58px while the four other Hebrew h1s at the same size
   shipped at normal. It closes up the counters in ש and ח.
   AND THE LEADING GOES BACK ON THE SCALE. 1.08 is tighter than any other
   heading on the site; at 21.84px on a phone it put a three-line headline's
   lines 23.59px apart, which is touching. */
/* ── THE OPENING LOCKUP: A NAME, THEN WHAT IT IS ──────────────────────────
   Admin, 22 September: `שח״ף ·` as the h1 and the registered description as an
   h2 under it, two lines in all. One heading carrying both halves took three
   lines at 1280 and gave the eye nothing to land on first.
   THE LADDER IS 58 / 40 / 24.3 AT 1280 - the name, the description, then the
   promise - which is 1.45 and 1.65 between the steps, both past the scale's
   own 1.25. The description is `--xl`, the same step every section heading on
   the site takes, so the biggest thing under the h1 is the thing that says
   what the organisation is.
   NO CAP ON THE DESCRIPTION, AND THE ARITHMETIC IS WHY IT IS SAFE. 31 Hebrew
   characters at 40px measure about 508px. In Hebrew the words start at the
   right edge of the band, so 508px reaches x=692 at 1280 and x=852 at 1600,
   and the man in the photograph occupies the half below x=640 and x=800. The
   line stops short of him at both widths, and check-hero-contrast measures the
   pixels actually behind it rather than taking that on trust. */
.hero-name{font-size:var(--xl);font-weight:800;line-height:1.15;
           margin:0 0 var(--s3);max-width:none;text-wrap:balance}
.op > .hero-name::before{display:none}
.home .op h1{font-size:var(--xxl);line-height:1.12;
             margin-block-end:var(--s3);max-width:16ch}
/* 🔴 THE NAME IS IN THE h1 NOW, Admin 22 September: `שח״ף · עמותה לשיקום...`.
   That is also why removing the lockup from the opening is still safe under
   positioning.md - the rule is that the NAME never travels without its
   descriptor, and here they are the same sentence.
   The separator is the middle dot the brand already uses in the footer, set
   quieter than the words on either side of it so it reads as punctuation. */
.h1-mark{white-space:nowrap}
.h1-sep{color:var(--accent-ink);font-weight:400;padding-inline:0.15em}
/* 🔴 ENGLISH TAKES A STEP DOWN, AND IT IS MEASURED. The English descriptor is
   "A nonprofit for rehabilitation and resilience after post-trauma" against the
   Hebrew "עמותה לשיקום וחוסן לפוסט־טראומה" - nearly twice the characters for the
   same sentence. At the display step it ran to four lines, the opening measured
   731px of an 800px screen at 1280 (102.6% with the bar) and the English heroes
   spread 1.82x apart, over the 1.75x check-mobile holds them to. One step down
   fixes all three, and the Hebrew keeps the larger size it can carry. */
/* 🔴 THE ENGLISH HOME HEADLINE WAS THE SIZE OF ITS OWN SECTION HEADINGS.
   22 September. `--xl` is the h2 step, so at 1280 the h1, all four h2s, the
   turn line and the closing line were 40px - the page had two type sizes and
   no title. And `20ch` held it to 432px in a 640px column, which is what broke
   "post-trauma" across two lines and left one word alone on line four, while
   the 16px dedication under it ran 627px: the widest block in the opening was
   its smallest type.
   `--xxl` is what Hebrew uses and what every other English page uses. The cap
   comes off and `text-wrap:balance` evens the lines instead. */
:root[lang="en"] .home .op h1{max-width:none;text-wrap:balance}
/* TWO DOORS, AND THEY WRAP RATHER THAN SHRINK. A button that shrinks to fit a
   narrow screen stops being a 44px target, which check-viewport measures. */
/* TWO DOORS, AND THEY WRAP RATHER THAN SHRINK. A button that shrinks to fit a
   narrow screen stops being a 44px target, which check-viewport measures.
   THE GAP IS s4 AND NOT s5, and that is measured rather than chosen: at s5 the
   English opening plus the bar filled 92.9% of a 1280x800 screen against the
   92% check-mobile allows, because a reader who cannot see the page continues
   does not scroll. Eight pixels decided it. */
.hero-go{display:flex;flex-wrap:wrap;gap:var(--s3);margin:var(--s4) 0 0}
/* WHAT SHAHAF IS: the mark, then the sentence, then the creed.
   🔴 THE MARK IS ON THE PHYSICAL LEFT IN BOTH LANGUAGES, Admin 22 September:
   "make it on center and from left side have the logo". Left means left here,
   not "the start of the line", so this is one of the few places in this file
   that does NOT use a logical property. It is first in the DOM, which puts it
   on the left in English by default; Hebrew reverses the row so the first item
   lands on the left there too. A screen reader hears the mark first either way.
   THE WORDS ARE CENTRED and the mark is not, so the block reads as a masthead
   beside a statement rather than as two columns of text. */
/* 🔴 THE MARK IS ON THE PHYSICAL RIGHT IN BOTH LANGUAGES, Admin 22 September:
   "logo from right side". He asked for the left earlier the same day and then
   looked at it; this is the later instruction and it prints.
   RIGHT MEANS RIGHT, so this is one of the few rules in this file NOT written in
   logical properties: everything else uses inline-start and inline-end so that
   `dir` mirrors it, and mirroring is exactly what must not happen here. The mark
   is first in the DOM, which a screen reader meets first in both languages. In
   Hebrew a flex row starts on the right, so the default puts it there; English
   reverses the row to land it in the same place.
   THE WORDS ARE CENTRED IN THEIR OWN COLUMN, and the column is centred in the
   page, so the paragraph reads as a statement rather than as a second column. */
/* 🔴 IT BREAKS OUT OF THE READING COLUMN, and without that the cap below can
   never be met. `main` is capped at 820px on this page, so a lockup plus a gap
   left the words about 670px; at the display size that is 39 characters a line
   at 1600px and 37 at 768px, against the 45 check-mobile requires from 768 up.
   Measured at eight widths before and after, not guessed.
   THE TECHNIQUE IS THE ONE THE FIGURES BAND ALREADY USES - full bleed by
   negative inline margin, content re-capped by padding - so there is one way of
   escaping the column in this file rather than two. check-viewport proves it
   never turns into sideways scrolling. */
/* 🔴 `--s7` UNDER IT, NOT ZERO, 22 September. Measured on the Hebrew home page:
   the last ink of the closing creed sat at y=1039 and the statistics band's own
   top hairline at y=1042 - THREE PIXELS - while every other seam on that page
   was 104. English never showed it, because the English section rule put 104px
   back by a different route. The band looked as though it owned the sentence.
   AND THE RAIL: this was `50vw - 520px`, a fourth number. */
/* 🔴 THE WORDS WERE NOT ON THE CENTRE OF THE PAGE AND THE MARK IS WHY.
   Admin, 23 September: "on center of section and logo right to that."
   Measured before: the page's centre is 640 at 1280 and the paragraph's centre
   was 540 - a hundred pixels to the left of it, and 122px out at 1600. The row
   was a flex row holding the mark AND the words with `justify-content:center`,
   so what was centred was the PAIR: the mark took its width out of the right
   and pushed the words left by half of it.
   A THREE-COLUMN GRID CENTRES THE MIDDLE ONE BY CONSTRUCTION. The two flanks
   are `1fr` each, so they are always equal and the words sit on the page's own
   centre line whatever the mark is doing. The mark lives in the flank on the
   reading side - column 1 is the rightmost in a right-to-left grid, and English
   names column 3 for the same physical place, because "right" here means right
   and is one of the few rules in this file deliberately not written in logical
   properties. The third column is empty and exists only to balance the first. */
.lede-block{max-width:none;margin-block:var(--s6) var(--s7);
            margin-inline:calc(50% - 50vw);
            padding-inline:max(var(--s4), calc(50vw - 560px));
            display:grid;
            grid-template-columns:var(--lede-flank) auto var(--lede-flank);
            /* 24px and not a fluid gap, and the arithmetic is the reason: the
               rail gives the row 1120px, Admin's four written lines need about
               770 of it to land whole, and the mark is 148 wide. 770 + 2 x 148
               + 2 x 24 = 1114, which fits with three pixels to spare. A 64px
               gap here takes 80px off the flanks, the mark stops fitting in its
               own column and overflows the rail by 12px on the reading side. */
            align-items:center;column-gap:var(--s4)}
.lede-block > .lede-mark{grid-column:1;justify-self:center;min-width:0}
/* The artwork fills its declared flank and takes its own height from its own
   proportions. A fixed height with a width cap collapses an SVG to nothing:
   the height was clamped here and `max-inline-size` had nothing to cap, so the
   mark measured 0px wide. */
.lede-block > .lede-mark svg{inline-size:100%;block-size:auto;height:auto}
.lede-block > .lede-words{grid-column:2}
[dir="ltr"] .lede-block > .lede-mark{grid-column:3}
/* (the row is a grid now; the mark's physical side is set by `grid-column`
   above, so the old flex reversal has nothing left to reverse) */
.lede-mark{flex:none;margin:0;line-height:0}
.lede-mark svg{height:clamp(44px,5.4vw,84px);width:auto}
/* 🔴 THE COLUMN IS CAPPED IN CHARACTERS, NOT IN PIXELS, and that is what makes
   it hold at every width. check-mobile refuses running text over 75 characters
   a line and under 45 from 768px up, and the two languages fit very different
   amounts in the same box: Hebrew sets about 72 characters where English sets
   93. A single rem cap therefore cannot be right for both. `ch` is measured in
   the font actually rendering, so each language lands inside the window on its
   own terms, and `min()` keeps it from ever exceeding the space it has. */
/* 🔴 THE FONT SIZE IS SET ON THE COLUMN, NOT ON THE LINE, and that is the whole
   reason the cap works. `ch` is measured in the font of the element it is
   written on. With the size on `.lede-line` and the cap on `.lede-words`, the
   62ch was 62 characters of BODY text while the line rendered at the display
   size - so the column came out at 37 to 47 characters a line, under the 45
   check-mobile requires from 768px up, and the English paragraph ran to ten
   lines on a 1280px screen. Measured, not guessed: that is what the table of
   widths said before this line moved. */
.lede-words{flex:0 1 min(58ch, 100%);text-align:center;min-width:0;
            font-size:var(--lg)}
.lede-line{font-size:inherit;line-height:1.55;color:var(--ink);margin:0;
           text-wrap:pretty}
/* THE CREED IN THE BRAND PURPLE, as asked. accentInk on the page ground
   measures 7.01:1 and is the locked list's colour for exactly this job: the
   same voice as the accent, on a light ground. */
/* 🔴 ADMIN'S OWN LINE BREAKS, AND THEY ONLY APPLY WHERE THE LINES FIT.
   22 September: he wrote the block out as four lines and asked for it to look
   like that, so the breaks are written into the page rather than left to the
   column. Above 64rem the longest of them is 64 Hebrew characters in a 799px
   column at 28px and lands whole. Below it the column is narrower than the
   line, so a written break would split every phrase twice and the block would
   read as eight ragged lines instead of four. There the paragraph wraps on its
   own, which is what it did before.
   THE CREED KEEPS ITS TWO LINES AT EVERY WIDTH: both halves are short enough
   to hold on any screen this site is built for. */
@media (max-width:63.99rem){.lede-line br{display:none}}
.lede-creed{font-size:inherit;font-weight:800;line-height:1.35;
            color:var(--accent-ink);margin:var(--s4) 0 0}
/* 🔴 EQUAL, 22 September. Measured in the Hebrew hero: the outlined secondary
   was 179px and the filled primary 142px, so the quieter of the two was 26%
   the larger object and the hierarchy read backwards. English: 166 against
   147. A shared minimum makes the pair one control with two ranks. */
.hero-go .btn{flex:0 1 auto;min-inline-size:11rem}
.hero-mark{margin:0 0 var(--s5);line-height:0}
.hero-mark svg{height:clamp(46px,9vw,72px);width:auto;max-width:100%}


/* The registered scope, under the reason line. Smaller, because it is the legal
   completeness rather than the argument, and it must still be read. */
.lede-scope{font-size:var(--sm);line-height:1.5;color:var(--accent);margin:0 0 var(--s4);max-width:46ch}

/* ── THE DEDICATION AND THE CREED ─────────────────────────────────────────
   Admin, 8 September. Two lines under the headline where the eligibility
   sentence used to sit: a quiet dedication with a heart, and then the one line
   he wants read loudest on the page.
   THE HEART IS DRAWN, NOT TYPED. An emoji renders in a different face on every
   machine, is a different colour on each, and carries a spoken name a screen
   reader would read out in the middle of the sentence.
   INK, NOT greyLite, AND A MACHINE PICKED IT. greyLite is 7.04:1 on white and
   looked like the obvious quiet colour; check-hero-contrast measured it where
   it actually lands, on the studio floor of the photograph, and got 2.86:1
   against the 4.5 the standard asks. The dedication is quiet by size and weight
   instead. This is the fourth time a colour reasoned about against a section's
   background has failed against the pixels really behind the words. */
.dedication{display:flex;align-items:baseline;gap:var(--s2);
            font-size:var(--sm);line-height:1.5;color:var(--ink);
            margin:0 0 var(--s3);max-width:46ch}
.heart{inline-size:16px;block-size:15px;flex:none;color:var(--fill);
       transform:translateY(2px)}
/* accentInk, and check-hero-contrast is the arbiter rather than this comment.
   The pale accent is a dark-ground colour and measures 2.59:1 on this white;
   accentInk measures 7.01:1 on white, and the check reads the pixels actually
   behind the words - which on this photograph can be the grey of the shadow. */
.creed{font-size:var(--md);font-weight:800;line-height:1.35;
       color:var(--accent-ink);margin:0 0 var(--s4);max-width:44ch}
/* TWICE THE SIZE, WHERE ADMIN ASKED FOR IT AND NOWHERE ELSE. `.creed` carries
   this same sentence in three places; a bigger `.creed` would have grown all of
   them, including the one in the giving page's hero where the size is right.
   A second class is the smaller change. */
.creed-big{font-size:var(--xl);line-height:1.25;max-width:20ch}
/* The opening line of the giving page, up a step with it. */
.h1-big{font-size:var(--xxl)}
/* 🔴 THE GIVING PAGE'S OPENING, MUCH LARGER ON A DESKTOP. Admin, 16 September.
   Both lines, and only above 64rem: below that the hero is already stacked,
   words over picture, and the same jump would push the picture off the first
   screen - which check-mobile refuses outright, because a reader who sees only
   a bar and a headline has no sign the page goes on.
   THE MEASURE COMES DOWN AS THE SIZE GOES UP. A line set this large in a half
   width column will wrap; 14ch and 11ch are where each of these two sentences
   breaks where it should rather than where it runs out of room. */
/* THE MEASURE IS 15ch AND NOT 11, AND A CHECK PICKED THE NUMBER. check-mobile
   allows a heading one line per 18 characters: `נכנסים איתנו מתחת לאלונקה` is
   25 characters, so two lines, and at 11ch it took three. The same happened to
   `Take the weight with us`. A headline broken into more lines than its own
   length justifies is a headline fighting its column, which is exactly what
   that rule exists to catch. */
/* 🔴 AND THE COLUMN HAD TO GIVE, NOT THE TYPE. Measured: at 1280 the words sit
   in half the section, and that half is mostly padding - 230px of it aligns the
   text to the page's reading column and 40px closes the gap to the picture, so
   the headline actually had 370px to live in. At the size Admin asked for,
   `נכנסים איתנו מתחת לאלונקה` needs about 700px over two lines and took three.
   `ch` IS NOT THE MEASURE AND THIS FILE ALREADY KNEW IT: one ch is the width of
   a zero, and Hebrew letters are far wider relative to it - the same 568px
   column holds 72 Hebrew characters and 93 English ones. A 15ch cap sounded
   generous and was 200px narrower than the sentence needed.
   So the words take 57% of the section and the picture 43%. The picture is
   `contain` inside its half and simply draws a little smaller; nothing is
   cropped, which is the whole reason it is `contain` in the first place. */
@media (min-width:64rem){
  .op.duo{grid-template-columns:1.32fr 1fr}
  .op.duo .creed-big{font-size:clamp(30px,2.4vw,40px);max-width:none}
  .op.duo .h1-big{font-size:clamp(46px,4.8vw,74px);line-height:1.08;max-width:none}
}
/* ── THE HERO LADDER ──────────────────────────────────────────────────────
   Ram's review, 15 September: mark, h1, h2, three lines of body. A stranger
   should know what this site is within a second, and one long headline
   carrying both halves at once did not do that.
   THE COLOURS ARE THE TWO check-hero-contrast HAS ALREADY MEASURED ON THIS
   PHOTOGRAPH. `ground` reads 9.50:1 on the pixels behind these words and `ink`
   is what the dedication uses; the pale accent is a dark-ground colour and
   measures 2.59:1 here. Four colours reasoned about against a section's
   background have failed against the pixels really behind the words, so these
   two are reused rather than a third one chosen. */
/* A MAQAF IS A BREAK OPPORTUNITY AND `פוסט־טראומה` IS ONE WORD. At 1280 the
   headline broke after the maqaf and printed `לפוסט־` above `טראומה.`, which is
   the compound split in half. This holds it together; the prefix ל stays
   outside so the line can still break before it. */
.keep{white-space:nowrap}
/* 🔴 THE PROMISE IS IN THE BRAND PURPLE, Admin 15 September, and it is
   accentInk rather than accent. The pale accent is a DARK-GROUND colour: on
   this white it measures 2.59:1 against the 4.5 the standard asks, and
   check-hero-contrast reads the pixels actually painted behind the words - which
   on this photograph can be the grey of the shadow. accentInk holds 7.01:1 on
   the white and clears the shadow too. This is the fifth colour on this site
   reasoned about against a section's background and settled by measurement. */
/* THE SPACING SAYS WHAT BELONGS WITH WHAT, and that is the whole of Admin's
   "better position" of 15 September. The opening is three groups, not six
   lines: the mark and the two headings; then the three body lines, which are
   one argument and are set TIGHT so they read as a block; then the dedication,
   set apart because it is addressed to somebody else entirely.
   Even gaps between all six made a reader work out the grouping for themselves,
   and on a 1280px screen it read as a list. Nothing moved and nothing resized:
   the only thing that changed is where the air is. */
.hero-h2{font-size:var(--lg);font-weight:800;line-height:1.25;color:var(--fill);
         margin:0 0 var(--s5);max-width:24ch}
.hero-body{font-size:var(--sm);line-height:1.6;color:var(--ink);
           margin:0 0 var(--s2);max-width:46ch}
.hero-body + .dedication{margin-block-start:var(--s4)}
/* 🔴 40px OF AIR ABOVE THE DEDICATION, ON A DESKTOP ONLY. Admin, 16 September.
   It is the one line in the opening addressed to somebody other than the
   reader, and the gap is what says so.
   DESKTOP ONLY, and the two narrower bands already say why in their own
   comments: the opening is bounded at 390px by the photograph the words sit on
   and at 768px by check-mobile, and both of those bands have already given up
   this same gap once to stay inside their bounds. A third helping of air is
   something only a wide screen can afford. */
@media (min-width:64rem){
  .hero-body + .dedication{margin-block-start:calc(var(--s4) + 40px)}
}
.op.plain .creed{color:var(--accent)}
/* The attribution under a quotation: the name is the loud half and the unit is
   the quiet one, with the number itself in the brand purple. */
.quote figcaption strong{font-weight:800;font-size:var(--sm);color:var(--ink)}

/* ── THE FORMAL DETAILS, AS A BAND ────────────────────────────────────────
   Admin, 8 September: the registered name and the number belong in a purple
   stripe rather than in a section of their own, like the details band on Home.
   It reuses .strip, so it is the same object in the same colour; .formal only
   adds the room a heading needs and repairs the two colours that were written
   for a WHITE ground and would land on purple here.
       .facts dd is `ink` by default, which on this purple is unreadable
       .purpose's rule is `fill`, which against groundLo is not separable
   Both are stated rather than inherited, which is the mistake this file has
   made before in the other direction. */
.strip.formal{padding-block:var(--s5)}
.strip.formal h2{color:var(--white)}
.strip.formal .facts dd{color:var(--white)}
.strip.formal .facts dd strong{color:var(--white)}
.strip.formal h3{color:var(--accent);font-size:var(--md);margin:var(--s4) 0 var(--s2)}
.strip.formal .purpose{border-inline-start-color:var(--fill-dark)}
.strip.formal .purpose p{color:var(--white)}
.strip.formal .purpose .trans{color:var(--accent)}
.strip.formal .on a{background:var(--fill-dark);color:var(--ground-lo)}

/* ── THE TEAM, IN A ROW ───────────────────────────────────────────────────
   Admin, 8 September: horizontal. Five people read as a team when they sit
   side by side and as a list of posts when they stack. The portrait goes above
   the name here rather than beside it, because a row of five needs its columns
   narrow and a portrait beside text in a narrow column is a thumbnail with a
   paragraph squeezed next to it.
   min() on the track floor so the row can never be wider than the screen: a
   bare 15rem minimum is a hard 240px, and a 320px phone has 272 to give. */
/* 13rem, and the sum is why. Pulled out to 764px with a 24px gap, three tracks
   of 15rem want 768 and get two; three of 13rem want 672 and fit, so five
   people read as three and two rather than as two, two and a straggler. */
/* 🔴 A COUNT, NOT `auto-fit`, 22 September. `auto-fit` cannot know how many
   items there are, and the item count is the design: five portraits in three
   columns left a hole at the start of the second row, and in RTL the hole fell
   on one side and in LTR on the other, so the fault reversed between languages
   and never went away. Five across, once there is room for five. */
.people{grid-template-columns:repeat(auto-fit,minmax(min(13rem,100%),1fr));
        gap:var(--s5) var(--s4);align-items:start}
.people li{display:block;text-align:center}
.people img{inline-size:132px;block-size:132px;margin:0 auto var(--s3)}
.people .p-name{font-size:var(--lg)}
.people p:not(.p-name):not(.p-role){text-align:start;font-size:var(--sm);
        line-height:1.55}
@media (max-width:30rem){
  .people li{text-align:start}
  .people img{margin-inline:0}
}

/* ── TECHNOLOGY AND THERAPY, AS A SPECIFICATION ───────────────────────────
   Admin, 8 September: official, and it has to show every machine and every
   therapy rather than gesture at them. So each stage is a specification sheet,
   not a bullet list: a numbered header rule, the stage's name, then the tools
   as label-and-line rows separated by hairlines, and the person who operates
   the stage as a footer band on the card - which FR-26a requires stated
   wherever treatment is described, and which a reader skimming would miss in
   the middle of a paragraph. */
.kit > li{padding:0;overflow:hidden;display:flex;flex-direction:column;
          background:var(--white)}
.kit-n{margin:0;padding:var(--s3) var(--s4);background:var(--ground);
       display:flex;align-items:center;gap:var(--s3)}
.kit-n span{inline-size:30px;block-size:30px;font-size:var(--xs);
            background:var(--fill-dark);color:var(--ground-lo)}
.kit h3{margin:0;padding:var(--s4) var(--s4) var(--s3);font-size:var(--md);
        line-height:1.25}
.kit ul{padding:0 var(--s4) var(--s4);gap:0;flex:1}
.kit ul li{padding-block:var(--s3);font-size:var(--sm);line-height:1.5;
           border-block-start:1px solid color-mix(in srgb, var(--fill) 22%, transparent)}
.kit ul li:first-child{border-block-start:0}
.kit ul strong{display:block;color:var(--ink);font-weight:800;
               margin-block-end:2px}
/* The operator, as a band at the foot of the card rather than a line in the
   middle of it. Same fill the buttons use, measured at 8.63:1 with white. */
.kit-who{order:2;margin:0;padding:var(--s3) var(--s4);border-inline-start:0;
         background:color-mix(in srgb, var(--accent) 8%, var(--white));
         border-block-start:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
         color:var(--accent-ink);font-size:var(--xs);font-weight:700}
.kit-who::before{content:"";display:inline-block;inline-size:8px;block-size:8px;
                 border-radius:50%;background:var(--fill);
                 margin-inline-end:var(--s2);vertical-align:middle}

/* ── THE TWO GATES, AS BUTTONS ────────────────────────────────────────────
   Admin, 8 September. Both doors lead to the same form, and the two buttons
   sit side by side because their panels already do.
   THE COLOURS ARE THE TWO MEASURED PAIRS, not a light and a dark version of
   one: `fill` carries white at 8.63:1, and `accentInk` on white is 7.01:1.
   THE PRESSED STATE IS A REAL STATE, not an animation. :active darkens the
   filled button and fills the outlined one, so a thumb sees the tap land;
   :focus-visible is separate, because a keyboard needs to see where it is
   before it presses anything. Nothing moves, which FR-21 requires. */
.btn{display:inline-flex;align-items:center;justify-content:center;
     min-height:48px;min-width:44px;padding:var(--s2) var(--s5);
     border-radius:999px;font-weight:700;font-size:var(--md);
     text-decoration:none;border:2px solid var(--fill);cursor:pointer;
     /* 🔴 A BUTTON ANSWERS THE POINTER, Admin 22 September: "add to buttons some
        animation once user mark the buttons, that the color will change or have
        some reflection that user understand that it clickable".
        THIS IS NOT THE MOTION FR-21 FORBIDS, and the difference is worth stating
        because the rule is strict. FR-21 and decision 0056 are about things that
        move WITHOUT being asked - autoplay, reveals, carousels. A state change
        under a reader's own pointer is the opposite: it is the control telling
        them it heard. Nothing here starts on its own and nothing repeats.
        The global prefers-reduced-motion rule already turns every transition on
        this site off, so a reader who asked for stillness gets the colour change
        instantly instead of over 160ms. The affordance survives; only the fade
        goes, which is exactly the right trade. */
     transition:background-color .16s ease, color .16s ease,
                border-color .16s ease, box-shadow .16s ease, transform .12s ease}
.btn-fill{background:var(--fill);color:var(--white)}
/* HOVER GOES DARKER, NOT LIGHTER. Both states are on the locked design system's
   measured list: white on `fill` is 8.63:1 and white on `ground` is 18.52:1, so
   the button gets MORE readable under the pointer rather than less. The lift is
   one pixel and the ring is the brand purple at low alpha - enough to read as a
   raised object, not enough to be movement. */
.btn-fill:hover{background:var(--ground);border-color:var(--ground);
                box-shadow:0 4px 14px color-mix(in srgb, var(--ground) 28%, transparent);
                transform:translateY(-1px)}
.btn-fill:active{background:var(--ground);border-color:var(--ground);
                 transform:translateY(0);box-shadow:none}
.btn-line{background:var(--white);color:var(--accent-ink)}
/* THE OUTLINED ONE FILLS IN. accentInk on white is 7.01:1 and white on `fill`
   is 8.63:1, so this one also gains contrast rather than losing it. */
.btn-line:hover{background:var(--fill);color:var(--white);
                box-shadow:0 4px 14px color-mix(in srgb, var(--fill) 26%, transparent);
                transform:translateY(-1px)}

/* ── EVERY BUTTON ON THE SITE ANSWERS THE POINTER THE SAME WAY ────────────
   🔴 Admin, 23 September: "be sure that each button on the web will be with the
   same mark elements as on the hero section ones once a user marks the button."
   IT WAS TRUE OF THE HERO AND OF ALMOST NOTHING ELSE. The two hero doors carry
   `.btn`, and `.btn` is where the transition, the darker ground, the one-pixel
   lift and the low-alpha ring live. The onward pills at the foot of a section
   are `.on a` and had NO hover at all; the bar's action had a colour change and
   nothing else; the pills on the dark bands had neither. A reader who learned
   at the top of the page that a purple pill answers them found four more that
   did not.
   THE THREE GROUNDS EACH KEEP THEIR OWN MEASURED PAIR, and no new colour is
   introduced: on light the pill goes from `fill` to `ground` (white on them is
   8.63:1 and 18.52:1, so it gains contrast under the pointer); on a dark band
   `fillDark` carrying `groundLo` deepens to `accent`, which carries `groundLo`
   at 7.66:1; the bar's action follows the light rule because its band is white.
   NOTHING HERE MOVES ON ITS OWN. FR-21 and decision 0056 are about things that
   move without being asked; this is a control telling a reader it heard them,
   and the global reduced-motion rule already turns every transition off. */
.on a,.nav-go,.strip-on a,.mb > summary{
   transition:background-color .16s ease, color .16s ease,
              border-color .16s ease, box-shadow .16s ease, transform .12s ease}
.on a:not(.btn):hover,.nav-go:hover{
   background:var(--ground);border-color:var(--ground);color:var(--white);
   box-shadow:0 4px 14px color-mix(in srgb, var(--ground) 28%, transparent);
   transform:translateY(-1px)}
.on a:not(.btn):active,.nav-go:active{transform:translateY(0);box-shadow:none}
/* On a dark band the pale pill deepens instead of darkening, or it would
   disappear into the ground it sits on. */
.strip .on a:hover,.side:first-child .on a:hover,.op .on a:hover,
.films .on a:hover,.strip.formal .on a:hover{
   background:var(--accent);color:var(--ground-lo);border-color:var(--accent);
   box-shadow:0 4px 14px color-mix(in srgb, var(--ground-lo) 45%, transparent);
   transform:translateY(-1px)}
/* The menu control is a button too. */
.mb > summary:hover{background:color-mix(in srgb, var(--accent) 14%, transparent)}
.btn-line:active{background:var(--fill);color:var(--white);
                 transform:translateY(0);box-shadow:none}
.btn-line:active{background:var(--fill);color:var(--white)}
.btn:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
/* 🔴 THE TWO BUTTONS SIT ON ONE LINE, AND THEY ARE IN DIFFERENT CARDS. Admin,
   15 September: one door's text runs two paragraphs longer than the other's, so
   its button sat lower and the pair read as a mistake rather than as a choice.
   THE CARD IS A COLUMN AND THE BUTTON IS PUSHED TO ITS FOOT. `margin-block-start:auto`
   inside a flex column takes all the leftover height, so the button lands on
   the card's bottom edge whatever the text above it does - and since the two
   cards are the same height, the two buttons land on the same line. Nothing
   here depends on counting the paragraphs, which is what would break the next
   time somebody edits one of them.
   `align-items:stretch` on the row is what makes the two cards the same height
   in the first place; it is the grid default and is restated here because this
   rule depends on it. */
.doors{align-items:stretch}
.doors .side{display:flex;flex-direction:column}
.gate-go{margin:var(--s4) 0 0}
.doors .gate-go{margin-block-start:auto}
.gate-go .btn{width:100%}

/* ── THE FORM ─────────────────────────────────────────────────────────────
   No JavaScript anywhere in it. The choice is two radio buttons drawn as
   pressed keys, which is what a browser gives free once the input itself is
   hidden from sight but not from the keyboard: :checked + label does the
   drawing, and the input keeps its own focus ring through :focus-visible on
   the label beside it. */
.form-wrap{background:color-mix(in srgb, var(--accent) 8%, var(--white));
           border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
           border-radius:8px;padding:var(--s5) var(--s4);max-width:none}
.lead{display:block}
.pick{border:0;padding:0;margin:0 0 var(--s5);min-width:0}
.pick legend{padding:0;margin:0 0 var(--s3);font-weight:700;font-size:var(--sm);
             color:var(--accent-ink)}
.pick-row{display:flex;flex-wrap:wrap;gap:var(--s3)}
/* Off-screen rather than display:none: a hidden input is not focusable, and a
   choice a keyboard cannot reach is not a choice. */
.pick input{position:absolute;opacity:0;inline-size:1px;block-size:1px}
.pick label{display:inline-flex;align-items:center;justify-content:center;
            min-height:48px;padding:var(--s2) var(--s5);border-radius:999px;
            border:2px solid var(--fill);background:var(--white);
            color:var(--accent-ink);font-weight:700;cursor:pointer}
.pick input:checked + label{background:var(--fill);color:var(--white)}
.pick input:focus-visible + label{outline:2px solid var(--accent-ink);outline-offset:3px}
.fields{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(15rem,100%),1fr));
        gap:var(--s4)}
.field{margin:0;min-width:0}
.field-wide{grid-column:1/-1}
.field label{display:block;font-size:var(--sm);font-weight:700;
             margin-block-end:var(--s2);color:var(--ink)}
.field :is(input,select,textarea){inline-size:100%;min-height:48px;
     padding:var(--s2) var(--s3);font:inherit;font-size:var(--sm);
     color:var(--ink);background:var(--white);border-radius:8px;
     border:1px solid var(--grey-lite)}
.field textarea{min-height:120px;line-height:1.5;resize:vertical}
.field :is(input,select,textarea):focus-visible{outline:2px solid var(--accent-ink);
     outline-offset:1px;border-color:var(--fill)}
.tel-row{display:flex;gap:var(--s2)}
.tel-row select{inline-size:auto;flex:none}
.tel-row input{flex:1;min-width:0}
/* The line that says the form is not live yet. It is not a warning colour,
   because nothing is wrong: it is a fact about a thing still being built. */
.form-note{margin:var(--s5) 0 var(--s4);font-size:var(--sm);line-height:1.5;
           max-width:var(--measure);
           color:var(--ink);border-inline-start:3px solid var(--fill-dark);
           padding-inline-start:var(--s3)}
.form-go{margin:0}
/* A disabled control still has to be READ. greyLite on white is 7.04:1, and
   the usual grey-on-grey a browser draws is nowhere near it. */
.btn[disabled]{background:var(--grey-lite);border-color:var(--grey-lite);
               color:var(--white);cursor:not-allowed}

/* ══ SMALL SCREENS ═════════════════════════════════════════════════════════
   EVERYTHING FOR A PHONE IS AT THE END OF THE FILE, AND THAT IS THE POINT.
   A media query carries no extra specificity, so a plain rule written later
   beats one written earlier however narrow the query. This file has been
   bitten by that six times already - the .founder columns, align-items
   declared twice, .beside and .home .beside font sizes, the .kit margin
   shorthand, and .op.plain{min-height:0} silently undoing the hero floor.
   Rules that must win are last. There is nothing after them to lose to. */

/* ── THE BAR ON A PHONE ────────────────────────────────────────────────────
   MEASURED FIRST. On the preview at 320, 390 and 430px the bar was 262px tall,
   which is 31% of an iPhone 14's 844px screen, and it got there by stacking
   four rows: the lockup, the descriptor, five menu items over two lines, and
   the language switch. The home hero under it is another 741px, so bar plus
   hero came to 1003px and a reader saw nothing else at all.
   ONE ROW NOW, and the five links move behind a disclosure the browser already
   has. No JavaScript ships, because none is needed: <summary> takes focus,
   opens on Enter or Space, and announces open and closed by itself.
   The links are the NEXT ELEMENT after the <details>, not inside it - a closed
   <details> hides its children and no CSS re-opens that in every browser
   shipping today. `.mb[open] ~ .bar-nav` has worked everywhere <details> has,
   and it keeps exactly one copy of every link in the page. */
.bar-nav{display:flex;align-items:center;gap:var(--s3) var(--s4);flex-wrap:wrap;
         justify-content:flex-end;min-width:0}
.bar-end{display:flex;align-items:center;gap:var(--s4);min-width:0}
/* ── THE FOUR LINKS, CENTRED IN THE BAR ───────────────────────────────────
   Admin, 16 September. Centred means centred in the BAR, not in whatever space
   is left over, and those are different places whenever the mark and the action
   are different widths - which they always are, and by more in English than in
   Hebrew.
   SO THE BAR BECOMES A THREE COLUMN GRID: `1fr auto 1fr`. The middle column is
   exactly as wide as the links need, and the two 1fr columns either side are
   forced equal, which puts the middle one on the bar's centre line however wide
   the mark or the action happen to be. A flex row with `margin-inline:auto`
   would have centred the links between their neighbours instead, and drifted
   off centre on the English page where the mark is wider.
   `display:contents` ON THE WRAPPER is what lets this work without a second set
   of elements: `.bar-nav` has to exist, because `.mb[open] ~ .bar-nav` is what
   opens the phone menu, and on a phone it is a real box again. Up here it stops
   being a box and its two children become the grid's own items.
   THE ORDER IS STILL THE DOM ORDER, so `dir` decides which end is which and the
   English bar mirrors without a physical left or right anywhere. */
@media (min-width:64rem){
  .hd{display:grid;grid-template-columns:1fr auto 1fr;align-items:center}
  .bar-nav{display:contents}
  .bar-end{justify-self:end}
  /* 🔴 THE LANGUAGE LINK GOES PAST THE ACTION, ON THE BAR ONLY. Admin,
     16 September: he wants it on the far side of `לתרומות`.
     `order` AND NOT A SWAP IN THE MARKUP, because the markup is also the phone
     menu. Down there the four links stack, then the language, then the action
     across the foot - and moving the action above the language in the source
     would put a full-width filled button in the middle of a list of rows.
     One rule, one breakpoint, and the panel is untouched.
     IT MIRRORS BY ITSELF. `order` moves an item along the flex axis, and the
     axis follows `dir`: last means leftmost in Hebrew and rightmost in English,
     so the language switch sits at the outer end of the bar in both. No
     physical left or right is written here, which is the rule this file keeps
     everywhere. */
  .bar-end .lg{order:2}
}
/* Above the breakpoint there is room for the row, so the button is not there. */
.mb{display:none}
@media (max-width:63.99rem){
  /* nowrap: the bar is one row and nothing in it is allowed to start a second.
     z-index so the panel paints over the hero rather than under it - the hero
     sets its own stacking context and would otherwise win by being later. */
  .hd{flex-wrap:nowrap;padding:var(--s2) var(--s3);gap:var(--s3);
      position:relative;z-index:20}
  .brand{min-height:0}
  .brand svg{height:26px}
  .brand-d{line-height:1.15}
  .mb{display:block;flex:none}
  /* THE BUTTON. Outlined when shut, filled when open, so its state is visible
     and not only spoken. 44px in both directions, which is the minimum a thumb
     needs and the same floor every other control on this site is held to. */
  .mb > summary{display:inline-flex;align-items:center;justify-content:center;
     gap:var(--s2);min-height:44px;min-width:44px;padding-inline:var(--s3);
     list-style:none;cursor:pointer;color:var(--accent-ink);font-weight:700;
     border:1px solid color-mix(in srgb, var(--fill) 45%, transparent);
     border-radius:999px}
  /* Safari before 17 draws the marker through a pseudo-element instead. */
  .mb > summary::-webkit-details-marker{display:none}
  .mb > summary svg{inline-size:19px;block-size:14px;flex:none}
  .mb[open] > summary{background:var(--fill);color:var(--white);
     border-color:var(--fill)}
  .mb > summary:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
  /* THE PANEL. Absolute, so opening the menu covers the top of the page rather
     than shoving it down - a hero that jumps 300px when you tap a button reads
     as a page that broke. It carries the same three-pixel fill edge the bar
     does, so the two read as one object. */
  .bar-nav{display:none;position:absolute;inset-inline:0;top:100%;
     flex-direction:column;align-items:stretch;justify-content:flex-start;
     flex-wrap:nowrap;gap:var(--s1);background:var(--white);
     border-block-end:3px solid var(--fill);
     padding:var(--s3) var(--s3) var(--s4);
     box-shadow:0 14px 26px -14px color-mix(in srgb, var(--ground) 55%, transparent)}
  .mb[open] ~ .bar-nav{display:flex}
  .bar-nav .nv ul{flex-direction:column;flex-wrap:nowrap;gap:var(--s1);width:100%}
  /* Full-width rows, text at the reading edge, 48px tall. A centred link in a
     stacked menu gives the eye no left-hand rail to run down. */
  .bar-nav .nv a{justify-content:flex-start;width:100%;min-height:48px;
     padding-inline:var(--s3);border-radius:8px}
  /* 🔴 THE PANEL COULD OUTGROW THE SCREEN WITH NOTHING TO SCROLL.
     22 September: 363px tall with `overflow:visible` and no maximum. It fits a
     320x568 phone and it does not fit one on its side, and it will not fit a
     reader who has raised their text size - and the rows past the bottom were
     simply unreachable. The bar is 65px, so `100vh - 5rem` leaves the panel
     everything below it and a margin. */
  .bar-nav{max-block-size:calc(100vh - 5rem);overflow-y:auto;
     overscroll-behavior:contain}
  /* The one ACTION in the menu was the shortest row in it: 44px against the
     four page rows' 48. */
  .bar-nav .nav-go{min-height:48px}
  .bar-nav .nv a[aria-current="page"]{border-block-end:0;
     background:color-mix(in srgb, var(--accent) 8%, var(--white))}
  /* IN THE PANEL THE ORDER IS THE DOM ORDER AGAIN: four rows, the language,
     then the action across the foot. `li:last-child` used to catch the action
     here too and no longer can, because it is not in the list. */
  /* 🔴 THE LANGUAGE ROW SITS AT THE PAGE'S EDGE, NOT AT ITS OWN. The anchor
     carries dir="ltr" - it has to, or `English` reads backwards inside a Hebrew
     page - and a full-width flex box aligned to ITS OWN start put the word at
     the far LEFT of the panel while every Hebrew row sat at the right.
     So the alignment is done by `.lg`, which inherits the PAGE's direction, and
     the anchor is only as wide as its word. Both languages now start their rows
     at the same edge. */
  .bar-nav .lg{display:flex;justify-content:flex-start}
  .bar-nav .lg a{width:auto;min-height:48px;
     padding-inline:var(--s3);border-radius:8px}
  .bar-nav .nav-go{justify-content:center;width:100%;margin-block-start:var(--s3)}
  /* In the panel the end group is a column like everything else in it. */
  .bar-end{flex-direction:column;align-items:stretch;gap:var(--s1);width:100%}
}

/* ── EVERY HERO INSIDE ONE BAND, ON A PHONE ────────────────────────────────
   MEASURED FIRST, at 390x844 with the old bar and the old type: the five
   heroes were 88%, 61%, 53%, 47% and 39% of the screen. On a laptop that reads
   as variety. On a phone it reads as five different websites, and the tallest
   filled the screen so completely that a reader had no sign the page went on.
   Three numbers do the work, and none of them crops a photograph.
     A FLOOR of 420px, so the two word-only heroes stop looking like a
     paragraph that happens to be purple.
     TIGHTER SPACING, so the tallest one leaves room under itself: the block
     padding and the gaps between the five parts of the hero come down a step.
     A SMALLER HERO HEADLINE than a section heading, which is what the desktop
     hero has always done and the phone never did. The English home headline is
     84 characters and was landing in five lines; at 24px it lands in three.

   AND THIS BLOCK SITS *AFTER* `.op.plain`, WHICH IS THE ONLY REASON IT WORKS.
   A media query carries no extra specificity, so `.op.plain{min-height:0}`
   further up the file was quietly beating an identical rule written earlier.
   Sixth time this file has been bitten by a later rule undoing an earlier one:
   .founder columns, align-items twice, .beside font, .home .beside font, the
   .kit margin shorthand, and now this. */
@media (max-width:63.99rem){
  /* 440, NOT 420, AND THE SUM IS THE REASON. check-mobile holds the five
     heroes inside 1.75x of each other. The home hero takes its photograph's own
     shape on a phone, which is 760px on a 430px screen, and 760/420 is 1.81.
     760/1.75 is 434, so the floor is 440 and the band holds with room. */
  .op,.op.plain,.op.scene,.op.duo{min-height:440px}
  .op,.op.plain,.op.scene{padding-block:var(--s5)}
  .op.duo .duo-words{padding-block:var(--s5)}
  /* Every gap inside the hero comes down one step on the scale. */
  .op > :not(.hero-img){margin-block-end:var(--s3)}
  .op h1{margin-block-end:var(--s4)}
  /* (the hero's last block loses its bottom margin at every width now) */
  /* The lockup was 46px at every phone width, because 9vw only overtakes its
     floor at 512px. Same fault as the type scale had, and the same fix. */
  .hero-mark{margin-block-end:var(--s4)}
  .hero-mark svg{height:clamp(38px,7.5vw,72px)}
  /* 🔴 THE TOP OF THIS CLAMP WAS 34px AND h2 IS 30.4px AT 768, 22 September.
     Measured on nine of the ten pages at 768: h1 30.37px, h2 30.40px - a
     difference of THREE HUNDREDTHS OF A PIXEL, with 62 elements inside a
     0.45px band. There was no page title on a tablet; there was a stack of
     equal headings. The step the scale asks for is 1.25, so the h1 has to
     clear 38px where the h2 is 30.4.
     26px at 320 to 44px at 1023, same two-point line as the rest of the scale:
     slope (44-26)/703 = 2.5605vw, intercept 26 - 0.025605 x 320 = 17.81px.
     At 768 that is 37.5px against 30.4 = 1.23, and at 800 it passes 1.25. */
  /* 🔴 ON THE SCALE, 22 September. This was its own clamp, put here to clear
     the h2 at 768 when the two were three hundredths of a pixel apart. The
     rebuilt `--xxl` clears it by 1.33 at 768 and 1.45 at 1280 on its own, so
     the page title is the scale's own top step at every width instead of a
     fourth display size nobody could tell from the other three. */
  .op h1{font-size:var(--xxl)}
  .op .hero-img{margin-block-start:var(--s4)}
  /* THE STRETCHER PICTURE, CAPPED. Stacked, its 5:4 crop is 312px tall at
     390px and 614px at 768px, which alone put that hero at 93% of the screen.
     The cap is on the CELL, and object-position keeps the hands in it. */
  .op.duo .hero-img{max-height:300px}
  /* ── THE INJURY HERO IS A CARD, AND THE WORDS ARE ON THE PICTURE ────────
     Admin, 9 September: the headline goes on the photograph on a phone too.
     It could not before. The wide file is 1600x905, which at 390px stands 220px
     tall, and a headline needs about 120 of them: measured 1.94:1, unreadable.
     THE PHONE CROP IS WHAT CHANGED IT. 1400x1045 fills a 440px card, so there
     is room under the words for a ground to rise into - the same edgeless
     gradient the desktop card uses, darkening the pavement and leaving the
     faces and the whole of the shadow alone.
     check-hero-contrast measures the result against the pixels actually
     painted at 360px, which is the only test that counts. */
  /* A LOWER FLOOR ON THIS ONE, AND THE SUM THAT PICKED IT. The 420px minimum
     every other hero takes left about 160px of empty dark under the headline,
     because a card sized to a picture plus one line is naturally shorter than a
     hero built of five paragraphs. With no floor at all it fell to 301px, and
     the tallest hero on an English phone is 627, which is 2.08x - outside the
     1.75 the five heroes are held to. 627 / 1.75 is 358, so the floor is 380:
     under 40px of space under the headline instead of 160. It moved again to
     440 when the home hero took its phone photograph's own height: see the
     floor above for that sum. */
  .op.scene{position:relative;isolation:isolate;
            background:var(--ground-lo);color:var(--white);min-height:440px;
            /* 🔴 FULL BLEED ON A PHONE, 22 September, AND A MEASUREMENT
               FORCED IT. As a card on the page gutter the headline sat in a
               240px column at 320px wide, and `בבית, אבל לא באמת` measures
               250px at the rebuilt scale's 30px floor - it took two lines, and
               check-mobile allows a 17-character heading exactly one.
               Full bleed gives it the page's own 24px gutter and a 272px
               column, which holds it with 22px to spare. It also removes the
               last of the three different side margins this page had on one
               screen: the bar at 16, the card at 15.6 and the text at 24 are
               now one number.
               THE CARD IS STILL A CARD ABOVE 64rem, where Admin asked for it
               on 9 September - all four corners visible, rounded, inset from
               the window. On a phone a hero photograph runs to the edges, the
               way the home page's already does. */
            margin-inline:calc(50% - 50vw);border-radius:0;overflow:hidden;
            padding:var(--s5) 0;justify-content:flex-end}
  .op.scene .hero-img{position:absolute;inset:0;z-index:-2;margin:0;
            width:100%;height:100%;object-fit:cover;object-position:center 40%;
            max-inline-size:none;max-height:none;border-radius:0}
  .op.scene::after{content:"";position:absolute;inset:0;z-index:-1;
     background:linear-gradient(to top,
       color-mix(in srgb, var(--ground-lo) 90%, transparent) 0%,
       color-mix(in srgb, var(--ground-lo) 66%, transparent) 30%,
       color-mix(in srgb, var(--ground-lo) 22%, transparent) 62%,
       transparent 88%)}
  /* The page's own gutter, so the headline starts where every sentence under
     it starts. */
  .op.scene .scene-words{padding-inline:var(--s4)}
  .op.scene :is(h1,h2,p){color:var(--white)}
}

/* THE SPACE BETWEEN SECTIONS IS A DESKTOP RHYTHM. 104px under every section
   is a quarter of a phone screen of nothing, and on the Injury page it left
   about 160px of white between the photograph and the first sentence about it.
   Two steps down the same scale, on phones only. */
@media (max-width:63.99rem){
  section{margin-block-end:var(--s6)}
  section:last-of-type{margin-block-end:var(--s5)}
}
@media (max-width:63.99rem){
  /* 22ch is a cap for a headline that has a whole window to sit in. On a phone
     the column is already narrower than 22ch, so the cap only ever made the
     line shorter than the screen: it held the English home headline to 297px
     inside a 342px column and cost it a fifth line. */
  .op h1{max-width:none}
  /* THE PICTURE STOPS GROWING WITH THE WINDOW at the point where growing stops
     helping. Stacked above 520px it was 368px tall on a 768px tablet, which by
     itself put that hero at 92% of the screen. Capped and centred, nothing is
     cropped and nothing is letterboxed - the picture is simply smaller. */
  .op .hero-img{max-inline-size:520px;margin-inline:auto}
}

/* ── THE TWO DOORS AND THE FORM NEED MORE THAN THE READING COLUMN ─────────
   Both are side-by-side objects, and the reading measure came down to 464px on
   8 September, which is under the 544 that two 17rem tracks need. So the split
   silently collapsed to one column and Admin's two buttons stacked instead of
   sitting next to each other. Same treatment the four stages and the technology
   cards already get: the block breaks out of the column, the running text does
   not.
   AT THE END OF THE FILE, because these have to beat `main`'s own max-width and
   a media query carries no extra specificity. */
main > section > :is(.doors,.people){max-width:none}
.form-wrap{max-width:none}
/* 🔴 -150px GONE, 22 September. See `main`: the column is the rail. */

/* ── THE PROBLEM, IN THE STATE'S OWN NUMBERS ──────────────────────────────
   Admin, 9 September. A band between the films and Yuval, and it has one job:
   look official. So it is set as a record rather than as marketing - a plain
   band, a grid of equal cards, the figure large and the sentence under it in
   the register of the rest of the page, and the body that published each one
   named and linked on every card.
   THE FIGURE IS THE LOUD PART AND THE SOURCE IS ALWAYS VISIBLE. A statistic
   whose source is a footnote is a statistic a reader has to trust; one with the
   Comptroller's name under it is one they can open. */
/* 🔴 THE BAND WENT DARK AND CAME BACK, and both instructions are Admin's on the
   same day. "Make it with contrast" produced the deep purple ground; seeing it,
   "the statistic cards are too bold and aggressive, bring it back to the
   previous version, just add a bit more colour to the BG to give a little
   contrast".
   SO IT IS THE PALE WASH AGAIN, AT 14% RATHER THAN 8%. That is the whole of the
   note: enough colour that the band is visibly its own section, not so much
   that four cards about suicide arrive shouting. The white cards then sit on a
   ground that is clearly not the page, which is the contrast that was missing,
   and the hairline rules come back to close it top and bottom. */
.facts-band{background:color-mix(in srgb, var(--accent) 14%, var(--white));
            border-block:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
            margin-inline:calc(50% - 50vw);
            padding:var(--s6) max(var(--s4), calc(50vw - 560px));max-width:none}
.facts-band > h2{max-width:none}
.facts-band > .lede{color:var(--grey-lite);font-size:var(--sm);max-width:52ch}
/* TWO ACROSS, NOT THREE AND AN ORPHAN. With five cards auto-fit gave three and
   then two, which reads as a grid. With Ram's four it gave three and then ONE,
   and a single card alone on a second row reads as a mistake. Four cards want
   two rows of two, and the cards are now a title plus a paragraph rather than a
   number plus a line, so the wider column is what they wanted anyway. */
.stat-grid{list-style:none;display:grid;gap:var(--s4);padding:0;margin:var(--s5) 0 0;
           grid-template-columns:repeat(auto-fit,minmax(min(17rem,100%),1fr))}
/* TWO ACROSS, AND FOUR CARDS MAKE TWO ROWS OF TWO. It was three across for the
   day the 78% card was off the page; with it back, three columns leave the
   fourth alone on a second row, which reads as a mistake rather than as a grid.
   Auto-fit cannot decide this: it fits as many as will go, which is exactly how
   the five cards became three and then two. The count is the design. */
/* THREE ACROSS SINCE 2 OCTOBER, because there are three cards (issue 135).
   The note below is the four-card reasoning and it still holds: the count is
   the design, and auto-fit cannot decide it. Two columns over three cards left
   the third alone on a second row, which is the exact failure that note
   describes. */
@media (min-width:48rem){
  .stat-grid{grid-template-columns:repeat(3,1fr)}
}
@media (min-width:48rem) and (max-width:63.99rem){
  .stat-grid{grid-template-columns:repeat(2,1fr)}
  .stat-grid > .stat-split{grid-column:1 / -1}
}
/* THE CARD KEEPS THE elem CORNER AND GIVES UP THE REST. 24px still reads as a
   shape somebody chose rather than a box, which is what "more circle" asked
   for; the hairline comes back because the ground behind it is pale again and
   a white card on a pale wash needs an edge. */
.stat-grid > li{background:var(--white);border-radius:24px;min-width:0;
                border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
                color:var(--ink);
                padding:var(--s5);display:flex;flex-direction:column}
/* 🔴 NO DISC. Admin, 22 September: "I don't like that the numbers of statistics
   are on bubbles." The figure is a run of brand purple inside the sentence
   again, which is how it read before that morning. accentInk and not accent:
   the pale accent is a dark-ground colour and measures 2.63:1 on white.
   The counting machinery below is untouched - what changed is the shape around
   the number, not how it arrives. */
.stat-n{color:var(--accent-ink)}
/* THE CARD NOW HAS A TITLE, AND THAT IS THE WHOLE OF Ram's note. It was a
   number and then a sentence, and a reader had to assemble the claim from the
   two. Now the figure sits above a heading that states the claim on its own -
   `40%`, then `זינוק במקרי פוסט־טראומה מאובחנים` - and the sentence under it
   explains rather than announces.
   THE FIGURE IS NOT INSIDE THE HEADING, and check-mobile is why. It allows a
   heading one line per 18 characters; a figure set as a block inside the
   heading forces a line break the count does not know about, so every card
   reported one line too many. Two elements, one visual sentence. */
/* THE FIGURE IS INSIDE THE TITLE NOW, AND IN THE BRAND PURPLE. Admin,
   15 September: the title has to say the whole thing on its own. It was a
   figure standing alone over a separate sentence, and a reader had to join the
   two to get the claim. `זינוק של 40% במקרי פוסט־טראומה מאובחנים` is one
.stat-n{font-weight:800}
   INLINE, NOT A BLOCK. As a block it forced a line break the heading-length
   check does not know about and every card reported one line too many.
   accentInk and not accent: the pale accent is a dark-ground colour and
   measures 2.59:1 on this white. accentInk measures 7.01:1, and
   check-rendered-contrast reads the pixels rather than this sentence. */
.stat-h{margin:0 0 var(--s3);font-size:var(--lg);font-weight:800;line-height:1.3;
        color:var(--ink);max-width:none}
.stat-n{font-weight:800}   /* the colour is set with the disc above; a later colour here would undo it */

/* ── THE FIGURES COUNT UP, AND THEY DO IT WITH NO JAVASCRIPT ─────────────────
   Admin, 22 September: "Add animation to the statistics card that number loads
   to statistics as on elem (only the numbers)".

   🔴 THIS IS THE SECOND THING ON THIS SITE THAT MOVES, and it is allowed by
   decision 0056 rather than by nobody noticing. Read that file before adding a
   third.

   HOW IT WORKS WITHOUT A SCRIPT. `@property` registers --stat as an integer, so
   a browser can interpolate it; `counter-reset` turns that number into text in
   a pseudo-element; `animation-timeline: view()` starts it when the card comes
   into view rather than on load, which matters because these cards are four
   screens down and a load-triggered count finishes before anybody sees it.

   THE REAL NUMBER NEVER LEAVES THE DOM. `.stat-lit` holds it as text. That is
   what a screen reader announces, what a browser with no support for any of
   this displays, and what a reader who asked for no motion sees. The animation
   only ever hides it visually, using the same clip technique as `.vh`, which
   assistive technology still reads - not `visibility:hidden`, which it does not.

   WHAT THE CONTRAST CHECK SEES. check-rendered-contrast walks text nodes and so
   measures `.stat-lit`, not the pseudo-element. That is sound rather than a gap:
   `::after` inherits `color` from `.stat-n`, so the measured literal and the
   painted counter are the same colour by construction. If that ever stops being
   true, the literal is the one to change.

   WCAG 2.2.2 asks for a pause only where motion runs over five seconds. This
   runs once, for 1.4s, and never repeats, so there is nothing to pause. */
@property --stat{syntax:"<integer>";initial-value:0;inherits:false}
@keyframes stat-count{from{--stat:0}to{--stat:var(--to)}}
@media (prefers-reduced-motion:no-preference){
  @supports (animation-timeline:view()){
    .stat-n{position:relative}
    .stat-lit{position:absolute;width:1px;height:1px;overflow:hidden;
              clip-path:inset(50%);white-space:nowrap}
    .stat-n::after{content:counter(stat) attr(data-suffix);
              counter-reset:stat var(--stat);
              animation:stat-count 1.4s ease-out both;
              animation-timeline:view();
              animation-range:entry 20% cover 35%}
    /* 🔴 ON A PHONE THE COUNT WAS OVER BEFORE THE CARD WAS THERE, Admin
       23 September: "the numbers need to run smoothly, they do not have
       counting on mobile."
       THEY DO COUNT - measured at 390px mid-scroll the four figures read 78,
       40, 277 and 16 while their cards were entering. What they do not do is
       count WHERE A READER IS LOOKING. `entry 20% cover 35%` is a range
       written for a desktop, where four cards sit in one row and enter
       together; on a phone the cards are stacked and full width, so a card
       finishes entering while it is still at the bottom of the screen and the
       whole count is over down there. By the time a thumb brings it to the
       middle the number has been sitting at its final value for half a screen.
       `entry 0% cover 55%` spans the card's whole arrival AND the first half
       of its time on screen, so the figure is still moving when the card is
       where the eye is. Nothing else changes: it is still driven by the
       reader's own thumb, it still stops when they stop, and
       `prefers-reduced-motion` still removes it. */
    /* 🔴 THE FIGURES DO NOT COUNT ON A PHONE AT ALL, Admin 23 September, and
       this replaces yesterday's change to where they counted rather than
       adding to it. He asked for the range to be widened, looked at it, and
       asked for the counting to come off the phone entirely.
       THE NUMBER A PHONE SHOWS IS THE REAL ONE IN THE DOM. `.stat-lit` is the
       figure as text; on every other screen it is hidden by clipping, which is
       the technique a screen reader still reads. Here the clip comes off and
       the pseudo-element that paints the counter is removed, so what a phone
       renders is the same element a screen reader has always announced. That
       is also exactly what `prefers-reduced-motion` produces, so the two paths
       are one path and there is one thing to get wrong instead of two. */
    @media (max-width:47.99rem){
      .stat-n::after{content:none;animation:none}
      .stat-lit{position:static;width:auto;height:auto;overflow:visible;
                clip-path:none;white-space:normal}
    }
  }
}
/* 🔴 `flex:1` GONE, 22 September. It bottom-anchored the source line, so in a
   row of two cards the gap above the source was 28px in one and 50px in the
   other while the two source lines sat on the same baseline - which a reader
   reads as one card with a dent in it. The leftover space now collects at the
   foot of the card, where it is padding. */
.stat-t{font-size:var(--sm);line-height:1.55;color:var(--ink);margin:0 0 var(--s4)}
/* THE SOURCE IS A NAME AND NOT A LINK, Admin 15 September. It is a caption now,
   so it no longer needs the 44px touch target a link owes a thumb. The links
   are not lost: archive/research/problem-statistics.md carries every one. */
.stat-s{margin:0;font-size:var(--xs);line-height:1.4;color:var(--grey-lite)}
/* QUOTED WORDS LOOK QUOTED, 4 October. The 65% figure is the Ministry of
   Defence's sentence, including a word this site bans in its own voice, so the
   page marks it as theirs rather than editing it. A browser's default marks for
   `q` are the English pair; Hebrew takes the same straight double mark at both
   ends, which is what the rest of this site's quoted material uses. Set on the
   element and not on `:root` so nothing else on the site changes shape. */
.stat-h q{quotes:"\0022" "\0022"}
/* THE HELP LINE IS PART OF THE SECTION, NOT DECORATION BESIDE IT. Decision
   0048: a page that names suicide and offers nothing does harm to the one
   reader it should most want to keep. Taking this line out means taking the
   figures out with it. */
/* 🔴 CAPPED, AND THE RADIUS IS ON THE SYSTEM, 22 September. At 1280 this was
   a 1120px slab holding 457px of text - 637px of empty dark, 57% of the bar -
   and it carried a 6px corner while a 360px statistics card beside it carried
   24px, so the widest box on the page had the smallest corner. */
.helpline{margin:var(--s5) 0 0;padding:var(--s4) var(--s5);border-radius:8px;
          background:var(--ground);color:var(--white);font-size:var(--md);
          line-height:1.5;max-width:max-content}
.helpline strong{color:var(--accent)}

/* THE TURN, AND THE CLOSE. Admin, 9 September: the line about getting under the
   stretcher is the loudest sentence on the page, and the page now ends on it. */
/* THE TURN CARRIES AN OPENING'S WEIGHT, Admin 22 September. xxl is the display
   step, the same one the home h1 takes, so the page has two moments set at that
   size and this is the second. The rule under every other h2 is suppressed: a
   48px bar above a line this large reads as a section label rather than as the
   sentence turning. */
.turn{font-size:var(--xxl);font-weight:800;line-height:1.1;letter-spacing:-0.015em;
      color:var(--accent-ink);margin:var(--s6) 0 var(--s4);max-width:20ch}
.turn::before{display:none}
/* No 20ch cap on this one. The English line is 49 characters and at 58px a
   20ch box gave it four lines; check-mobile refused it, because a heading gets
   one line for every 18 characters and no more. It takes the heading width the
   rest of the page uses. */
.close-h{font-size:var(--xxl);color:var(--accent-ink);max-width:none}
.close-h::before{display:none}
.close-sub{font-size:var(--lg);font-weight:800;line-height:1.3;
           color:var(--ink);margin:0 0 var(--s3)}
/* 🔴 `.close-ask`, NOT `.close-creed`, 22 September. The creed left the foot of
   the page when Admin settled where it lives; what closes the page now is the
   invitation, and the class says so. Same treatment, same place. */
.close-ask{font-size:var(--md);color:var(--accent-ink);margin:0 0 var(--s5)}

/* THE MARK AND THE DESCRIPTOR ON ONE LINE. They were a flex row already and
   still wrapped, because the band's own padding leaves them under 400px on a
   laptop once the mark is in front. A dot between them and a wider allowance
   keeps them together, and they still stack on a phone, where they must. */
.strip-mark{max-width:none;align-items:baseline}
.strip-mark span::before{content:"· ";color:var(--fill-dark)}

/* A HEADING GETS MORE WIDTH THAN A PARAGRAPH, and one heading is why.
   `הם עשו את שלהם, מעל ומעבר` is 25 characters, which at 40px is about 493px,
   and the reading measure came down to 464px on 8 September - so the last word
   dropped to a line of its own. Running text keeps the measure, because the
   measure is about reading a paragraph. A heading is read in one glance and
   wants to hold together. */
main > section > :is(h1,h2,h3){max-width:34rem}
h2{text-wrap:balance}

/* Two words carried in colour inside a heading, and a heading set in the brand
   purple. accentInk on white is 7.01:1 and check-rendered-contrast measures
   both where they land. */
.split-h .hl{color:var(--accent-ink)}
.purple-h{color:var(--accent-ink)}
.beat{font-size:var(--md);line-height:1.5}

/* ── THE INJURY HERO IS A CARD AT EVERY WIDTH ─────────────────────────────
   Admin, 9 September: all four corners of the photograph visible, corners
   rounded, and about a tenth smaller. Above 1024 the section used to take the
   file's own 1600x905 shape and fill it edge to edge, which meant `cover` and
   `contain` were the same thing - true, and only true while the section is
   exactly that shape. `contain` states it instead of relying on it, so a
   photograph swapped in later at a different shape still arrives whole.
   🔴 72vw BECAME THE RAIL, 22 September, AND THAT REVERSES A SIZE ADMIN SET.
   The 9 September instruction was "about a tenth smaller", and 72vw delivered
   it. What it also delivered was a fifth edge: at 1280 the card's own edge
   landed 179px from the window while the bar, the footer, every band and every
   other hero landed at 80, and a card that is the only object on the page not
   on the rail reads as a mistake however well-proportioned it is.
   WHAT ADMIN ASKED FOR IS KEPT - all four corners visible, rounded, inset from
   the window rather than bleeding to it. What changes is that the inset is now
   the same one the whole site uses instead of a number of its own.
   IT ALSO STOPS GROWING. At 72vw the card was 922px at 1280 and 1152px at
   1600; on the rail it is 1120px at both, so its height is 633px and stays
   633px instead of running to 652 and beyond on a wide screen. */
@media (min-width:64rem){
  .op.scene{margin-inline:0;border-radius:8px}
  .op.scene .hero-img{object-fit:contain}
  /* Five board members, five columns. Eight pieces of equipment, four. Three
     films, three. Each of these was `auto-fit` and each left one empty cell. */
  .people{grid-template-columns:repeat(5,1fr)}
  .gear{grid-template-columns:repeat(4,1fr)}
  .films ul{grid-template-columns:repeat(3,1fr)}
  .roster{grid-template-columns:repeat(5,1fr)}
}

/* ── EQUIPMENT AND TECHNOLOGY, AS A SPECIFICATION LIST ────────────────────
   Admin, 9 September. A description list rather than cards: eight things, each
   a name and one line, read down rather than across. A hairline between rows
   and nothing else, because a specification sheet earns its authority by being
   plain. */
/* SMALL CARDS ON A LIGHT PURPLE, Admin 9 September. It was a list of hairline
   rows, which read as a specification and not as a set of things. Eight cards
   on the same pale accent the other bordered blocks use, so the section reads
   as an inventory a reader can scan rather than a document they have to work
   down.
   min() on the track floor so a 320px phone can never be given a 240px minimum
   it does not have: the same guard the four stages and the statistics grid use. */
/* margin-BLOCK, not the margin shorthand. The shorthand sets all four sides, so
   it silently reset the -150px breakout set for this class at 58rem and eight
   cards stacked one per row in a 464px column. Second time this file has been
   bitten by exactly that, after .kit. */
/* 🔴 NOTHING ON THE SITE USES `.gear` OR `.kit-list` SINCE 23 SEPTEMBER. Admin
   removed the equipment section from the Treatment page whole, and it was the
   only place either of them appeared. The rules are kept rather than deleted
   because the section may come back - the eight devices still exist and
   `archive/research/devices.md` still lists them - and because the phone
   treatment below took a measurement to arrive at. If it is still unused when
   the evidence component is built, delete both. */
.gear{display:grid;gap:var(--s4);margin-block:var(--s5) 0;max-width:none;
      grid-template-columns:repeat(auto-fit,minmax(min(15rem,100%),1fr))}
.gear > div{min-width:0;border-radius:8px;padding:var(--s4);
            background:color-mix(in srgb, var(--accent) 8%, var(--white));
            border:1px solid color-mix(in srgb, var(--fill) 22%, transparent)}
.gear dt{font-weight:800;font-size:var(--md);line-height:1.3;color:var(--ground);
         margin:0 0 var(--s2)}
.gear dd{margin:0;font-size:var(--sm);line-height:1.55;color:var(--ink)}
/* 🔴 THE DETAIL THAT IS THERE WITHOUT ASKING FOR ATTENTION, 23 September.
   Admin asked for copy that "gives the reader the idea and not too much
   detail", and the densest thing in this section is the home kit's five device
   names - vibroacoustics, rhythm pacing, deep pressure, calming virtual
   reality and photobiomodulation. They are also the ONLY place those five are
   stated anywhere on the site, so deleting them deletes a fact rather than
   softening a sentence. They stay, one step quieter: the reader gets the idea
   from the first two sentences and the list is there for the one who wants it.
   greyLite on white measures 7.04:1, which clears AAA. */
.kit-list{display:block;margin-block-start:var(--s2);
          color:var(--grey-lite);font-size:var(--xs);line-height:1.5}
/* Who runs the stages, said once above them. It reads as a note rather than as
   a step, which is what it is. */
.who-line{font-weight:700;color:var(--accent-ink);font-size:var(--sm);
          line-height:1.5;border-inline-start:3px solid var(--fill-dark);
          padding-inline-start:var(--s3);margin:0 0 var(--s4)}

/* The technology manifesto: running text set a step up from body copy, because
   it is the page's argument rather than its detail. */
.manifest{max-width:none;margin:var(--s5) 0 var(--s4)}
.manifest p{font-size:var(--md);line-height:1.6;margin:0 0 var(--s4);
            max-width:var(--measure)}
.manifest p:last-child{margin-block-end:0;color:var(--accent-ink);font-weight:800}

/* A BUTTON INSIDE THE PURPLE BAND KEEPS ITS OWN COLOURS. `.strip-on a` was
   written for a plain link on that dark ground and sets `accent`, which is a
   dark-ground colour; on the button's white pill it measures 2.63:1 against the
   4.5 the standard asks. Found by check-rendered-contrast, which reads what
   actually renders rather than what a class is called. */
.strip-on .btn-line{color:var(--accent-ink)}
.strip-on .btn::after{content:none}

/* THE STAT GRID IS AN <ol>, AND THAT IS WHY IT WAS ONE COLUMN WIDE. The home
   page caps every ol at the reading measure, which is right for a list of
   sentences and wrong for a grid of cards: 464px fits one 17rem track, so six
   cards stacked in a column inside a band 1120px wide.
   THE HOME SELECTOR IS REPEATED HERE ON PURPOSE. `.home main > section > ol`
   outranks `main > section > .stat-grid` on specificity, so writing this rule
   later in the file was not enough - the same trap this file has now hit eight
   times, in the one direction where being last does not help. */
.home main > section > :is(.stat-grid,.helpline,.lede),
main > section > :is(.stat-grid,.helpline){max-width:none}

/* ── THE DETAILS BAND, AS ONE ROW ─────────────────────────────────────────
   Admin, 9 September: the mark, the number, who it is for and the button side
   by side. A flex row with `space-between`, so `dir` decides which end holds
   the mark and the English page mirrors it with no physical left or right
   written anywhere.
   It WRAPS rather than shrinking: four items on one line need about 900px, and
   below that they fall into two rows and then four, which is what a phone
   needs. Nothing is hidden and nothing is truncated at any width. */
/* 🔴 THE FOUR THINGS IN THIS ROW WERE NOT ON ONE LINE, Admin 23 September with
   a screenshot. They were centred on each OTHER - `align-items:center` puts the
   middle of each box on one line, and the four boxes are different heights
   because one of them holds a 30px mark and the others hold a single line of
   type. Centred boxes means staggered text: the name sat highest, the registry
   line a little lower, the eligibility sentence lower again.
   `baseline` puts the TYPE on one line, which is what a reader sees. The button
   keeps `center`, because a 53px pill hung from its own text baseline sits
   below everything else. */
.strip-row{display:flex;flex-wrap:wrap;align-items:baseline;
           gap:var(--s3) var(--s5);padding-block:var(--s4)}
.strip-row > .strip-on{align-self:center}
.strip-row > *{margin:0;min-width:0}
.strip-row .strip-mark{margin:0;flex:0 1 auto}
.strip-fact{font-size:var(--sm);line-height:1.4;color:var(--white)}
.strip-fact > span{color:var(--accent)}
.strip-fact strong{font-weight:800}
/* The eligibility line takes what is left, so it breaks before the button
   does: it is the longest item and the one that may not be cut. */
.strip-who{flex:1 1 16rem;color:var(--accent)}
.strip-row .strip-on{margin:0;flex:0 0 auto}

/* A FILM THAT PLAYS IN PLACE. The frame keeps 16:9 with aspect-ratio rather
   than the old padding trick, so it holds its shape before it loads and the
   band does not jump. Same border and radius as the poster tiles beside it, so
   a row of three reads as one set whether each is a player or a link. */
/* ── ONE TILE DESIGN FOR ALL THREE FILMS ──────────────────────────────────
   Admin, 9 September: same design and same view whether a film plays here or
   opens on YouTube. So `details.film` is styled as the tile exactly as
   `.films li > a` is, and the caption rule below is shared by both so the two
   cannot drift apart.

   clip-path, NOT overflow:hidden, AND THAT IS NOT A PREFERENCE. Measured in
   Chrome 149: `overflow:hidden` on a <details> stops it sizing to its own
   <summary> - the summary measured 278px tall and the details around it 201,
   so the caption was laid out and then clipped away. clip-path rounds the
   corners identically and does not touch layout at all. */
/* THE <li> IS THE TILE for the film that plays, because its caption sits
   outside the <details> - see the template for why it has to. It carries the
   same border, ground and radius as the anchor tiles beside it. */
.films li.film-li{color:var(--white);background:var(--ground-lo);
         border:1px solid color-mix(in srgb, var(--fill-dark) 55%, transparent);
         border-radius:8px;clip-path:inset(0 round 8px)}
.films .film{display:block}
.films .film > summary{display:block;cursor:pointer;list-style:none}
.films .film > summary::-webkit-details-marker{display:none}
.films .film > summary:focus-visible{outline:2px solid var(--accent);outline-offset:-3px}
/* Opened, the poster gives its place to the player rather than sitting above
   it: two 16:9 boxes stacked would double the tile's height the moment somebody
   pressed it and push the rest of the band down the page. */
.films .film[open] > summary .poster{display:none}
/* THE SHAPE IS ON THE FRAME, NOT ON A BOX AROUND IT, and check-no-images is
   why: with aspect-ratio on the wrapper, a page whose media does not load kept
   a 16:9 empty box where the player should be, which is exactly the hole
   decision 0009 says a page must close. */
.film-frame{line-height:0}
.film-frame iframe{display:block;width:100%;aspect-ratio:16/9;border:0}
/* ONE CAPTION RULE FOR BOTH TILES. A link tile and a player tile read the same
   because this is the same class and the same declaration, not two that happen
   to match today. */
.films .film-cap{display:block;margin:0;padding:var(--s3) var(--s4);
   font-weight:700;font-size:var(--md);line-height:1.3}
.films .film-cap small{display:block;font-weight:400;
   font-size:var(--xs);color:var(--accent);margin-block-start:2px}
/* Opened, the caption stops offering to play what is already playing. */
.films .film-li:has(.film[open]) .film-cap small{display:none}

/* ── THE FOUR STAGES, IN THE BRAND'S OWN COLOURS ──────────────────────────
   Admin, 9 September: more design on the two treatment sections, in the brand
   colours. The stages were an outlined box with a dark numbered disc; they are
   a card with a purple head band now, so the number and the stage name read as
   one object and four of them read as a sequence.
   The number sits in the band rather than above it, which is what turns four
   cards into a numbered order a reader can follow at a glance. */
.steps > li{padding:0;overflow:hidden;display:flex;flex-direction:column;
            background:var(--white);
            border-color:color-mix(in srgb, var(--fill) 45%, transparent)}
.step-n{margin:0;padding:var(--s3) var(--s4);background:var(--ground);
        display:flex;align-items:center;gap:var(--s3)}
.step-n span{inline-size:34px;block-size:34px;font-size:var(--sm);
             background:var(--fill-dark);color:var(--ground-lo)}
.steps h3{margin:0;padding:var(--s4) var(--s4) var(--s2);color:var(--ground)}
.step-lead{padding:0 var(--s4) var(--s5);margin:0;flex:1;
           font-weight:400;color:var(--ink);line-height:1.6}
/* A rule in the brand purple along the foot of each card, so the sequence has a
   base line running under it rather than four cards ending in nothing. */
.steps > li::after{content:"";display:block;block-size:4px;background:var(--fill-dark)}

/* THE EQUIPMENT CARDS take the same purple head treatment, at a smaller size:
   the name on the brand purple, the description on the pale ground under it.
   Same object as a stage card, one step quieter, so the two sections read as
   one page rather than two. */
.gear > div{padding:0;overflow:hidden}
.gear dt{margin:0;padding:var(--s3) var(--s4);background:var(--fill);
         color:var(--white);font-size:var(--sm)}
.gear dd{padding:var(--s4);color:var(--ink)}

/* ══ PHONES ONLY, ADMIN 9 SEPTEMBER ════════════════════════════════════════ */

/* ── A HERO PHOTOGRAPH MADE FOR A PHONE ───────────────────────────────────
   A landscape crop composed for a laptop is the wrong picture on a tall narrow
   screen, and no CSS invents a composition that fits one. So the home hero may
   carry a SECOND file, and <picture> chooses: the browser downloads one of
   them, never both. Decision 0049.

   THE COMPOSITION DECIDES WHERE THE WORDS GO, and this photograph says it
   plainly: the top half is empty studio white and the man and the shadow are in
   the bottom half. So the words sit at the TOP, in the space left for them, and
   the picture is whole underneath. Laid over the bottom, as the first attempt
   did, they landed on the man.

   AND THE WORDS ARE THE DEEP BRAND PURPLE WITH NO GROUND UNDER THEM, which is
   what Admin asked for on 7 September and what this file could not honour until
   there was a picture composed for it. The studio background measures within
   two points of pure white, so `ground` reads 18.52:1 on it and `accentInk`
   7.01:1. check-hero-contrast measures both against the pixels actually painted
   at 360px, not against this claim.

   NOTHING IS CROPPED. The section takes the file's own shape - the same trick
   the desktop hero uses with 2400/1150 - so cover has nothing left to trim.
   PHONES ONLY. At 48rem this stops: the crop is 792x1400, so on a 768px tablet
   it would stand 1357px tall and bury the page under it. */
@media (max-width:47.99rem){
  /* ── THE PHONE OPENING: WORDS, THEN THE PICTURE, THEN THE DEDICATION ─────
     Admin, 16 September. The words no longer sit ON the photograph at all.
     They sit above it, the picture is a band of its own, and the dedication
     closes the opening underneath it.
     🔴 THIS IS THE THIRD ARRANGEMENT AND THE FIRST ONE THAT IS NOT A
     COMPROMISE. Overlaying words on this crop only ever worked while the
     opening was short: the empty studio white is the file's top half, so every
     line added to the copy pushed the last one onto the man, and
     check-hero-contrast caught exactly that twice - 1.03:1 in September and
     1.00:1 when the third body line landed. Each time the answer was to shrink
     the photograph, and by then it was 173px wide on a 360px screen. Taking the
     words off the picture gives both of them the whole width.
     AND IT ENDS A RUNNING FIGHT WITH THE CONTRAST CHECK. Nothing is painted
     over a photograph here any more, so there is nothing left to measure.

     THE ORDER IS DONE WITH `order` AND NOT IN THE MARKUP. The <picture> is
     first in the source because on every wider screen it is a background, and
     `.hero-pic` is display:contents so the <img> itself is the flex item. Two
     numbers rearrange the column on phones and nothing above 48rem changes. */
  .op.op-mob{position:relative;isolation:isolate;overflow:hidden;
             background:color-mix(in srgb, var(--accent) 8%, var(--white));
             aspect-ratio:auto;min-block-size:0;
             justify-content:flex-start;padding-block:var(--s4)}
  /* 🔴 130% WIDE, AND THE CROP IS MEASURED OFF THE FILE RATHER THAN GUESSED.
     The picture was scanned: `hero-mobile.jpg` is 792x1400, the man and his
     shadow begin 47% down and span x=72 to x=788, whose centre is 54% of the
     width, not 50%.
     SO TWO NUMBERS COME OUT OF THAT SCAN.
     THE WINDOW IS 1.07 WIDE TO 1 TALL, ANCHORED AT THE BOTTOM. Any squarer and
     it cannot start as low as 47% and still reach the foot of the picture, so
     the empty studio comes back into the top of the frame - which is what the
     first attempt did. At this ratio the window holds the bottom 53% of the
     file and nothing else.
     AND THE PULL IS UNEVEN, BECAUSE THE SUBJECT IS. A symmetrical pull puts the
     FILE's centre on the screen's centre, which left the man and shadow sitting
     5% to one side. -14.8 and -5.2 put the SUBJECT's centre there instead, and
     still add up to the extra width.
     🔴 109%, WHICH IS ADMIN'S 5% BACK OFF THE 114%, AND THE TALLER WINDOW IS
     PAID FOR OUT OF THE MARGINS. A window at 0.99 rather than 1.07 is fifteen
     pixels taller at 430px wide and the English opening had no room for it, so
     the gap above the picture and the gap above the dedication each come down a
     step. The picture itself gives up nothing.
     AND 114% WAS NOT THE 130% FIRST ASKED FOR, for the same kind of reason: at
     130 the English opening measured 983px against a 938px bound at 430px wide,
     and 120 left it four pixels over. check-mobile holds the openings of one
     kind inside 1.75x of each other, and English says the same three lines in
     more words than Hebrew, so English sets the limit. The man is still about
     three times the size he was before this arrangement.
     PHYSICAL MARGINS, DELIBERATELY. Everything else in this file is written in
     logical properties so `dir` can mirror it; a photograph's composition is
     not mirrored by reading direction, and the phone hero is not flipped in
     either language. Left and right mean left and right here. */
  /* 🔴 THE TOP OF HIS HEAD WAS BEING CUT, Admin 23 September, and the
     arithmetic says why. The window is 1.07 wide to 1 tall and the file is
     792x1400, so `cover` shows 0.935 / 1.768 = 52.9% of the file's height and
     leaves 47.1% of it to choose from. Anchored at the BOTTOM the window
     therefore starts at exactly 47.1% - and the man's head starts at 47%.
     The crop edge and the top of his hair were the same line, which held at
     390px by a pixel or two and clipped at 430.
     85% rather than 100% starts the window at 40.5% instead, which is 6.6% of
     the file - about 92 source pixels - of clear air above him. What it gives
     up is the same 6.6% at the foot, and that is floor. The picture is not
     scaled, moved or flipped; only the window over it moves up. */
  .op.op-mob .hero-img{position:static;order:1;z-index:0;
             inline-size:114%;margin-left:-11.6%;margin-right:-2.4%;
             block-size:auto;max-block-size:none;max-inline-size:none;
             aspect-ratio:1.07;object-fit:cover;object-position:center 85%;
             margin-block:var(--s4) 0;border-radius:0}
  /* The dedication follows the picture, and it is the only thing that does. */
  /* The mark above the words on a phone, both centred: a lockup beside a
     sentence leaves the sentence about nine characters wide at 390px. Both
     directions are named, or the reverse set for English above would survive
     into the stack and put the mark under the words on one language only. */
  /* 🔴 THE CAP HAS TO BE RESTATED WHEN THE BLOCK STACKS. `flex-basis` governs
     the MAIN axis, so in a column it caps the height and the words take the
     full width. Measured between 640px and 767px, that ran to 79 characters a
     line in Hebrew and 93 in English, against the 75 the standard allows.
     check-mobile tests 320, 360, 390, 430, 768 and 1280 and would never have
     seen it: the fault lives entirely between two of its viewports. Admin asked
     for every size, so it is measured at every size. */
  /* 🔴 THE ROW IS A GRID NOW AND `flex-direction` HAS NOTHING TO TURN.
     23 September: this rule used to stack the block on a phone and stopped
     working the moment the row became a three-column grid - the three columns
     stayed, the English lockup is wider than a 320px flank can hold, and
     check-viewport measured 365px of content in a 320px window on every
     English phone. One column, and the mark sits above the words. */
  .lede-block{grid-template-columns:1fr;gap:var(--s4);
              padding-inline:var(--s4)}
  .lede-block > .lede-mark,[dir="ltr"] .lede-block > .lede-mark{grid-column:1}
  .lede-block > .lede-words{grid-column:1}
  /* 🔴 AND THE TWO LANGUAGES NEED DIFFERENT NUMBERS. `ch` is the width of the
     digit zero, and Hebrew glyphs are narrower than that by about a third: at
     58ch the Hebrew line measured 79 characters where the English measured 74.
     This file has been here before - the note on the hero column says the same
     thing, 72 Hebrew characters against 93 English in one 568px box. So the cap
     is 50ch in Hebrew and 58ch in English, and both land inside 75. */
  .lede-words{max-inline-size:min(50ch, 100%);margin-inline:auto}
  :root[lang="en"] .lede-words{max-inline-size:min(58ch, 100%)}
  [dir="ltr"] .lede-block{flex-direction:column}
  .lede-mark svg{height:44px}
  .lede-line{font-size:var(--md)}
  .lede-creed{font-size:var(--md)}
  /* 🔴 THE BUTTONS GO TO THE FOOT OF THE OPENING, Admin 23 September. They
     sat directly above the photograph, so the first thing under the promise
     was a pair of pills and the picture arrived after them - the two loudest
     objects in the band stacked on each other and the photograph read as
     something they were sitting on. Last now: the words, the picture, the
     dedication, then the two doors.
     `order` AND NOT THE MARKUP, because the markup is also what every wider
     screen uses, where the picture is a background and the buttons follow the
     words. One number, one breakpoint. */
  .op.op-mob .hero-go{order:3;margin-block-start:var(--s4)}
  .op.op-mob .dedication{order:2;font-size:var(--xs);
             margin-block:var(--s3) 0}
  .op.op-mob .hero-mark{margin-block-end:var(--s2)}
  .op.op-mob .hero-mark svg{height:32px}
  /* 🔴 THE NAME GOT BIGGER WHEN IT STOPPED CARRYING THE DESCRIPTION.
     22 September. `שח״ף ·` is four characters; at the size the whole heading
     needed it was the quietest thing in the opening. 32px at 390, and the
     description takes the size the heading used to have - 31 Hebrew characters
     at 21.8px measure about 278px in a 342px column, so it still lands on one
     line and the block is 69px where the three-line heading was 73. */
  /* 🔴 THE OPENING IS ON THE SCALE TOO, 22 September. The home page's title
     was 31.98px and the four inner pages' were 27.80px - 15% apart, and a
     reader clicking between them cannot see it. All of them are `--xxl` now,
     the description is `--lg` and the promise under it is `--md`, which is
     33.9 / 22.9 / 19.1 at 390: 1.48 and 1.20 between the steps. */
  .op.op-mob h1{margin-block-end:var(--s2)}
  .op.op-mob .hero-name{font-size:var(--lg);margin-block-end:var(--s3)}
  .op.op-mob .hero-h2{font-size:var(--md);margin-block-end:var(--s3)}
  .op.op-mob .hero-body{font-size:var(--xs);margin-block-end:var(--s2)}
  .op.op-mob .hero-body:last-of-type{margin-block-end:0}
}

/* ── THE TABLET BAND, WHERE THE HOME HERO IS STACKED ──────────────────────
   Between 768 and 1023 the home hero is words with the WIDE photograph under
   them, at full width: 434px of picture at 768. Ram's h2 and two body lines
   pushed the English hero to 894px, and check-mobile refused it twice over -
   the bar and hero filled 93.7% of a 1024-tall screen against a 92% bound, and
   the English heroes ran 2.03x apart against a 1.75x bound.
   THE PICTURE GIVES UP THE HEIGHT, AND IT IS NOT CROPPED FOR IT. `contain`
   inside a 300px cap scales the whole frame down; `cover` would have taken the
   134px off the bottom, which is where the man is standing. Home only: this is
   the only hero carrying a second crop, so `.op-mob` is the hook that does not
   touch the other four pages. */
/* ══ THE TABLET, 48rem TO 64rem ════════════════════════════════════════════
   🔴 768 WAS RUNNING PHONE RULES WITH THREE EXCEPTIONS, 22 September, which is
   why it read as a blown-up phone rather than as a tablet. It took the phone
   bar, the phone hero, the phone rhythm and single-column card grids, but the
   desktop statistics grid. Measured at 768: the bar was 65px tall with 496px
   of empty space between the mark and the menu button, three films sat in a
   2x2 grid with one hole in it, and five board portraits sat in two columns
   with a hole at the start of the second row.
   Three things change and nothing else: the bar takes desktop proportions, the
   two grids get a column count instead of guessing one, and the hero picture
   takes the same rail its own headline uses instead of floating centred. */
@media (min-width:48rem) and (max-width:63.99rem){
  .hd{padding:var(--s3) var(--s4)}
  .brand svg{height:34px}
  .films ul,.roster{grid-template-columns:repeat(3,1fr)}
  /* The picture was centred with 234px of white either side while the headline
     beside it hugged the rail - two edges, one above the other. */
  .op .hero-img{margin-inline:0;max-inline-size:none}

  /* EVERY NUMBER HERE WAS MEASURED, NOT GUESSED, and the first three guesses
     were wrong. The English hero stood at 894px against a 770px bound (1.75x
     the shortest hero on the site, 440px). Capping the picture at 300 took off
     12. Dropping the headline a step took off 12 more - the English headline
     was already on two lines, so the step bought only leading.
     The stack at 768, measured: 80 padding, 58 mark, 75 h1, 46 h2, 77 + 77
     body, 72 dedication, 294 picture, 96 of margins between them. The picture
     and the padding are the only parts that can give 120px without taking the
     words apart, so that is where it comes from. At a 200px picture it landed
     on 770.44 against a bound of 770.00, which is a fail: 170 leaves room that
     a font update will not immediately spend. */
  /* 🔴 AND THE PHONE SHARE CAME DOWN FROM 62% TO 48% WHEN THE BODY GAINED A
     THIRD LINE. The arithmetic, measured rather than guessed: the section is
     636px at 360px wide, the picture's own top 48% is empty studio, so with the
     box H pixels tall the man begins at 636 - 0.52H. The English words now end
     at 457px. 636 - 0.52H must be past that, which puts H under 344 - and 62%
     was 395. check-hero-contrast had already said so in its own way: the
     dedication measured 1.00:1, which is text on itself. */
  /* THE PADDING CAME DOWN A STEP WHEN THE BODY GAINED A THIRD LINE. Admin
     replaced the two-line body on 15 September and the English hero went to
     782px against a bound of 770 - 1.75x the shortest hero on the site. The
     band's own padding is the cheapest 32px on the page: it costs air around
     the block, not space between the lines a reader is actually reading. */
  .op.op-mob{padding-block:var(--s4)}
  /* THE GROUPING SPACING IS A WIDE-SCREEN LUXURY, AND THIS BAND CANNOT AFFORD
     IT EITHER. Setting the three groups apart cost 40px here; the English hero
     had four to spare and went to 782 against a bound of 770. Both gaps come
     back a step in this band only. The groups are still told apart, by the type
     rather than by the air. */
  .op.op-mob .hero-h2{margin-block-end:var(--s4)}
  .op.op-mob .hero-body + .dedication{margin-block-start:var(--s2)}
  /* 🔴 THE PICTURE TOOK THE COLUMN, 22 September. At a 170px height cap and
     `contain` it drew 300px wide and centred with 234px of white either side,
     under a headline that hugged the rail - two edges, one above the other,
     and the smallest picture on any page. The cap stays (it is what holds the
     opening inside the bound at this width); what changes is that the window
     is as wide as the column and the photograph fills it. */
  .op.op-mob .hero-img{max-height:230px;inline-size:100%;max-inline-size:none;
     margin-inline:0;object-fit:cover;object-position:center 42%}
  .op.op-mob .hero-mark svg{height:40px}
  /* 🔴 RAISED, 22 September, for the same reason as `.op h1`: at 768 this
     resolved to 29.95px against an h2 of 30.4px, so the home page's own title
     was SMALLER than every heading under it. 30px at 521 to 44px at 1023:
     slope (44-30)/502 = 2.7888vw, intercept 30 - 0.027888 x 521 = 15.47px. */
  .op.op-mob h1{font-size:clamp(30px, calc(15.47px + 2.7888vw), 44px)}
  /* 36.9 / 30.4 / 18.4 at 768. The description holds one line here too: 31
     Hebrew characters at 30.4px measure about 386px in a 720px column. */
  .op.op-mob .hero-name{font-size:var(--xl);margin-block-end:var(--s3)}
  .op.op-mob .hero-h2{font-size:var(--md)}
}

/* ── THE PORTRAIT SITS BETWEEN THE WORDS AND THE NAME ─────────────────────
   Admin, 9 September, on phones only: the three lines, then Yuval, then who he
   is. It reads as a caption that way round rather than as a picture with a
   label stuck under it.
   `display:contents` ON THE FIGURE IS WHAT MAKES IT POSSIBLE. The picture is a
   SIBLING of the figure while the lines and the attribution are INSIDE it, so
   no amount of `order` can put the picture between them. Dissolving the
   figure's own box lets all three become children of the same column, and then
   ordering them is ordinary. The reading order for a screen reader is the same
   three things in the same sequence. */
@media (max-width:33.99rem){
  .beside{display:flex;flex-direction:column;gap:var(--s4)}
  .beside .quote{display:contents}
  .beside blockquote{order:0;margin:0}
  .beside > img{order:1}
  .beside figcaption{order:2;margin-block-start:0}
}


/* ── THE FOUR SIGNS ───────────────────────────────────────────────────────
   Admin, 9 September: simple and professional, on both a phone and a laptop.
   So: a rule, a name in the brand purple, and the sentence under it. Nothing
   else. Four of them read as an observed list rather than as four paragraphs
   that happen to start in bold, and a reader scanning sees four names instead
   of one grey block.
   The rule is on the START edge, which `dir` puts on the right in Hebrew and
   the left in English without a physical side named anywhere. */
.signs{display:grid;gap:var(--s4);margin:var(--s5) 0 var(--s4);max-width:none}
.signs > div{border-inline-start:3px solid var(--fill-dark);
             padding-inline-start:var(--s4)}
.signs dt{font-weight:800;font-size:var(--md);line-height:1.3;
          color:var(--accent-ink);margin:0 0 var(--s2)}
.signs dd{margin:0;font-size:var(--sm);line-height:1.6;color:var(--ink);
          max-width:var(--measure)}
.signs-end{font-size:var(--md);line-height:1.5;margin:0}
.signs-end strong{color:var(--accent-ink);font-weight:800}
@media (min-width:58rem){
  .signs{grid-template-columns:1fr 1fr;gap:var(--s5) var(--s5)}
  .signs dd{max-width:none}
}

/* ── THE FIGURES, AS A RECORD RATHER THAN AS CARDS, ON A PHONE ────────────
   Admin, 9 September: fit the phone and stay professional. Five bordered cards
   one under another is a lot of chrome and a lot of scrolling for five facts -
   at 390px they ran past two screens. On one column the box around each one
   earns nothing, because a single column already separates them.
   So on a phone the cards become rows: a hairline between, the figure and the
   sentence in one block, the source under it. Less furniture, more record, and
   the whole set fits where three cards used to. */
@media (max-width:47.99rem){
  /* 🔴 THE CARDS KEEP THEIR WHITE GROUND ON A PHONE NOW, and this rule used to
     say the opposite. It stripped the card furniture - `background:none` and a
     hairline rule instead - to save height, which was right while the band
     behind them was a pale wash. The band is the deep purple since 22 September,
     and stripping the white left dark ink on a dark ground:
     check-rendered-contrast measured the English card at 360px as 1.05:1
     against the 4.5:1 the law requires. Not hard to read. Invisible.
     THE HEIGHT COMES BACK OUT OF THE PADDING AND THE GAP instead, which costs a
     reader air rather than the text itself. */
  .stat-grid{gap:var(--s4);margin-block-start:var(--s4)}
  .stat-grid > li{background:var(--white);border-radius:24px;
     border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
     padding:var(--s4);color:var(--ink)}
  /* The figure carries the weight and the sentence sits directly under it, so
     the eye lands on the number first and reads on without a gap. */
  .stat-n{font-size:var(--lg)}
  .stat-t{font-size:var(--sm);line-height:1.5;margin-block-end:var(--s2)}
  /* 🔴 THE SOURCE LINK KEEPS ITS 44px, and the attempt to shrink it was caught
     by check-viewport at 430px: 165x36 and 322x36. It is a standalone link in
     its own paragraph, so WCAG 2.5.8's "inside a sentence" exception does not
     reach it and EXPERIENCE.md's floor applies. The height saved here came from
     dropping the card furniture instead, which costs a reader nothing. */
  .stat-s a{color:var(--grey-lite)}
  .facts-band{padding-block:var(--s5)}
  .facts-band > .lede{font-size:var(--xs)}
  .helpline{margin-block-start:var(--s4);padding:var(--s3);font-size:var(--sm)}
}

/* ── RAM IS IN THE MANIFESTO, NOT ALSO IN THE ROW BELOW IT, ON A PHONE ────
   Admin, 9 September. His portrait and his name open the manifesto directly
   above this row; on a narrow screen the roster repeats the same face within
   one screen. Four faces, and he is the fifth already.
   THE WHOLE ITEM GOES, not just its caption. Hiding the words and keeping the
   picture was the 9 September first pass and it left a nameless face in a row
   where every other face has a name under it, which reads as a mistake. */
@media (max-width:47.99rem){
  .home .roster li:first-child{display:none}
}

/* ══ THE PHONE, 22 September ═══════════════════════════════════════════════
   Everything here came out of measuring all ten pages at 390x844. */
@media (max-width:47.99rem){
  /* 🔴 FIVE SIDE MARGINS ON ONE SCREEN, measured on the Injury page: the bar
     at 16, the hero card at 15.6, the body text at 24, the hero headline at
     39.6 and the bulleted list at 48. The bar was the odd one out by a whole
     step; it takes the page's own gutter now. */
  .hd{padding:var(--s2) var(--s4)}

  /* 🔴 THE WORD-ONLY HEROES WERE BOTTOM-HEAVY, NOT TOO TALL. Treatment and
     Transparency open with a 440px purple band whose last line of text ends at
     225px - 279px of empty dark UNDER it, 63% of the band, because the column
     packs to the top and the floor holds the rest open.
     THE FLOOR STAYS. Taking it off was tried and measured: the word-only
     heroes fell to 200-250px against the picture heroes' 440, which is 2.20x
     and check-mobile refuses anything past 1.75x - the five openings have to
     look like one object. So the same space is split above and below the words
     instead of pooling beneath them, which is the difference between a band
     that is generous and a band that is unfinished. */
  .op.plain{justify-content:center}

  /* 🔴 THE TWO HERO BUTTONS WERE UNEQUAL AND LEFT AN ORPHAN. 134px against
     166px, the pair ending 26px short of the row (34px in English). Two equal
     halves of the row, primary on the side the language starts from. */
  .op.op-mob .hero-go{display:grid;grid-template-columns:1fr 1fr;gap:var(--s3);
     margin-block:var(--s3) 0}
  /* 40px of side padding inside a 163px half-row leaves 83px for the label,
     and `הסיפור שלנו` does not fit in 83px - it wrapped to two lines and took
     29px of hero height with it. The pill keeps its height; only the air
     beside the word comes down, which is what a full-width button does not
     need in the first place. */
  .op.op-mob .hero-go .btn{min-inline-size:0;width:100%;padding-inline:var(--s3)}

  /* 🔴 THE OPENING FILLED 95% OF THE FIRST PHONE SCREEN, 96% in English -
     measured bar plus hero against 844px. A reader saw a photograph, a
     headline and no sign the page continued. The words are untouched and the
     photograph is untouched; what comes out is the air between the blocks,
     which is the cheapest height in the band. */
  .op.op-mob .dedication{margin-block-start:var(--s2)}

  /* 🔴 THE ONLY TINTED BLOCK THAT DID NOT REACH THE EDGE. The form band ran
     x=24 to x=365 while every other band ran 0 to 390, and its fields sat 25px
     deeper than the page's own column - two left edges, one above the other. */
  .form-wrap{margin-inline:calc(50% - 50vw);border-radius:0;border-inline:0;
             padding:var(--s5) var(--s4)}
  /* The submit was the quietest thing in the form: a 136px grey pill at the
     foot of a column of full-width fields. The two gates already do this. */
  .form-go .btn{width:100%}
  /* Hebrew put the two choices on one row and English staircased them. */
  .pick-row{display:grid;grid-template-columns:1fr 1fr}

  /* 🔴 THE QUOTATION BLOCK HAD THREE ALIGNMENTS STACKED IN ONE SECTION:
     the heading at the page edge, the quote lines 102px inside it in a
     shrink-to-fit centred box, and the caption inside a third box of its own.
     `align-items:center` was written for a two-column desktop and survived
     into the phone stack. */
  .beside{align-items:stretch}

  /* The portrait stopped 22px short of a column it could have filled. */
  .founder img{max-inline-size:100%}

  /* 🔴 THE BOARD APPEARED TWICE ON THE SITE IN TWO SHAPES: two columns of
     circles on the home page, one column on About with 210px of empty space
     beside every portrait and five rows running 1,138px. Two columns on both. */
  .people{grid-template-columns:repeat(2,1fr);text-align:center}
  .people li{grid-template-columns:1fr}

  /* Two statistics headings ended on a single stranded word. `balance` was set
     on h2 and the two elements that actually wrap on a phone are h1 and h3. */
  h1,h3,.stat-h{text-wrap:balance}

  /* The closing band takes the phone's own rhythm, and its button takes the
     width a thumb expects at the end of a page. */
  main > .on:last-child{margin-block-start:var(--s6);padding-block:var(--s5)}
  main > .on:last-child a{flex:1 1 auto;justify-content:center}
}

/* ══ THE PAGE'S DISPLAY MOMENTS SIT IN THE MIDDLE ═════════════════════════
   Admin, 23 September, naming the whole run from `מאחורי כל מספר עומד לוחם`
   down to the trust strip: it should be "on center of the page".
   WHAT HE WAS LOOKING AT, measured at 1280: the heading, the quotation, the
   photograph, the turn line and its button all hang on the rail at x=1200 and
   the block is capped at 820px, so everything sat against the right edge with
   380px of empty white down the left of it. On the rail that is correct for
   information - a reader runs their eye down one edge - and wrong for a moment
   the page is meant to stop on.
   SO THE PAGE NOW HAS TWO MODES AND THEY ARE NOT ARBITRARY.
     INFORMATION HANGS ON THE RAIL: the statistics, the equipment, the board,
     every section heading a reader scans past.
     A DISPLAY MOMENT SITS IN THE MIDDLE: the opening lede (Admin, 22
     September), this quotation, the turn line, and the trust strip.
   🔴 THE QUOTATION'S OWN LINES STAY HANGING ON THEIR RULE. The block is
   centred; the three lengths are not. They sit against a 3px brand rule, and
   text centred beside a rule that marks its edge reads as text that has come
   loose from it. The container moves, the typography does not.
   🔴 AND ONE THING IS LEFT AT THE RAIL THAT ARGUABLY BELONGS HERE: the closing
   section at the foot of this page - `התחלנו את הדרך` and its button - is the
   same kind of moment and Admin did not name it. It is one line to add if he
   wants the pair to match. */
/* `text-align` alone was not enough and the measurement said why: every one of
   these has a max-width of its own - the heading 544px, the turn line 626, the
   button row 464 - so the TEXT centred inside a box that was still hanging on
   the rail. The box has to move too. */
/* 🔴 THE OPENING'S LINES CENTRE ON EACH OTHER, NOT ON THE PAGE. Admin,
   23 September, listing the hero text with the lede and asking for both "on
   center of section".
   THE LEDE COULD GO ON THE PAGE'S CENTRE AND THE OPENING CANNOT, and the
   photograph is why. The man occupies roughly x 195 to 455 at 1280 and his
   shadow runs to 815; the page's centre line is 640, which is on him. The
   hero's words are the one block on this site whose position is not a
   composition choice - `check-hero-contrast` reads the pixels a browser
   actually painted behind every one of them, and the right half of this frame
   is the only half that clears the standard.
   SO THE BLOCK STAYS ON THE READING SIDE AND ITS LINES CENTRE WITHIN IT. Five
   things that were ragged down one edge - the name, the description, the
   promise, the dedication and the two doors - now share one 40rem box and one
   centre line, which is the composition Admin asked for, in the half of the
   photograph that can carry it. */
@media (min-width:64rem){
  /* NO AUTO MARGIN. In a column flex box a child that cannot stretch falls
     back to the start of the cross axis, which in Hebrew is the right - which
     is where these belong. `margin-inline-start:auto` put the free space on
     that side instead and shoved all five blocks LEFT onto the man in the
     photograph: check-hero-contrast measured 1.00:1 at x=283 within a minute,
     which is text on itself. */
  .home .op > :is(h1,.hero-name,.hero-h2,.dedication,.hero-go){
     max-inline-size:min(40rem,100%);text-align:center}
  .home .op > .hero-go{justify-content:center}
}

main > section:has(> .beside) > :is(h2,.turn,.on){text-align:center;
   margin-inline:auto}
main > section:has(> .beside) > h2::before{margin-inline:auto}
main > section:has(> .beside) > .beside{margin-inline:auto}
/* The strip is one row of four things and it was spread across the whole rail,
   which left the eligibility sentence and the button a long way apart with
   nothing between them. Centred as a group, the four read as one statement. */
.strip-row{justify-content:center}

/* ══ THE PHONE: LANDMARKS, AND A LIGHTER EQUIPMENT LIST ═══════════════════
   Measured on 22 September, full-width ground changes and the longest run of
   unbroken white on each page at 390px:

       Home     7 changes   1,770px  2.1 screens
       Support  5           840px    1.0
       About    5           2,301px  2.7
       Injury   3           3,889px  4.6
       Treatment 4          5,073px  6.0   (English 7.0)

   Length is not the fault - Treatment is 7.0 screens and Home is 8.5. The
   absence of landmarks is. Home changes ground every 0.93 screens and a thumb
   always knows where it is; Treatment changes it once in six.
   ONE SECTION PER LONG PAGE TAKES THE GROUND THE SITE ALREADY USES. No new
   colour, no new copy, nothing reordered: `:has()` finds the section that holds
   the equipment list on Treatment and the one that holds the signs list on
   Injury, and gives it the same pale band the press strip and the form use. */
@media (max-width:47.99rem){
  main > section:has(> .gear),
  main > section:has(> .signs){
    margin-inline:calc(50% - 50vw);
    padding:var(--s6) var(--s4);
    background:color-mix(in srgb, var(--accent) 8%, var(--white));
    border-block:1px solid color-mix(in srgb, var(--fill) 22%, transparent)}

  /* 🔴 EIGHT IDENTICAL PURPLE SLABS DOWN ONE COLUMN. The equipment list is
     eight items and each one carried a FILLED purple header band, which on a
     desktop is four cards in a row where the bands read as headers, and on a
     phone is eight full-width purple bands over about 1,800px - two screens of
     one shape repeating, and the strongest impression the page left.
     THE NAME KEEPS THE BRAND PURPLE AND GIVES UP THE FILL. A rule along the
     reading edge carries the same weight at a tenth of the ink, and the cards
     sit on the band's own ground rather than fighting it. */
  .gear > div{padding:var(--s4);background:var(--white);
     border-radius:8px;overflow:visible}
  .gear dt{margin:0 0 var(--s2);padding:0;background:none;
     color:var(--ground);font-size:var(--md);
     border-inline-start:3px solid var(--fill);padding-inline-start:var(--s3)}
  .gear dd{padding:0}

  /* 🔴 THE BOARD'S TWO COLUMNS HAD RAGGED BOTTOMS. Role text runs one to three
     lines, so two cards in a row ended up to 60px apart. Three explicit rows -
     portrait, name, role - start every name on one line and every role on one
     line, whatever each of them wraps to. */
  .people li{display:grid;grid-template-rows:auto auto 1fr;align-content:start;
     gap:var(--s2)}

  /* A headline underlined across four wrapped lines reads as four corrections.
     The card is the target on a phone and its own edge says so. */
  .news-list a .news-t{text-decoration:none}
}

/* 🔴 THE PAPER DOES NOT END WHERE THE SCREEN DOES. A full-bleed dark band at
   the foot of the page sits under the home indicator on a notched phone, and
   the registry line lands in the part of the glass the hardware owns. One
   inset, on the one element that touches the bottom edge. */
.ft{padding-block-end:calc(var(--s5) + env(safe-area-inset-bottom, 0px))}

/* ══ A SHORT SCREEN, STILL UPRIGHT ════════════════════════════════════════
   🔴 A 320px PHONE IS 568px TALL, NOT 844. 22 September. check-mobile renders
   320x844, which is a shape no phone has ever had; the device that is actually
   320 wide is the first iPhone SE, and it is 568 tall. Measured there, the home
   opening was 122% of the screen in Hebrew and 142% in English - the same fault
   the landscape block below fixes, on a phone held the normal way.
   THE PHOTOGRAPH STAYS HERE. There is enough height for it; what it cannot have
   is its own full crop window, which is as tall as it is wide. 30vh of a 568px
   screen is 170px, and the window keeps its bottom anchor, so what comes out of
   it is the man and his shadow rather than the empty studio above them. The air
   between the blocks comes down a step with it. */
@media (min-height:30.01rem) and (max-height:40rem) and (max-width:47.99rem){
  /* 🔴 AND THE CROP MOVES WITH THE WINDOW. The file's window is anchored at
     the BOTTOM, which is right when it is as tall as it is wide: it holds the
     man and his shadow and leaves the empty studio above them out. Shortened
     to 30vh the same anchor holds only the bottom band of that - his legs and
     his feet, with his head cut off. 70% puts the window back over him. */
  .op.op-mob .hero-img{max-block-size:30vh;margin-block-start:var(--s3);
     object-position:center 70%}
  .op.duo .hero-img{max-block-size:34vh}
  .op.op-mob{padding-block:var(--s3)}
  .op.op-mob h1{margin-block-end:var(--s1)}
  .op.op-mob .hero-name{margin-block-end:var(--s2)}
  .op.op-mob .hero-h2{margin-block-end:var(--s2)}
  .op.op-mob .hero-go{margin-block-start:var(--s3)}
  .op.op-mob .dedication{font-size:var(--xs);margin-block-start:var(--s2)}
}

/* ══ A SHORT SCREEN: A PHONE HELD SIDEWAYS ════════════════════════════════
   🔴 EVERY BREAKPOINT IN THIS FILE IS A WIDTH, AND A PHONE ON ITS SIDE IS
   WIDE AND SHORT. 22 September. Measured before this block existed, the
   opening against the screen it sits in:

       844x390   Home 181%   the four inner pages 136%   English Home 196%
       736x414   Home 272%   the four inner pages 122%   English Home 286%
       568x320   Home 296%   the four inner pages 158%   English Home 314%

   At 844 wide the page was handed the TABLET layout at desktop type sizes in a
   390px-tall window; at 736 and 568 it was handed the phone layout, whose 440px
   floor is by itself 136% of a landscape screen. Either way a reader saw a
   headline and no sign the page continued, and on the home page scrolled three
   screens to get past the opening. `check-mobile` renders six shapes and all
   six are portrait, so nothing caught it.

   THE RULE IS A HEIGHT, WHICH IS THE THING THAT IS ACTUALLY SCARCE. 30rem is
   480px: it catches every phone on its side and it also catches a short
   desktop window, where the same reasoning applies.
   NOTHING IS HIDDEN AND NO WORD IS DROPPED. The floors come off, the display
   sizes come down two steps, the photograph is capped against the screen
   rather than against the width, and the air between the blocks tightens. */
@media (max-height:30rem){
  .op,.op.plain,.op.scene,.op.duo,.op.op-mob{min-height:0;min-block-size:0;
     aspect-ratio:auto;padding-block:var(--s3)}
  /* Written at the weight of the rules they replace - `.home .op h1` and
     `.op.op-mob .hero-name` are two and three classes, and a one-class rule
     loses to them wherever it sits in the file. */
  .home .op h1,.op h1,.op .h1-big,.op.duo .h1-big{
     font-size:var(--lg);line-height:1.15;margin-block-end:var(--s2)}
  .op .hero-name,.op.op-mob .hero-name{font-size:var(--md);
     line-height:1.2;margin-block-end:var(--s2)}
  .op .hero-h2,.op.op-mob .hero-h2,.op .lede,.op.plain .lede,
  .op .dedication,.op.op-mob .dedication,.op .creed,.op .creed-big{
     font-size:var(--sm);line-height:1.4;margin-block-end:var(--s2);max-width:none}
  .op .dedication,.op.op-mob .dedication{font-size:var(--xs)}
  .op .hero-go,.op.op-mob .hero-go{margin-block-start:var(--s3);gap:var(--s2)}
  /* The selectors are written at the same weight as the ones they have to
     beat: `.op.op-mob .hero-img` is three classes, and a one-class rule loses
     to it however late it is in the file. This is the sixth time a later rule
     in here has been silently outranked by an earlier one. */
  /* 🔴 THE PHOTOGRAPH STEPS OUT WHERE IT IS A BLOCK OF ITS OWN, AND STAYS
     WHERE IT IS THE GROUND. The arithmetic decides it rather than taste: on a
     390px-tall screen the bar is 89px and the home opening's words are 207px
     before any air at all, which is 76% of the screen with nothing else in it.
     There is no arrangement that shows those words AND a photograph and still
     leaves a reader a sign that the page continues.
     ON THE INJURY PAGE IT STAYS, because there the picture is the section's
     background and the words sit over it - it costs no height at all.
     🔴 AND THIS IS A LAYOUT DECISION THE DESIGN SYSTEM ALREADY ALLOWS.
     Decision 0009 requires every page to read with its image regions absent,
     and `check-no-images` renders all ten pages with every picture removed and
     proves the layout closes the space. Treatment and About already open with
     words alone at every width. */
  .op.op-mob .hero-img,.op.op-mob .hero-pic,
  .op.duo .hero-img{display:none}
  .op.scene .hero-img{max-block-size:none}
  /* An opening still has to read as an opening, AND the five of them have to
     stay inside 1.75x of each other - check-mobile holds them to it at every
     shape it renders, landscape included since 22 September. The tallest of
     them on a short screen is the home page at about 50vh, so the floor is
     50vh and not 34: at 320px tall that is 160px against 276px, which is 1.7x. */
  .op,.op.plain,.op.scene,.op.duo{min-block-size:50vh}
  /* One line, so the bar does not take 81px of a 320px screen. At 568 wide
     the English descriptor measures about 290px and the row has 520. */
  .brand-d{white-space:nowrap;text-wrap:auto}
}

/* ── AND ONE STEP FURTHER ON A 320px-TALL SCREEN ──────────────────────────
   22rem is 352px: the smallest phone there is, on its side. There the bar takes
   65px of 320 and check-mobile allows the bar and the opening 92% of the screen
   between them, which leaves the opening 229px. Measured at 568x320 before this
   block: Hebrew 233px and English 276px, and the whole of the difference is two
   lines - the English descriptor wraps at 19px in a 520px column and so does the
   dedication. A step down on the descriptor puts it back on one line, and the
   air between the five blocks comes down from 8px to 4px. */
@media (max-height:22rem){
  .op,.op.plain,.op.scene,.op.duo,.op.op-mob{padding-block:var(--s2)}
  .op .hero-name,.op.op-mob .hero-name{font-size:var(--sm)}
  .op > *{margin-block-end:var(--s1)}
  .op .hero-go,.op.op-mob .hero-go{margin-block-start:var(--s2)}
}

/* Text for a screen reader and not for the eye. Off-screen rather than
   display:none, because display:none is not announced either. */
.vh{position:absolute;width:1px;height:1px;overflow:hidden;clip-path:inset(50%);
    white-space:nowrap}
/* ── THE CLOSE BAR ON AN OPEN FILM ────────────────────────────────────────
   Opened, the summary held only the poster and the poster is hidden when open,
   so the control measured 355x0: nothing to press, and a keyboard user who had
   tabbed to it was standing on a target with no size and no way back. This is
   the way back, and it is 44px tall like every other control on this site. */
.films .film-close{display:none}
.films .film[open] > summary .film-close{display:flex;align-items:center;
   justify-content:center;gap:var(--s2);min-height:44px;padding-inline:var(--s4);
   font-size:var(--sm);font-weight:700;color:var(--accent);
   border-block-end:1px solid color-mix(in srgb, var(--fill-dark) 45%, transparent)}
.films .film-close svg{inline-size:12px;block-size:12px;flex:none}
.films .film[open] > summary .film-open-l{display:none}

/* ── THE PRESS STRIP ──────────────────────────────────────────────────────
   Admin, 15 September. Seven headlines on one moving line, each a link.

   🔴 IT MOVES LEFT TO RIGHT, AND THAT IS THE HEBREW DIRECTION. Reading runs
   AGAINST the travel: an English ticker moves right to left so the eye reads
   into the line. Hebrew reads right to left, so the line has to travel the
   other way or every headline arrives back to front.

   HOW THE LOOP IS SEAMLESS. The belt holds the list TWICE and is exactly twice
   one list wide, so translating it by 50% of itself moves it by exactly one
   list: at the end of the cycle the second copy stands where the first stood
   and the jump back to 0 is invisible. The second copy is plain text and not
   links, so nothing is in the tab order twice.

   🔴 FR-21, AND EVERY PART OF THIS RULE IS IT. "Calm by construction: no
   autoplay, no flashing, no popups, prefers-reduced-motion honoured", for a
   readership that includes people with hyperarousal symptoms. So the motion is
   linear with no easing, slow enough to read at a walk, stops under a pointer,
   stops when a keyboard enters it, stops on a control anybody can reach, and
   under prefers-reduced-motion does not start. */
.news .helpline{margin-block:var(--s2) 0}
.news{background:color-mix(in srgb, var(--accent) 8%, var(--white));
      border-block:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
      margin-inline:calc(50% - 50vw);
      padding:var(--s5) 0;max-width:none;
      display:flex;flex-direction:column;gap:var(--s3)}
/* EVERYTHING BUT THE MOVING LINE KEEPS THE PAGE'S GUTTER. The belt is the one
   part that runs edge to edge, because a strip that stops short of the window
   looks like a mistake rather than a band. The helpline is inside this section
   and takes the gutter with the rest: it closes the section that names suicide,
   which is what decision 0048 asks of it. */
/* 🔴 THE HELP-LINE BAR WAS 57% EMPTY, 22 September: 1120px of dark for 457px
   of text. It keeps the rail as its start edge and stops at its own content. */
.news > .news-note{max-width:none;
      margin-inline:max(var(--s4), calc(50vw - 560px))}
/* 🔴 ON THE MIDDLE OF THE BAND, Admin 23 September. It was capped to its own
   content and left on the rail, so a single dark line sat against one edge of
   a full-width band with 540px of empty band beside it. Measured before: its
   centre was 930 against the page's 640. */
.news > .helpline{max-width:max-content;margin-inline:auto;text-align:center}
.news-note{margin:0;font-size:var(--xs);line-height:1.4;color:var(--grey-lite)}

/* THE CONTROL IS A REAL CONTROL. WCAG 2.2.2 wants a way to pause anything that
   moves for more than five seconds, and hover does not reach somebody who never
   uses a pointer. A checkbox and its label are a button the browser already
   has: it takes focus, it toggles on Enter and Space, and it needs no
   JavaScript. The label says which of the two things it will DO, and that
   swaps with the state - a fixed string would announce "stop" to a reader
   looking at a strip that had already stopped. */
/* THE CONTROL, AS A MARK. Admin took the words off it on 15 September; the
   control itself cannot go, because WCAG 2.2.2 is a Level A rule that
   ת"י 5568 adopts, so on an Israeli nonprofit's site it is law rather than
   taste. It sits at the END of the line - the left, in this RTL band - which is
   where the headlines are leaving, so it covers the least legible part of the
   strip rather than the part being read.
   44x44, WHICH IS THE OTHER LAW. check-viewport refuses anything a thumb
   cannot hit, and an icon-only control is exactly the kind that ends up 24px. */
.news-hold{position:absolute;inset-block:0;inset-inline-end:0;z-index:2;
           cursor:pointer;color:var(--accent-ink);
           inline-size:44px;display:flex;align-items:center;justify-content:center;
           background:linear-gradient(to var(--news-fade,left),
                      color-mix(in srgb, var(--accent) 8%, var(--white)) 62%,
                      transparent)}
.news-hold .ic{inline-size:19px;block-size:19px;display:block}
.news-hold:hover{color:var(--ground)}
.news-hold .ic-go,
#news-hold:checked ~ .news-vp .news-hold .ic-hold{display:none}
#news-hold:checked ~ .news-vp .news-hold .ic-go{display:block}
/* THE LABEL IS A GRANDCHILD OF THE CHECKBOX'S SIBLING, NOT A SIBLING. It moved
   into `.news-top` so it could sit on the heading's row, and `~ .news-hold`
   silently stopped matching: the control kept saying "stop" after it had
   stopped. The combinator has to follow the markup. */
/* THE LABEL MOVED INSIDE THE VIEWPORT, so the combinator follows it. This is
   the second time these selectors have had to: the first move silently stopped
   them matching and the control went on saying "stop" after it had stopped,
   which is why scripts/check-motion.mjs exists. */
.news-hold .hold-b,
#news-hold:checked ~ .news-vp .news-hold .hold-a{display:none}
#news-hold:checked ~ .news-vp .news-hold .hold-b{display:inline}
#news-hold:focus-visible ~ .news-vp .news-hold{outline:2px solid var(--accent-ink);
           outline-offset:-3px;border-radius:8px}

/* The fade under the control points at the band's edge, and `left`/`right` in a
   gradient are PHYSICAL: the English page is LTR but this band's content is
   Hebrew and runs the same way on both, so the direction is set once here. */
/* 🔴 THE STRIP LAYS OUT RIGHT TO LEFT IN BOTH LANGUAGES, AND WITHOUT THIS THE
   ENGLISH ONE SCROLLED ITSELF EMPTY. Measured through one loop at 1280px:
       Hebrew   3  4  3  3  3  items visible
       English  3  1  0  0  0
   The belt overflows past its START edge. In Hebrew that edge is the right, so
   the belt hangs off to the LEFT and translating rightward brings the duplicate
   copy in. On the English page the whole document is left to right, so the belt
   hung off to the right instead and the same translation pushed it AWAY - after
   a quarter of the loop there was nothing in the band at all.
   The content is Hebrew on both pages and travels the Hebrew way on both, so the
   box it travels in has to be the Hebrew way round on both. This is the one
   place on the site where a direction is set rather than inherited, and it is
   set because the CONTENT has a direction, not because the page does. */
/* 🔴 THE FADE RAN THE WRONG WAY, 22 September. `to left` made the control's
   gradient opaque on the side facing the CENTRE of the strip and transparent
   at the window edge, so the last headline was still cut flush against the
   frame with a translucent button over it. A fade covers the edge, not the
   middle. */
.news-vp{position:relative;overflow:hidden;direction:rtl;--news-fade:right}
/* 🔴 THE BELT WAS CUT FLUSH AT THE EDGE IT ARRIVES FROM, 22 September. The
   leaving edge has had a fade since the pause control was built; the arriving
   edge had nothing, so the first headline was sliced mid-word against the
   browser frame while every other element on the page sat inside an 80px
   gutter. Same gradient, same width, the other end. It is painted over the
   belt rather than masked into it, because a mask on the viewport would fade
   the pause control with it. */
.news-vp::before,.news-vp::after{content:"";position:absolute;inset-block:0;
   inline-size:72px;z-index:1;pointer-events:none}
.news-vp::before{inset-inline-start:0;
   background:linear-gradient(to left,
              color-mix(in srgb, var(--accent) 8%, var(--white)) 62%, transparent)}
.news-vp::after{inset-inline-end:0;
   background:linear-gradient(to right,
              color-mix(in srgb, var(--accent) 8%, var(--white)) 62%, transparent)}
/* The outlet names on the English page are Latin. A Latin run inside an RTL box
   keeps its own order, but stating it costs nothing and survives a name with a
   digit or an ampersand in it. */
html[lang="en"] .news-src{direction:ltr}
.news-belt{display:flex;inline-size:max-content;
           animation:news-run 96s linear infinite}
.news-list{list-style:none;display:flex;margin:0;padding:0;max-width:none}
.news-list > li{flex:none}
.news-list :is(a,li > .news-src){display:flex}
/* 44px TALL, AND check-viewport IS WHY. At 8px of padding each headline was a
   634x40 tap target: wide enough to be obvious, and 4px short of the height a
   thumb is owed. It failed on both pages at all six widths. */
.news-list a,
.news-dup li{display:flex;align-items:baseline;gap:var(--s3);
             padding:var(--s3) var(--s5);min-block-size:44px;
             white-space:nowrap;text-decoration:none}
/* A DOT BETWEEN ARTICLES, SET IN THE GAP RATHER THAN AFTER THE LAST ONE.
   Without it seven headlines read as one long sentence sliding past. It is on
   the LEADING edge of every item, which in this RTL line is the right, and the
   very first item in the belt loses it - at the seam the previous copy's last
   item is already supplying one. */
.news-list > li{position:relative}
.news-list > li::before{content:"";position:absolute;inset-block:35%;
   inset-inline-start:0;inline-size:1px;
   background:color-mix(in srgb, var(--fill) 45%, transparent)}
/* accentInk on this ground, which check-rendered-contrast measures. The source
   is the quiet half and the headline is the loud one, because the headline is
   the thing a reader is deciding whether to open. */
/* 🔴 BOLDER AND MORE OFFICIAL, Admin 22 September. A ticker of press headlines
   is the most factual thing on the page and it was set like a caption: the
   outlet at 700 and the headline at 400, both quiet. It is the reverse of what
   the block is for - a reader is weighing whether the STATE'S OWN PRESS says
   this, so the outlet is a mark of authority and the headline is a statement
   of record. Both go up a step in weight and the outlet takes the deep brand
   purple rather than the mid one, which is also the pair with the wider margin
   on this pale ground.
   AND THE UNDERLINE STOPS SHOUTING. Seven underlined headlines at 700 in one
   line read as seven corrections. It is still there - these are links in a row
   of text and the underline is what says so - but drawn in the same hairline
   the separators use, so the words come first and the line follows them. */
.news-src{flex:none;font-size:var(--xs);font-weight:800;letter-spacing:.04em;
          color:var(--ground);white-space:nowrap}
.news-t{font-size:var(--sm);line-height:1.5;color:var(--ink);font-weight:700}
.news-list a .news-t{text-decoration:underline;text-underline-offset:4px;
   text-decoration-color:color-mix(in srgb, var(--fill) 45%, transparent);
                     text-decoration-color:color-mix(in srgb, var(--fill) 45%, transparent)}
.news-list a:hover .news-t,
.news-list a:focus-visible .news-t{color:var(--accent-ink);text-decoration-color:currentColor}
.news-list a:focus-visible{outline:2px solid var(--accent-ink);outline-offset:2px;border-radius:8px}

/* TRAVEL IS POSITIVE X, WHICH IS RIGHTWARD IN BOTH DIRECTIONS. transform is
   not a logical property: translateX(50%) moves an element to the visual right
   whatever the page's `dir` is. The English page mirrors nothing here, because
   the headlines are Hebrew on both pages and they read the same way on each. */
@keyframes news-run{from{transform:translateX(0)}to{transform:translateX(50%)}}
.news-vp:hover .news-belt,
.news-vp:focus-within .news-belt,
#news-hold:checked ~ .news-vp .news-belt{animation-play-state:paused}

/* 🔴 NOT SLOWER. STILL. And with the belt still, the second copy is duplicate
   text sitting next to the first, so it goes; the viewport scrolls by hand
   instead, which is how somebody who has asked for no motion reaches item
   seven. The inner container scrolls, never the page. */
@media (prefers-reduced-motion:reduce){
  .news-belt{animation:none}
  .news-dup{display:none}
  .news-vp{overflow-x:auto}
  /* 🔴 THE CHECKBOX GOES WITH ITS LABEL, AND HIDING THE LABEL ALONE IS NOT
     ENOUGH. `.vh` hides by clipping, which is exactly what keeps a control in
     the tab order - that is the point of it. So with the label at display:none
     a keyboard reader still tabbed onto an invisible checkbox that controls an
     animation which is not running. display:none on the input is what takes it
     out of the tab order. Caught in review. */
  .news-hold,#news-hold{display:none}
}

/* 🔴 IT TICKS ON A PHONE TOO, Admin 23 September: "the news strip needs to
   move as on the desktop version." THIS REVERSES A DELIBERATE DECISION AND THE
   REASONS IT REVERSES ARE WRITTEN HERE so nobody re-argues them from scratch.
   The strip was stopped below 48rem on three grounds:
     1. THE HEADLINES DO NOT FIT. The shortest of the seven is 50 characters
        and the longest 77. At 390px a Hebrew headline shows about five words,
        so a reader never has the sentence, only a window sliding along it.
     2. THERE IS NO HOVER ON A TOUCH SCREEN, so the one thing that stops it for
        a desktop reader by accident does not exist here at all.
     3. TAPPING A MOVING LINK IS A MISS. The target travels under the thumb.
   Admin has seen both and wants the movement. What the change cannot give up
   is the second and third of those, because they are the law rather than the
   design: WCAG 2.2.2 asks for a way to pause anything that moves for more than
   five seconds, and this loops for ever. SO THE PAUSE CONTROL COMES BACK ON
   PHONES, at the 44x44 every control on this site is held to, and it is the
   thing that answers (2) and (3) at once - a reader stops the line, then reads
   it, then taps it.
   AND IT RUNS SLOWER HERE. 140s against the desktop's 96s: the window is a
   third of the width, so at the desktop speed a headline crosses it in a third
   of the time. Same belt, same seven articles, same loop; a calmer speed.
   `prefers-reduced-motion` still stops it dead and turns the strip back into a
   row that is scrolled by hand - that block is below and is untouched, and it
   is what a reader who has asked for no motion gets on any screen. */
@media (max-width:47.99rem){
  .news-belt{animation-duration:140s}
  .news-vp{padding-inline:0}

  /* 🔴 THE DESIGN, AND THE PROBLEM IT SOLVES, Admin 23 September: "improve the
     design for the news link strip."
     ON A PHONE THE STRIP HAD NO LABEL OF ANY KIND. The section's name lives in
     an `aria-label` and nowhere on the glass, the outlet name slides out of the
     window before its own headline does, and what is left travelling past is a
     sentence about dead soldiers with nothing saying where it came from. A
     reader meeting it cold cannot tell whether the site is reporting or
     quoting.
     EACH ARTICLE IS A PILL NOW AND THE OUTLET IS A CHIP INSIDE IT. That is the
     label: `הארץ`, `ynet`, `כאן חדשות` in the deep brand purple at the head of
     every item, travelling WITH its headline instead of ahead of it. A moving
     line of pills reads as a press ticker; a moving line of words reads as a
     sentence coming apart.
     BOTH COPIES OF THE BELT ARE STYLED TOGETHER. The loop holds the list twice
     and moves by exactly half of itself, so anything that changes the width of
     one copy and not the other puts a visible jump at the seam. */
  .news-list a,.news-dup li{background:var(--white);border-radius:999px;
     border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
     padding:var(--s2) var(--s4);gap:var(--s3);min-block-size:44px;
     align-items:center}
  .news-list{gap:var(--s3)}
  /* The pills separate themselves; the hairline between them was drawn for a
     line of bare text. */
  .news-list > li::before{display:none}
  .news-src{background:var(--ground);color:var(--white);border-radius:999px;
     padding:3px var(--s2);font-size:var(--xs);line-height:1.4}
  /* The pill is the target and its own edge says so; an underline under a
     headline inside a bordered pill is a second thing saying the same thing. */
  .news-list a .news-t{font-size:var(--sm);line-height:1.45;text-decoration:none}
  .news-t{font-size:var(--sm);line-height:1.45}

  /* 🔴 AND THE PAUSE CONTROL LOOKS LIKE A CONTROL. It was two bars floating on
     the band with a gradient behind them that is invisible on a pale ground -
     the ONLY way to stop the line on a touch screen, drawn as though it were
     decoration. A round white button with the same hairline the pills carry,
     44x44, centred on the line. */
  .news-hold{inline-size:44px;block-size:44px;inset-block:auto;
     top:50%;transform:translateY(-50%);
     background:var(--white);border-radius:999px;
     border:1px solid color-mix(in srgb, var(--fill) 45%, transparent);
     margin-inline-end:var(--s2)}
  /* The two ends do different jobs and get different widths. The LEAVING edge
     carries the button, so its fade is wider than the button and a headline
     dissolves rather than sliding under it. The ARRIVING edge only has to stop
     a word being cut in half, and a wide fade there swallows the outlet chip
     at the moment it is most worth seeing. */
  .news-vp::after{inline-size:60px}
  .news-vp::before{inline-size:28px}

  .news-note{font-size:var(--xs)}
}

/* THE SEPARATOR IN A TWO-PART TERM. `הטיפול · הגורם האנושי` is one heading
   naming one thing two ways, and the dot is the quiet half.
   greyLite AND NOT fillDark. fillDark is a DARK-GROUND colour: on this white it
   measures 3.47:1 against the 4.5 the standard asks, and check-rendered-contrast
   caught it on four pages at both widths. A dot is still text. */
.signs dt .sep{color:var(--grey-lite);font-weight:400;padding-inline:var(--s1)}
/* 🔴 `dir` SETS GLYPH ORDER, NOT ALIGNMENT, 22 September.
   `dir="rtl"` on a block element makes `text-align:start` resolve to the
   RIGHT, so on English pages every Hebrew fragment flew to the opposite edge
   from the words it belongs to: a caption split across 250px with the name at
   one edge and the unit at the other, the footer's registered name 251px in
   from the column everything else hangs on, and the registered purpose with
   its 3px rule at one edge and its own sentence at the other.
   `match-parent` resolves `start` against the PARENT's direction, so the
   Hebrew still reads right to left inside itself and the block still hangs
   where the page hangs. Four places, one rule. */
html[lang="en"] [dir="rtl"]{text-align:match-parent}

/* An age beside a name: the name is the loud half, this is a fact about him. */
.age{font-size:var(--xs);font-weight:400;color:var(--grey-lite);
     padding-inline-start:var(--s2)}

/* ══ THE ENGLISH PAGES, SET FOR LATIN ══════════════════════════════════════
   Admin, 16 September, and he named the reference: tonyrobbins.com, "simple and
   clear". What that page actually does, read rather than recalled, is four
   things - sentence-case headings in a bold sans, body around 16 to 18px with
   generous leading of 1.6 to 1.8, 60 to 100px of air between sections, and a
   wide gap in size between a heading and the text under it.

   🔴 THE HEBREW IS NOT TOUCHED, and that is the instruction. Everything here is
   behind `html[lang="en"]`, which is on the root element of the English pages
   and nowhere else. Nothing in this block can reach a Hebrew page.

   🔴 AND THE TYPEFACE DOES NOT CHANGE. design-system.md is locked and gives
   Assistant to both scripts. Swapping the English face would be a second brand,
   not a typographic improvement, and the wordmark and the brochure would be
   left speaking a different language from the website. What changes is the
   SETTING: leading, tracking, rhythm, and the distance between a heading and
   its text. That is what the reference page is actually doing.

   WHY LATIN WANTS DIFFERENT SETTINGS FROM HEBREW AT ALL. Hebrew has no
   ascenders or descenders to speak of and no capitals, so its lines sit closer
   together comfortably and tracking added between letters opens gaps that read
   as broken words. Latin is the opposite on both counts. One number cannot be
   right for both, which is why this block exists rather than a change to the
   shared rules. */

/* LEADING. 1.7 rather than 1.6 on running text. At 16px that is 27px a line
   instead of 26 - small on one line, and the difference between a paragraph
   that reads and one that feels tight over six of them. Hebrew stays at 1.6. */
/* THE HERO IS EXCLUDED, AND MEASUREMENT IS WHY. 1.7 on the opening's three
   body lines put the English hero at 793px against a 770 bound at 768px wide -
   check-mobile refused it. It is also the right call on its own terms: the
   reference page's generous leading is for RUNNING TEXT, which a reader moves
   down through line by line. A hero is a display block, read in one look, and
   its height is bounded at three widths and by the photograph's own aspect
   above 1024. */
/* 🔴 IT SELECTED BY TAG, AND TEN DISPLAY BLOCKS ARE WRITTEN AS PARAGRAPHS.
   22 September. Measured, Hebrew against English: the 40px creed 50px a line
   against 68, a 28px/800 person's name 33.6 against 47.6, the 40px films
   headline 48 against 68. A name came apart from its own role; a three-line
   creed read as three separate statements. 911px of extra page across five
   pages, none of it running text.
   THE RULE IS BY ROLE NOW. 1.7 is for the sizes a reader moves down through
   line by line; anything set as display keeps the Hebrew ratio, which is the
   one the type was drawn at. */
html[lang="en"] main > section:not(.op)
  :is(p,li,dd,blockquote):not(.creed,.creed-big,.lede-creed,.close-ask,
      .films-l,.p-name,.founder-name,.invite,.stat-s,.strip-fact,.turn,
      .close-h,.unit,.p-role,.step-lead,.on,.strip-on){line-height:1.7}

/* TRACKING. Minus one hundredth of an em on the big display sizes only.
   Assistant at weight 800 sets its Latin capitals slightly loose at 40px and
   up, which reads as a headline that has not been finished. It is NEVER applied
   below the display sizes: at 16px the same adjustment makes text harder to
   read, not easier, and it is never applied to Hebrew at any size. */
html[lang="en"] :is(h1,.close-h,.split-h){letter-spacing:-0.01em}
html[lang="en"] .home .op h1{letter-spacing:-0.015em}

/* THE GAP BETWEEN A HEADING AND ITS TEXT. The reference page's clearest single
   move: the heading is large, and then there is real air before the sentence
   under it, so the eye lands on the heading first rather than reading the two
   as one block. */
/* 🔴 MOVED INTO THE SHARED `h2` RULE, 22 September, so Hebrew gets it too.
   It was 40px in English and 24px in Hebrew for a heading that is the same
   size in both, which is a difference a reader sees and nobody chose. */

/* RHYTHM BETWEEN SECTIONS. 104px rather than 64, which is the top of the range
   the reference page uses. A section that is isolated reads as one idea; the
   same content at 64px reads as a scroll.
   ON A PHONE IT STAYS AT 64. 104px of air between every section on a 390px
   screen is not calm, it is a page that will not end - and check-mobile's own
   measurements are what taught this file that proportion on a phone is not the
   same question as proportion on a laptop. */
/* 🔴 64rem, NOT 48rem, 22 September. Hebrew steps from 64px to 104px at 64rem
   and English stepped at 48rem, so between 768 and 1023 the same page ran two
   different rhythms - 8 gaps x 40px = 320px of extra page in English on Home
   alone, at a width where the two should be identical. */
@media (min-width:64rem){
  html[lang="en"] main > section{margin-block-start:var(--s7)}
  /* 🔴 THE OPENING KEEPS ITS TUCK, 22 September. `.op` pulls itself 64px up so
     it sits flush against the bar's own rule; this reset cancelled it, and
     every English page opened with a 64px band of white between the navigation
     and the hero while the Hebrew twin sat flush. Same page, switched language,
     and the whole thing dropped. 320px across five pages.
     TWO RULES, NOT `:not(.op)`: the rule above puts 104px on EVERY section, so
     an exclusion leaves the hero with 104px rather than with its own -64. */
  html[lang="en"] main > section:first-child{margin-block-start:0}
  html[lang="en"] main > section.op:first-child{margin-block-start:calc(var(--s6) * -1)}
}

/* THE DISTANCE BETWEEN A HEADING AND BODY TEXT, IN SIZE. `xl` is 22px at 320
   and 40px at 1280; `lg` tops out at 28. Section headings move up a step so the
   ramp from heading to 16px body is unmistakable, which is the whole of what
   "clear hierarchy" means here. The hero is deliberately NOT included: its
   height is bounded by check-mobile at three widths and by the photograph's own
   aspect above 1024, and a larger headline there is a layout change rather than
   a typographic one. */
/* 🔴 THIS RULE WAS A NO-OP THAT DID DAMAGE, 22 September. `h2` is already
   `--xl` in the shared rules, so the size it declared changed nothing it was
   written for - and because `html[lang="en"] main > section > h2` outranks a
   single class, it DID reach `.turn` and `.close-h`, the two display headings
   set at `--xxl`, and knocked both down a step. Measured at 1280: Hebrew 58px,
   English 40px, so the English home page had h1, every h2, the turn line and
   the closing line all at 40px - two type sizes on the whole page.
   The line-height it also set has moved into the shared `h2` rule at the
   locked 1.25, for both scripts. Nothing is left here to declare. */

/* ═══════════════════════════════════════════════════════════════════════════
   RAM'S MODEL, 2 October 2026, issue 135.
   Five components, and three of them exist because Ram wrote three sequences
   with `>` characters between the words. Typed, a sequence is a line a reader
   parses word by word; drawn, it is a route they take in at a glance. Same
   words either way - what changes is whether the shape arrives before the
   reading does.
   EVERY COLOUR BELOW IS ALREADY IN THE LOCKED PALETTE and every pair is one
   the design system already permits: white on `fill` is 8.63:1, `ink` on white
   is 18.42:1, `ground` on white is 18.52:1. No new colour is introduced.
   NOTHING HERE MOVES ON ITS OWN. Decision 0056 opened the door twice, to the
   press strip and to the counting figures, and this is not a third.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ── THE FIGURES BAND'S THIRD CARD, AND ITS CLOSING LINE ──────────────────
   The split card holds two shares of one total and must be read as one claim,
   so the two percentages sit on one line and the caveat sits directly under
   them, where a reader cannot take the numbers without it. */
.stat-pair{margin:var(--s3) 0 var(--s2);font-size:var(--lg);
           line-height:1.3;color:var(--ground);font-weight:700}
.stat-pair b{color:var(--accent-ink);font-weight:800}
.facts-close{margin:var(--s5) 0 0;font-size:var(--md);font-weight:700;
             line-height:1.5;color:var(--ground);max-width:var(--measure)}

/* ── THE TURN OFF THE NUMBERS AND ONTO A MAN ──────────────────────────────
   One sentence standing between a wall of percentages and a photograph. It is
   set larger than body text and lighter than a heading, because it is neither. */
.turn-in{font-size:var(--md);line-height:1.6;color:var(--ink);
         max-width:var(--measure);margin-block-end:var(--s4)}

/* ── THREE PLACES, NAMED ──────────────────────────────────────────────────
   A plan, not a directory. Set as three marks rather than a sentence so that
   nobody reads it as three addresses they could visit this week. */
.where-line{display:flex;flex-wrap:wrap;gap:var(--s2);
            margin:var(--s4) 0 0;padding:0;list-style:none}
.where-line > span{border:1px solid color-mix(in srgb, var(--fill) 35%, transparent);
                   border-radius:999px;padding:var(--s2) var(--s4);
                   font-weight:700;font-size:var(--sm);color:var(--ground);
                   background:var(--white)}

/* ── TWO LINES THAT CLOSE THEIR SECTIONS ─────────────────────────────────── */
.aim{margin-block-start:var(--s4);font-size:var(--md);line-height:1.5;
     color:var(--ground)}
.advisory{margin-block-start:var(--s5);font-size:var(--sm);line-height:1.65;
          color:var(--ink);max-width:var(--measure);
          border-inline-start:3px solid var(--accent);padding-inline-start:var(--s3)}

/* ═══════════════════════════════════════════════════════════════════════════
   BANDING THE TREATMENT PAGE, 2 October 2026.
   THE PROBLEM, MEASURED. The page ran 5,978px and all seven of its sections sat
   on the same white. Nothing told a reader scrolling that one idea had ended
   and another begun except a 48px dash over each heading. The home page has
   banded since 22 September and this page never did, which is why it reads as
   one unbroken wall - and why the eye keeps losing its place in it.
   NOT ONE WORD CHANGED. This is where the words sit and what they sit on.
   THE RHYTHM IS: dark opening - prose - portrait - WASH (the model) - prose
   (the process) - WASH (the measurement) - DARK (the limits). The two pale
   bands are the two sections that carry diagrams, so the drawings get a ground
   of their own and stop reading as more paragraphs. The dark band at the foot
   is the safety statement, which is the most serious thing on the page and the
   last thing a reader meets.
   EVERY PAIR IS ALREADY IN THE LOCKED SYSTEM: ink on the pale wash is the
   facts-band pair the home page has used since 22 September, and white on
   `ground` is 18.52:1, the first row of the permitted list.
   ═══════════════════════════════════════════════════════════════════════════ */

/* Full-bleed, exactly as `.facts-band` does it: pull the section out to the
   viewport edges, then put the gutter back as padding so the text column lands
   on the same rail as every unbanded section above it. */
main > section.band{
  margin-inline:calc(50% - 50vw);
  padding:var(--s6) max(var(--s4), calc(50vw - 560px));
  max-width:none;
  background:color-mix(in srgb, var(--accent) 14%, var(--white));
  border-block:1px solid color-mix(in srgb, var(--fill) 22%, transparent)}
main > section.band > :is(h2,h3,p,.run){max-width:var(--measure)}
main > section.band > :is(.flow,.cycle,.pillars){max-width:none}
/* A banded section brings its own top and bottom space, so the 104px every
   section carries would stack on top of it and open a gap twice the size. */
main > section.band{margin-block-start:var(--s6)}

/* THE LIMITS, AS THE PAGE'S CLOSING BAND.
   Its text ran 1067px wide while every other paragraph on the page ran 464px,
   so the most important warning on the site was also the one line a reader's
   eye could not hold. It is on the measure now, like everything else. */
main > section.band-dark{
  background:var(--ground);color:var(--white);
  border-block-color:color-mix(in srgb, var(--accent) 45%, transparent)}
main > section.band-dark > h2{color:var(--white)}
main > section.band-dark > h2::before{background:var(--accent)}
main > section.band-dark .limits{
  border-color:color-mix(in srgb, var(--accent) 55%, transparent);
  background:color-mix(in srgb, var(--white) 6%, transparent);
  max-width:var(--measure)}
main > section.band-dark .limits p{color:var(--white)}

/* The drawings get air above them inside a band, because the band's own
   padding is doing the work the section margin used to do. */
main > section.band > :is(.flow,.pillars):first-of-type{margin-block-start:var(--s4)}

@media (max-width:47.99rem){
  main > section.band{padding-block:var(--s5)}
}

/* CONSECUTIVE BANDS RUN AS ONE REGION, 2 October.
   The model, the process and the measurement are three sections and one idea -
   how the treatment works - and all three carry a drawn sequence. Banded
   separately they put a hairline and 104px of white between each, so the three
   sequences read as three unrelated things; two of them sat on a wash and the
   third on white, which is worse than either choice made consistently.
   Joined, the association's whole process has one ground of its own, between
   the prose that sets it up and the dark band that bounds it. */
main > section.band + section.band{margin-block-start:0}
/* 🔴 THE AIR ABOVE A CONTINUATION HEADING IS PADDING ON THE SECTION, NOT MARGIN
   ON THE HEADING, and the difference is the whole bug. With the top padding and
   the top border both removed, an `h2` with `margin-block-start` collapses its
   margin straight out of the section - so the 64px meant to sit above the
   heading became 64px of white between the two bands instead. Measured: the
   seam closed from 104px to 64px and stopped, which is the margin escaping.
   Padding cannot collapse. */
main > section.band + section.band:not(.band-dark){border-block-start:0}

/* The donate line, inside the dark closing band.
   🔴 THE CLASS STAYS EXACTLY `on`, AND THAT IS NOT CosMETIC. check-site strips
   `<p class="on">…</p>` from the body before testing FR-26a, with the literal
   `<p class="on"` and its closing quote. `class="on on-dark"` does not match it,
   so the onward link's own word counted as page text - and on `/injury/`, whose
   only remaining use of `טיפול` IS that link, the build refused the page for
   naming nobody who delivers care. The styling is scoped to the band instead. */
main > section.band-dark > .on{margin-block-start:var(--s5);text-align:start}
/* 🔴 THE BUTTON HAD TO INVERT, and the selector had to beat `.on a:not(.btn)`,
   which paints `fill` on white. On the dark band that put deep purple on deep
   purple: the white lettering still cleared its ratio, so no checker would have
   said a word, and the button all but disappeared into the ground. Contrast of
   TEXT is not the same thing as a control a reader can find.
   The pale accent carries `ground` here, which is the dark-band pair the design
   system already permits, and the hover goes to white - gaining contrast under
   the pointer, the same way every other button on the site behaves. */
main > section.band-dark .on a:not(.btn){background:var(--accent);color:var(--ground)}
main > section.band-dark .on a:not(.btn):hover{background:var(--white);color:var(--ground)}
main > section.band-dark .on a:focus-visible{outline-color:var(--accent)}

/* THE GAP WAS AT THE BOTTOM, NOT THE TOP. Every section carries
   `margin-block-end:104px`, so zeroing the top margin of a continuation band
   changed nothing and a 104px white stripe still ran between the three bands -
   the one thing the merge existed to remove. Measured before: 104px between
   bands 4-5 and 5-6. */
main > section.band:has(+ section.band){margin-block-end:0}
/* And the closing dark band meets the footer, which is the same ground. A white
   stripe between two dark grounds is a seam, not a space. */
main > section.band-dark{margin-block-end:0}

/* A dark closing band meets the footer. `main` carries 64px of bottom padding
   on every page, which is right when a page ends on white and wrong when it
   ends on the same dark ground the footer uses: it draws a white seam between
   two identical colours. Only a page that actually ends on the dark band loses
   it, so nothing else moves. */
main:has(> section.band-dark:last-of-type){padding-block-end:0}

/* ═══════════════════════════════════════════════════════════════════════════
   FEWER BOXES, 2 October 2026 - the second design pass on the treatment page.
   WHAT WAS WRONG. The page carried 31 outlined objects: four component cards,
   three rows of step cards (5 + 4 + 4) and three rows of pills (4 + 6 + 4).
   A reader meets the same rounded outline thirty-one times and stops reading
   any of them - the shape stops meaning anything once everything wears it.
   AND THE THREE SEQUENCES WERE NOT THE SAME KIND OF THING, which is the real
   error. They had one identical visual:
     1. הערכה > ויסות > טיפול > תרגול > מדידה והתאמה
        a person's route through the treatment. Chronological. The one diagram
        this page actually needs.
     2. נקודת פתיחה > במהלך הטיפול > סיום > מעקב בהמשך
        not a second process - the same route, seen again, marking WHEN the
        measuring happens. Same shape, deliberately quieter: it is a second
        pass over the first, and drawing it identically claimed two journeys.
     3. טיפול > מדידה > למידה > שיפור
        not a person's route at all. It is the association improving its own
        model over years. A different scale entirely, so a different object.
   NOT ONE WORD CHANGED anywhere in this pass.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ── THE ROUTE ────────────────────────────────────────────────────────────
   A line with stops on it, which is what a route looks like everywhere else in
   the world, and no boxes at all. The rule runs the width, each stage is a dot
   on it, the label sits under its own dot. 5 boxes become 1 line.
   THE LINE IS DRAWN FROM THE FIRST DOT TO THE LAST and not edge to edge: a rule
   that starts before the first stop implies a stage nobody named. */
.flow{list-style:none;display:flex;padding:0;margin:var(--s5) 0 var(--s4);
      position:relative;counter-reset:fl;gap:0}
.flow::before{content:"";position:absolute;inset-block-start:19px;
   inset-inline:calc(100% / var(--n) / 2);block-size:2px;
   background:color-mix(in srgb, var(--fill) 35%, transparent)}
.flow{--n:5}
.flow.quiet{--n:4}
.flow > li{flex:1 1 0;min-width:0;counter-increment:fl;position:relative;
   padding-block-start:var(--s5);text-align:center;
   font-size:var(--sm);font-weight:700;line-height:1.35;color:var(--ground);
   padding-inline:var(--s2)}
/* 🔴 THE NUMBER MOVED INSIDE THE STOP, issue 142. It used to sit small and
   above a small dot - two markers read as one glance only once a reader had
   already decoded which was which. One marker, big enough to hold its own
   number, reads in the one glance it was meant to. Desktop only: the phone
   layout below still hides the number, unchanged, because that decision was
   never about the number being hard to read - it was about five numbers
   eating a 390px row that the stacked list already orders top to bottom. */
.flow > li::before{content:"";position:absolute;inset-block-start:4px;
   inset-inline-start:calc(50% - 15px);inline-size:30px;block-size:30px;
   border-radius:50%;background:var(--fill);
   box-shadow:0 0 0 4px color-mix(in srgb, var(--accent) 18%, transparent)}
.flow > li::after{content:counter(fl);position:absolute;inset-block-start:4px;
   inset-inline-start:calc(50% - 15px);inline-size:30px;block-size:30px;
   line-height:30px;text-align:center;
   font-size:var(--sm);font-weight:800;color:var(--white)}
.flow > li{padding-block-start:calc(34px + var(--s2))}
/* WHEN THE MEASURING HAPPENS IS THE SAME ROUTE, SEEN AGAIN. Hollow stops and a
   fainter line say "this is a layer over the journey above", which is true;
   solid stops would have claimed a second journey, which is not. */
.flow.quiet > li::before{background:var(--white);
   box-shadow:inset 0 0 0 3px var(--fill-dark), 0 0 0 4px color-mix(in srgb, var(--accent) 16%, transparent)}
.flow.quiet > li::after{color:var(--accent-ink)}
.flow.quiet > li{font-weight:600}

/* ── THE CYCLE ────────────────────────────────────────────────────────────
   One object, not four. The association's own loop happens over years and at a
   different scale from a person's treatment, so it gets a shape of its own: a
   single strip that reads in one glance, with the arrows inside it and a return
   mark at the end. 4 boxes become 1. */
.cycle{list-style:none;display:inline-flex;flex-wrap:wrap;align-items:center;
   gap:var(--s2) var(--s3);padding:var(--s3) var(--s4);margin:var(--s4) 0 0;
   border:1px solid color-mix(in srgb, var(--fill) 30%, transparent);
   border-radius:999px;background:var(--white);
   font-size:var(--sm);font-weight:700;color:var(--ground)}
.cycle > li{display:flex;align-items:center;gap:var(--s3)}
.cycle > li:not(:last-child)::after{content:"";inline-size:0;block-size:0;
   border-block:5px solid transparent;
   border-inline-start:7px solid var(--fill-dark);border-inline-end:0}
.cycle::after{content:"\21BA";color:var(--accent-ink);font-weight:800;
   font-size:var(--md);line-height:1}

/* ── NAMED THINGS, AS A RUN OF TEXT ───────────────────────────────────────
   Ram wrote these separated by `·` and that is how they ship. Fourteen pills
   were fourteen more outlines on a page that already had too many, and a pill
   around `HRV` tells a reader nothing the word did not. The separator carries
   the brand colour, which is the whole decoration this needs. */
.run{list-style:none;display:flex;flex-wrap:wrap;align-items:baseline;
   gap:0 var(--s2);padding:0;margin:var(--s2) 0 var(--s4);
   font-size:var(--md);font-weight:700;line-height:1.7;color:var(--ground)}
.run > li:not(:last-child)::after{content:"·";color:var(--accent-ink);
   font-weight:800;margin-inline-start:var(--s2)}
/* The questionnaire line holds four clauses, not four labels - they are phrases
   with commas inside them, and a run of phrases separated by a dot is a
   sentence a reader has to take apart. These stack. */
.run.stack{display:grid;gap:var(--s2);font-size:var(--sm);font-weight:600;
   line-height:1.55;color:var(--ink)}
.run.stack > li{padding-inline-start:var(--s3);position:relative}
.run.stack > li::before{content:"";position:absolute;inset-block-start:0.62em;
   inset-inline-start:0;inline-size:6px;block-size:6px;border-radius:50%;
   background:var(--fill-dark)}
.run.stack > li:not(:last-child)::after{content:none}

/* ── THE TOOLS, AS ICON CARDS ─────────────────────────────────────────────
   Issue 142. Same bordered, tinted box as .limits and .kit - this site
   already has one way of saying "here is a named, boxed fact", and a second
   one invented for the same purpose would just be a different box. The icon
   is decoration, not information: it is aria-hidden, and the word beside it
   already says what the tool is. NOT ONE WORD OF THE FOUR NAMES CHANGED. */
.tool-grid{list-style:none;display:grid;gap:var(--s4);padding:0;
   margin:var(--s3) 0 var(--s4);grid-template-columns:1fr;max-width:none}
@media (min-width:30rem){ .tool-grid{grid-template-columns:repeat(2,1fr)} }
.tool-grid > li{display:flex;align-items:center;gap:var(--s4);min-width:0;
   border:1px solid color-mix(in srgb, var(--fill) 22%, transparent);
   border-radius:8px;padding:var(--s4);
   background:color-mix(in srgb, var(--accent) 8%, var(--white));
   font-size:var(--md);font-weight:700;color:var(--ground)}
.tool-grid svg{flex:none;inline-size:40px;block-size:40px;padding:8px;
   border-radius:50%;color:var(--accent-ink);
   background:color-mix(in srgb, var(--accent) 14%, var(--white))}

/* ── THE FOUR COMPONENTS ──────────────────────────────────────────────────
   They stay four, because four is what they are - but as flat tiles with one
   rule above each, not as four outlined boxes. The rule is the same mark that
   sits over every section heading on this site, which is what ties them to the
   page rather than to the step cards they used to look like. */
.pillars{list-style:none;display:grid;gap:var(--s4) var(--s5);padding:0;
   margin:var(--s5) 0 0;grid-template-columns:1fr}
@media (min-width:34rem){ .pillars{grid-template-columns:repeat(2,1fr)} }
@media (min-width:64rem){ .pillars{grid-template-columns:repeat(4,1fr)} }
.pillars > li{min-width:0;padding-block-start:var(--s3);
   border-block-start:3px solid var(--fill);
   font-size:var(--md);font-weight:700;line-height:1.35;color:var(--ground)}

/* ── ON A PHONE ───────────────────────────────────────────────────────────
   The route turns, and the line turns with it: the rule runs down the start
   edge and the stops sit on it, which is the same drawing rotated rather than a
   second design to keep right. */
@media (max-width:47.99rem){
  .flow{flex-direction:column;gap:var(--s4)}
  .flow::before{inset-block:12px;inset-inline-start:7px;inset-inline-end:auto;
     inline-size:2px;block-size:auto}
  .flow > li{padding-block-start:0;padding-inline-start:var(--s5);
     text-align:start;min-block-size:1.5rem}
  .flow > li::before{inset-block-start:2px;inset-inline-start:0;
     inline-size:16px;block-size:16px}
  /* 🔴 THE NUMBER COMES OFF ON A PHONE. Stacked, it landed at the far edge of a
     390px screen while its own label sat against the other - the full width of
     the phone between a stage and its number, for information the drawing
     already carries: five stops down one line, in order. The list is still an
     `ol`, so a screen reader counts them as it always did. */
  .flow > li::after{content:none}
  /* 🔴 THE LOOP HAS TO STAY A LOOP. `.flow` turns vertical on a phone and this
     one only lost its pill shape, so it wrapped into rows while every arrow
     went on pointing sideways - a sequence that appears to stop dead at the
     edge of each row. It stacks now, the arrows turn downward with it, and the
     return mark sits under the last step where the eye leaves off. */
  .cycle{border-radius:20px;display:flex;flex-direction:column;
     align-items:flex-start;gap:var(--s2)}
  .cycle > li{flex-direction:column;align-items:flex-start;gap:var(--s2)}
  .cycle > li:not(:last-child)::after{
     border-inline:5px solid transparent;
     border-block-start:7px solid var(--fill-dark);border-block-end:0;
     margin-inline-start:var(--s2)}
  .cycle::after{align-self:flex-start;margin-inline-start:var(--s2)}
}

/* TWO DOORS INSTEAD OF ONE, 4 October. `לתרומות` was the only way out of the
   turn line and of the page's close, so a reader who cannot give money had
   nothing to do with what they had just read. The volunteer button carries the
   support page's own wording and lands on its form, where `להתנדב` is already
   a choice.
   THE FILLED ONE LEADS. Two filled buttons make a reader choose before reading
   either; filled then outlined says which is the main road without closing the
   other. It is the same pair, in the same order, as the opening of this page. */
/* 🔴 IT LEFT THE MEASURE AND THEN LEFT ITS OWN TEXT BEHIND, Admin 4 October:
   "need to improve the position of buttons". Side by side the two pills want
   about 500px and `.on` is capped at `--measure`, 464px, so the first fix was
   `max-width:none`. That let the row take the WHOLE RAIL - 1120px at 1280 -
   while the words above it stayed in their 464px column, and measuring it
   showed the buttons missing the line they belong to at every single width:
   37px adrift at 1280, 28px at 768, and at 540px stretched to 492px under a
   394px heading. Centred on the page is not the same as centred on the text.
   THE BOX NOW HUGS ITS OWN CONTENT. `fit-content` sizes the row to the two
   pills and no further, so with no inline margin it starts exactly where the
   reading edge starts - the right in Hebrew, the left in English, because the
   whole rule is written in logical properties and needs no mirror. The cap is
   36rem, which clears the 500px the pair needs and still refuses the rail. */
.on.two-doors{display:flex;flex-wrap:wrap;gap:var(--s3);align-items:center;
   inline-size:fit-content;max-inline-size:min(100%, 36rem)}
/* 🔴 AND THEY FOLLOW THEIR SECTION. `main > section:has(> .beside)` centres its
   heading and its onward line - Admin's display-moment rule of 23 September -
   but `text-align` does nothing to a flex row. `justify-content` was the wrong
   tool too: it only moves pills INSIDE the box, and the box was the problem.
   An auto inline margin moves the box itself, so the pair now centres under a
   centred heading instead of on the rail beneath it. */
main > section:has(> .beside) .on.two-doors{margin-inline:auto}
@media (max-width:33.99rem){
  /* Stacked on a narrow phone, and the two matched to each other rather than
     to the screen. `align-items:stretch` inside a `fit-content` column makes
     both pills as wide as the longer one's words and not one pixel wider, so
     `לתרומות` stops being a 342px slab holding four letters. */
  .on.two-doors{flex-direction:column;align-items:stretch}
  .on.two-doors > .btn{text-align:center}
}


/* Responsive resilience shared by both languages. Keep intrinsic content from
   forcing a wider grid, and let the open menu follow the visible viewport. */
main :is(h1,h2,h3,p,dt,dd,figcaption,a),.ft p{overflow-wrap:anywhere}
main :is(input,textarea,select){max-inline-size:100%}
.hd .brand{min-inline-size:0}
.hd .brand-d{white-space:normal}
@media(max-width:63.99rem){
 /* Reserve room for the wrapped brand descriptor and the last focus ring. */
 .hd .bar-nav{max-block-size:calc(100svh - 7rem);max-block-size:calc(100dvh - 7rem);scroll-padding-block:12px}
 .hd .bar-end{flex-wrap:wrap;gap:12px 20px}
 .hd .bar-nav a{overflow-wrap:anywhere}
}
