[lippdev]

Stacked on #101 (controller navigation).

Summary

• Left stick → the browser's pointer on any page. It is a blue ring with a white edge and a dot (the click spot), drawn by spatial.js in its isolated world, so it never passes for the system mouse. Movement uses the existing deadzone and response curve (stickToVelocity).
• A at the pointer gives a left click (real mouse events at that spot, so hover and click behave like a mouse). A twice within 280 ms (DOUBLE_PRESS_MS) gives a right click, so a single press waits that long. Each click briefly squeezes the ring.
• The last one used wins: moving the stick hands A to the pointer. Pressing the D-pad hides the pointer and A presses the focused item again.
• Right stick → the wheel, vertical and sideways, under the pointer (or mid-page before the pointer was ever shown).
• Arrows mode (YouTube TV, Twitch) keeps the stick on the arrow keys its sites expect. The keyboard, dialogs and the toolbar keep taking the stick as a D-pad. The R3 Cursor mode is unchanged.

Test plan

• npm run typecheck
• npm test (118 passed)
• npm run test:e2e (58 passed, 3 skipped). The new controller.spec.ts test covers: the stick shows the pointer, A gives a left click, A A gives a right click with no extra left click, the D-pad hides the pointer and A presses the focused button, and the right stick scrolls
• Screenshot of the pointer over Wikipedia
• Physical controller on the TV (docs/CONTROLLER-TEST.md scenario 7), especially the pointer speed from the sofa

🤖 Generated with Claude Code