Glitch Invaders: fix the review's start error, console overflow, and LIVE badge #32

Need

The 2026-11-01 challenge UX review played v0.1.0 on a station at 212×41, where Chrome's two-thirds viewport is 597 px tall. Two high-impact problems: the attendee's first sight of Pi is a red error, and the Incident Console's action button is below the fold.

Fix

High:

• ENOENT at start. Pi's first visible action is read glitch-progress.json → ENOENT. Have setup write an empty progress file, or have the skill not read it before the game creates it.
• Incident Console overflows. At a 597 px viewport, Continue to Diagnose sits at 641 px. Scroll the console inside a fixed-height panel with its action pinned to the bottom.

Medium:

• LIVE badge beside simulated evidence. Hud.showLiveMode() sets LIVE · Sentry for the whole run, but every console showed SIMULATED · SENTRY UNAVAILABLE. Switch the badge to Simulated once a report falls back, or show LIVE only when live evidence arrives.
• Arrow pads. A tap moves the drone about 25 px, so catching a pickup took a dozen taps. Label the pads "hold", or make a tap move a full lane.
• Toasts cover the drone. Place "Patch applied…" toasts at the top of the arena, or fade them after 2 s.
• End card. It offers Continue Playing and Start New Run, but the last step is telling Pi which clue helped. Add "Last step: tell Pi which clue helped most."

Low:

• Pi asks questions mid-game while the attendee's hands are on the game. Save them for when an incident closes.
• The glitch-state v1 … line is visible under the game. Hide it visually; keep it readable by the monitor.
• The panel's step check trailed the game by about 20 s (step 3 still current while INC-3 was open). Find out whether that lag is in the package's monitor or in the station, and file it in MLH/boothstrap.sh if it is the station.

Done when

• Each item above is fixed, or noted in the PR's Decide section with why it isn't.
• The console's action and every game control fit a 597 px-tall viewport.
• npm run verify, npm test, and npm run lint pass; the standalone Pi flow still works.

Out of scope

Whether rehearsal-2026-11 should have run live Sentry (an event-config question; v0.1.0 also predates #29).