# Validation — October 30, 2026

- TypeScript: passed.
- Workers-runtime tests: 50 passed, including launcher settings, shortcut
  validation, arithmetic parsing, and the existing relay.
- Deployment bundle: Wrangler dry run passed. Existing production Worker retained.
- Live HTTP: Discord's public Gateway endpoint returned HTTP 200 through the Worker.
- Live WebSocket: Discord's Gateway hello was received through the Worker.
- Browser: the actual Discord login form and its QR login flow rendered through
  Scramjet in the local in-app browser. No account credentials were entered.
- Binary transport: text and binary frames preserved in the runtime fixture.
- Socket lifetime: regression test exchanges data after the old ten-second
  timeout, with no aborted upstream signal.
- Sessions: signed, HttpOnly proxy cookie; malformed/tampered sessions rejected.
- Uploads: browser-side streaming requests converted for HTTP/1 compatibility;
  size limits, binary bytes, and abort handling checked.

Not yet verified: account sign-in, authenticated messages, attachments, voice,
video, CAPTCHA completion, and behavior after deployment on Cloudflare.
Passkeys cannot authenticate Discord from a different origin.

Launcher browser checks: layered intro, disabling intro across reloads, light
theme and accent persistence, favorites across reloads, custom shortcuts and
search, notes across reloads, calculator result 14 for 2*(3+4), focus countdown,
memory matching, Snake touch controls, and phone-width layout without overflow.
Temporary QA notes and shortcuts were removed after testing.

An initial load can take time because Scramjet downloads and rewrites Discord's
large JavaScript bundles. This first version prioritizes transport correctness;
asset caching and startup performance have not been tuned.