This page exists to satisfy the Sprint 0 acceptance criterion: the widget works on a test page outside the portal. It loads only three files: lexi-public-config.js, lexi-widget.css, and lexi-embed.js. No portal modules, no PHI brain.
Before this returns real answers, deploy lexi-gateway.js as a Worker and set gatewayUrl in lexi-public-config.js. Until then:
The launcher, panel, quick replies, card rendering, and transport all work and can be inspected.
Sending a message will hit the configured gateway URL. If it is not yet deployed, you will see the graceful fallback ("I could not reach the assistant").
Confirm the footer reads: "Lexi does not access your medical records."
Tab through with the keyboard. Launcher, chips, input, and send all show a visible focus ring.
Open it on a phone width (or DevTools device mode). Panel goes full-screen under 480px.
Open from a nav link via the JS API:
What is deliberately NOT here
No reference to the patient's labs, vitals, WHOOP, medications, or any record. The public widget cannot reach that data by construction. The system prompt that would inject it lives server-side in the gateway and is only built for channels that are not public.