Give the table the screen back when the phone is on its side

A phone held sideways is 640x360: short of height and swimming in width. The layout
spent the whole of that shortage on one column — 70px of header, 85px of felt, 205px
of action bar. Two rows of seat pucks 55px tall have to fit inside 85px of felt, which
they cannot, so seven of nine finished past the rail with up to 17px of puck floating
on the page. That single fault was 96 of the 98 offenders the layout audit could find
anywhere.

No amount of shrinking fixes it, because the shortage was never in the table. The bar
is 205px tall and 529 wide to hold three buttons and a status line, and it was taking
that height from the one element that needed height. So in landscape it moves: the bar
becomes a rail down the right-hand side, the table takes the column beside it, and the
felt goes from 529x85 to 409x205 — an actual oval, with room for two rows of pucks and
a gap between them. It also puts Fold, Call and Raise under the right thumb rather than
along the bottom edge, where a landscape grip has the palm.

Which layout the bar is in is declared by the stylesheet in a custom property and read
back by actionBar.js, because the one thing that must not exist is a second copy of
that media query written in JavaScript.

Then the ring stopped predicting itself. seatRingRadii works out the widest ring whose
outermost puck still finishes inside the rail, and it is right about a puck it measured
before the width search settled and before a name wrapped or was shortened — each worth
up to 15px of height arriving after the answer. Four viewports finished with the top
seat 5-6px over. render.js now checks the drawn result the way the audit judges it: if
the worst puck hangs 6px past the rail, the ring comes in by 6px and they are placed
again. A layout that predicts itself has to be right about the future; one that measures
itself only has to be right about the present.

Also in this round:

- Names shorten at a word instead of being chopped mid-one. "Mike from work" on a
  nine-handed phone was "Mike f…"; he is Mike. A name never ends on a joining word,
  because "Mike from" looks cut off rather than shortened, and the whole name is on the
  tooltip either way.

- The blind badge is counted in what a seat needs. It always points away from the table,
  which was taken to mean it costs nothing between two seats — true of a straight rail
  and false of a ring, where neighbours sit at different heights. Three tables had a
  player's stack painted under the next player's SB or BB, and that badge outranks
  everything else on the felt. It also got shorter, 15px to 12: clearing its own name at
  5px of overhang instead of 9 hands every chair in the ring four pixels back, which at
  640x360 is the difference between a 66px puck and a 48px one.

- Border-box, inherited, for the whole app rather than nine elements opting in one at a
  time. Both elements that hadn't went wrong in the same afternoon: the rail overran the
  page's padding by 25px and put Resolve Pot underneath itself, and the raise pad's
  amount field pushed a horizontal scrollbar across a 640px phone.

- The raise amount field is thumb-sized. The rule that sizes fields for a finger names
  the settings panels and the seat form, so the one field on the one surface built for
  thumbs was 36px on every phone in the list. The sweep never saw it because it had no
  step that opened the raise pad; it has one now, and that step also caught the rail
  squeezing its own status line under the pad.

- mobile-web-app-capable alongside Apple's older name, which Chrome has been calling
  deprecated in this page's console on every load.

The audit goes from 19 failing configurations and 98 offenders to 2 and 3, across 294
audits — thirteen viewports, three table shapes, a mouse and a thumb. What is left is
twelve players on a 360px phone with the raise pad open, where twelve pucks at the 44px
minimum genuinely do not fit on the felt; the search reports that rather than papering
over it. Each new mechanism was checked by breaking it on purpose: removing the settle
pass puts 26 offenders back, dropping the badge from the footprint 5, and un-sizing the
raise field is caught by the step that now opens it.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015bnp7xKUPFFSpwkYNFaPgb

tests/holdem/README.md

@@ -22,6 +22,7 @@ other in the page, in the load order from `TexasHoldem.cshtml`.
 | `splitCalculator.test.js` | Chopped pots, odd chips, unmakeable denominations |
 | `handRank.test.js` | What beats what: categories, the wheel, kickers, best five of seven |
 | `readingTheShowdown.test.js` | The board, the picker that fills it, and who wins a side pot |
+| `theRail.test.js` | A phone on its side: which shape the bar is in, what it leaves under the felt, how a name is shortened, how the ring is pulled back onto the table |
 | `invariants.test.js` | 1000 randomised hands per property (see below) |
 
 ## The layout audit
@@ -38,13 +39,23 @@ enough not to trigger iOS zoom, that nothing important is covered or off-screen
 no way to scroll to it, that no grid column has collapsed to nothing, that no
 text is painted outside its box, that no seat covers another seat's writing, and that
 no bet chip is hidden behind a seat or another chip. It
-runs over the table, all five overlays and Quick Split, at thirteen viewports from a
+runs over the table, the raise pad, all five overlays and Quick Split, at thirteen
+viewports from a
 360px phone to a 1600px desktop and the same phones on their side — each viewport
 twice, once with a mouse and once with a thumb, and at three table shapes, mid-hand:
 the sweep posts blinds, deals and calls three times before it measures anything, so
 the bets layer has chips on it. It used to audit a table nobody had ever bet at,
 which is a third of what is on the felt during a hand left unlooked at.
 
+The raise pad is newer than the rest and was worth every second it costs. It is part
+of the bar rather than an overlay, so nothing here had a step that opened it, and it is
+both the tallest thing the bar ever holds and the only place in the tool a dealer types
+an amount. The first sweep that opened it found a 36px-tall field on every phone in the
+list: the `hover: none` rule that sizes fields for a thumb names the settings panels and
+the seat form, and the one field on the one surface built for thumbs was not in the
+list. It also found the rail squeezing its own status line under the pad, which is the
+kind of thing that only happens in the state nobody was looking at.
+
 "Covered" and "out of view" are told apart before anything is hit-tested. An element
 clipped away by a panel that scrolls is not covered by whatever happens to be painted
 at that height, and reporting it that way is a diagnosis of something that isn't
@@ -68,6 +79,26 @@ felt height. The seats follow a felt that changes size on their own, being place
 percentages of it; the chips anchored inside them do not, being placed in pixels. They
 were laid out for a felt 23px taller than the one they were painted on.
 
+## What the sweep taught the layout
+
+For a long run of rounds the seat ring was *predicted* onto the table: work out the
+widest ring whose outermost puck still finishes inside the rail, place the seats, and
+trust it. The prediction is correct arithmetic and it was wrong on the page anyway,
+because every input to it moves after it is taken — the width search settles on a
+narrower puck, a name wraps to a second line or gets shortened out of one, the board
+appears in the middle. Each of those is up to 15px of puck height arriving after the
+answer. Ninety-six of the ninety-eight offenders this sweep could find were that.
+
+So render.js now finishes the way the audit judges it. After the seats are placed it
+measures where they actually landed, and if the worst of them hangs 6px past the rail
+the ring comes in by 6px and they are placed again — the same question this file asks,
+asked by the code that has to get it right. Two passes, bounded, because each one is a
+forced layout of the whole felt and it runs after every tap a dealer makes.
+
+That is the general shape of the lesson here: a layout that predicts itself has to be
+right about the future, and a layout that measures itself only has to be right about
+the present.
+
 That last part, and two of those checks, are newer than this paragraph claiming them.
 `runAll()` did not include the contrast check at all, and touch targets sat behind an
 opt-in flag nothing passed, so "the audit is clean" meant nine checks rather than