console

The scheme a CARD is driven by: the title, the how-to-play, the pause card and the end card.

It is live exactly while a card is up — Screens.component activates it the instant one goes up and releases it the instant the last one comes down — and it stands down the whole flight and player groups while it is, so a stick held on a menu never also steers the toy and Escape means one thing at a time.

Control	Kind	Keyboard	Pad
navigate	axis2	arrow keys	left stick
navUp / navDown	button	W / S	d-pad up / down
confirm	button	Enter, Numpad Enter, Space	south
back	button	Backspace	east
restart	button	R	north
pause	button	Escape	start

navigate is an axis and an axis evaluates ONE binding per device class, so the arrows are the axis and W / S arrive as their own controls. Both walk the same focus.

No control here carries a touch class, deliberately. A finger drives these cards by tapping the rows themselves, which every card draws as real targets — an on-screen Confirm button would be a second way to do what the card already offers, drawn on top of the card offering it.