Now: a pick resolves only from an exact RoundRecorded event, an all-zero batch or an all-active batch. A zero-work round in a batch that also holds active rounds matches none of these, so the roundbook shows 'Pending' indefinitely, whichever way the visitor picked.

Change to: inside the settlement loop, collect snapshot.events with work > 0 and roundId in (from, through]. If that count equals s.activeRoundCount and the target round is not among them, return outcome 'rest'. If the count is lower, keep the pick pending, so an incomplete event page is still never read as Rest.

Why: the brief asks for games that 'settle on real rounds', and the docs say 'every omitted round in the span is certified as zero work'. README.md discloses this limit, but the data to resolve many of these rounds is already in the response.

Now: the how-strip renders in both modes. Under Live it says 'Use the last six outcomes as clues.' and 'Score more than Pip over five rounds.', but Live has no clue trail, no Pip and no five-round match.

Change to: wrap the section in {mode === "practice" && (...)}. The bottom note then moves up directly under the Live panel, with no gap to close.

Why: the instructions must describe the mode on screen. These describe a game the Live visitor is not playing.

Now: the matchup panel says 'Best of five'. All five rounds are always played, the winner is whoever has the higher point total with streak bonuses, both players can score in the same round, and a match can be drawn.

Change to: 'Five rounds, most points wins'.

Why: replacement copy and interface copy must be true. 'Best of five' tells a visitor the match ends at three wins, and it does not.

Now: the line under the headline is two fragments and uses 'Pip' with no explanation. The only mention of Squeekchain near the top is the header note, which is hidden at 1080 and below (src/styles.css:1257), so a phone visitor first meets the name in the bottom note.

Change to: 'A Squeekchain prediction game: call Run or Rest and outscore a bot named Pip over five rounds.' Keep the headline 'Outguess the little legs.' as it is.

Why: the hero is a pair, and the line under the headline is one plain sentence saying what this is. A game for 'the hamster economy' has to say whose hamster economy.

Now: before any round is played, the panel presents six outcomes as history. They come from the constant WARMUP in src/game.ts:3, so every match opens with the same trail, and Pip's opening pick is always Run.

Change to: label it 'Warm-up laps, then this match', and change 'Last six' at App.tsx:332 to 'Warm-up'. Leave WARMUP as it is, because saved matches replay from it.

Why: seeded data should not read as a record. The practice label makes this minor, but the wording still claims outcomes that never happened.

Now: 'Play' always carries the current underline, even while the Roundbook is open. Its handler closes a panel, which the open modal already blocks, and calls scrollIntoView with block 'nearest', which does nothing when the toolbar is on screen. In Live mode it does not return to practice. Below 540 it is hidden.

Change to: delete the button at App.tsx:198-208 and its .nav-item.current styles. 'How to play' and 'Roundbook' close up against the brand with the existing 30px gap.

Why: a control that visibly does nothing wastes the first click, and the site has only one page to navigate.

Now: the reveal timer survives a mode switch. The practice round resolves while the Live panel is showing, so its result is announced, its sound can play, and the match advances out of sight.

Change to: in the 'Live rounds' onClick at App.tsx:247, call togglePause() first when phase === "revealing" && !paused. The visitor comes back to the existing 'Resume reveal' state.

Why: no state should change unrelated content, and a result should not arrive for a game that is off screen.

Now: pressing Lock removes the focused button, and the focus effect handles result, choose and finished but not revealing. Focus falls to the body, and a keyboard user has 2.2 seconds to tab back through the page to 'Pause reveal'.

Change to: add a ref to the 'Pause reveal' button at App.tsx:384 and add a line to this effect: if (phase === "revealing") pauseButton.current?.focus({ preventScroll: true }).

Why: WCAG 2.4.3 focus order. DESIGN.md offers pause as the control for this motion, so it has to be reachable in the time it is available.

Now: at 1080 and below the radio mark is hidden, and the native input has opacity 0. The chosen card differs only by a 1px border colour and a very faint fill, on the game's one decision.

Change to: add box-shadow: inset 0 0 0 1px var(--ink) to .choice.selected at src/styles.css:476. That gives a 2px ring at every width with no layout shift. Keep the radio mark hidden where it does not fit.

Why: selection must be obvious at a glance. It passes the 3:1 bar on the border alone, so this is low, and the 'Lock Run' label also repeats the choice.

Now: 'Inspired by the hamster economy.' repeats the footer's 'A small game for the hamster economy.' (App.tsx:663). 'Trust your next prediction' (App.tsx:339) and 'A good instinct deserves a rematch.' (App.tsx:428) tell the player nothing.

Change to: delete all three and keep the footer line. 'Meet Squeekchain' becomes the only child of .bottom-note and sits at its left edge. 'The practice wheel' stays alone at the left of the stage caption. 'Play again' becomes the last item in the finished panel.

Why: a fact or a noun beats an adjective, and cutting these removes repetition without losing any information.