presentation: every screen composed from the live screen size, and one focus ring three device families agree about
Screens.component drives four screens — the HUD (20), the caption strip (40),
the HUD's tap targets (300, above the engine's touch overlay) and the cards
(800) — and activates game.screens.console while any card is up.
theme.module carries the palette, the type scale and the metrics, all derived
from ui.screenSize(); cards.module builds the title, the how-to handbill with
three drawn rules, the pause card and the two end cards; hud.module builds the
dawn meter with the four watches marked, the course readout, the streak, the
crane's prompt and the caption strip.
Both input maps are the slice's: console gains navigateAlt (W/S and the d-pad)
beside navigate (arrows and the left stick), because an axis2 evaluates one
binding per class and neither pair fits in one control. None of the console
controls declares a touch class — a card's own rows are the finger's control,
and a tap points the focus and confirms in one gesture.
A card row is a rich face with a real button laid over it: a container carrying
onClick never dispatches. The mouse re-points the focus on CROSSING a row, not
on resting over one, so a cursor left lying on a card cannot pin the focus away
from a controller.
README.md is the storefront copy and the control table.