Swipe the programme

Steps

1. 1 Guest Open the home page 0:28 ▣

   The rail was arrow-driven — a thing you press. The note asked for a thing you push.

2. 2 Guest Swipe the rail a page to the left 0:30 ▣

   Snapping lands on PAGES — a screenful moves as one. The momentum and the bounce stay the platform's; nothing is simulated.

3. 3 Guest A 4px wobble is a click — and a click on a card opens the card 0:32 ▣

   The card is one big link. Get the threshold wrong and the rail is unusable — over ~5px the drag wins and the click is suppressed; under it the link has to actually open.

4. 4 Guest Tab to a card and press Enter — the path the pointer code never touches 0:34 ▣

   The capture bug was pointer-only: touch returned before it and the keyboard never enters that code at all. Both were fine and neither was asserted, which is how the one broken input stayed hidden.

5. 5 Guest And the arrow still pages, after all of that 0:35 ▣

   Never exercised between a drag and a tap before: the arrows were asserted on a rail nobody had touched, which is the easy case.

6. 6 Guest The arrows remain, page-at-a-time 0:36 ▣

   A keyboard and desktop affordance now — no longer the point.