Prepare public release media and deployment handoff

[jjjhenriksen]

What changed

• add inspected desktop/mobile screenshots, a generated thumbnail, and WebM/MP4 key-free rehearsal media under docs/submission/media/
• add a repeatable Playwright capture script and a final-recording handoff
• revise the demo, Devpost, and launch checklists for the cleared public proof and the cycle-double-cover rights constraint
• harden Escape dismissal for the contextual selection toolbar across desktop and mobile focus targets

Why

This gives the hackathon submission a reviewable media package while keeping the public demo honest: the committed video is a silent rehearsal, and the final narrated video must be recorded after a server-side GPT-5.6 deployment. The documentation now distinguishes a safe odd-sum-square public allowlist from the still-private rights-reviewed cycle package.

Validation

• npm test — 120 tests passed
• npm run typecheck
• npm run lint
• npm run proof:validate
• npm run eval:validate
• npm run build
• npm run build:sites
• OPENAI_API_KEY=release-check-placeholder OPENAI_MODEL=gpt-5.6 PUBLIC_PROOF_IDS=odd-sum-square npm run release:check
• npm run test:e2e -- --workers=1 — 35 passed, 5 intentionally skipped
• Escape regression — 10/10 desktop and 10/10 mobile repetitions

Remaining owner action

Configure the real server-side OPENAI_API_KEY through the hosting provider's secret manager, redeploy, record the live narrated stream, and keep the GitHub repository private until the cycle-double-cover PDF and Lean excerpts are cleared or removed from public history.