I've repaired a copy of the site in `output/site/`. In browser tests, valid signups were saved, all four price examples came out right, and nothing overflowed sideways at 390 px or 1280 px. One check didn't happen: I couldn't test the server on its own, because Python wasn't allowed to open a local port. **What I fixed** (the original `site/` and `server.py` are unchanged): - **Signups never saved:** the form posted to `/api/lead`, but the server only accepts `/api/leads`. Before the fix, a valid signup showed "Signup failed". - **Wrong totals:** the formula multiplied by the discount instead of taking it off, so 3 seats showed CAD 80.64. It now takes off 10% for 3+ seats, adds 12% tax and shows two decimals. - **Seat count not checked:** blank, 0, negative, fractional and 9+ seats are now rejected. The total shows "—" and an error appears as you type and when you submit. - **No visible error text:** the browser's built-in checks could block a submit without a visible message, and names of only spaces got through. The page now checks name, email and seats itself, using the same rules as the server, and shows the error in words. - **Mobile layout:** a fixed 1120 px width caused sideways scrolling. Below 760 px the page is now one column. Title, text and the dark-blue/orange style are unchanged, and I added no frameworks, dependencies or tracking. **Browser checks:** - **Layout:** no sideways overflow in any run at either width. - **Price examples:** 1 seat = CAD 268.80, 2 = 537.60, 3 = 725.76, 8 = 1935.36, all matching the brief. - **Valid signups:** three (1, 3 and 8 seats) showed a confirmation, and the server's file held exactly those three records. - **Invalid signups:** blank name with bad email and blank seats, then seats 0, -2, 2.5 and 9, then an email with no domain ending. Each showed an error and none created a record. **Limitations:** - After my last small change to `app.js` (which added the error while typing), I re-ran only one valid signup, the bad email and 9 seats, not the whole invalid set. - Invalid entries are stopped in the page before anything is sent, so the server's own rejection of bad data was never exercised. - The browser tool returns text, not screenshots, so I didn't judge how the page looks. I didn't test real phones, other browsers or keyboard-only use. - After a successful signup the form clears, so the total goes back to the 1-seat price while the confirmation stays visible. Keeping the entered values instead is a one-line change. A person would need roughly 20–30 minutes (my estimate) to check the look on real phones and browsers, test the server directly with bad data, and decide whether the form should clear after signup. Files are in `output/`: - `site/` — `index.html`, `style.css`, `app.js` and the unchanged `server.py` - `handoff.md` — fixes and test evidence - `test-evidence-submissions.jsonl` — the records from my tests, moved out so the site starts empty