What problem does it solve? Building web experiences for the Meta Ray-Ban Display requires following a strict 600x600 display contract, public HTTPS delivery, focus and D-pad/EMG input handling, and separating simulator evidence from physical-device proof, all while official sources conflict on features like text input, offline support, and sensors. ## Core Features & Use Cases - Display and input contract enforcement: Guides design within the 600x600 canvas with visible focus, deterministic D-pad action mapping, and recoverable error states. - Preflight receipt runner: The bundled script inspects the HTML entrypoint for Meta metadata markers (viewport, description, mrbd-web-app-capable), checks local script references, optionally runs node --check, and performs read-only HTTPS origin checks. - Source-conflict tracking: Records toolkit-versus-Developer-Center disagreements on text composer, offline, back navigation, gestures, and sensors as separate to-verify evidence rows. - Use Case: When shipping a glanceable Web App to Ray-Ban Display, run the preflight runner against your entrypoint and public origin, then follow the staged simulator-to-physical-device validation workflow. ## Quick Start Ask the agent to preflight your Web App entrypoint with the bundled runner and review the page against the 600x600 display and input contract before deploying to a public HTTPS URL.
