I've repaired the signup site in `output/site/`. Valid signups now save through the supplied server, the prices match the brief's examples, and the page no longer scrolls sideways at 390 px or 1280 px. I couldn't run `python3 server.py` and open http://127.0.0.1:8765 myself, because my sandbox blocks network connections. All the page checks went through the provided browser tool and its trusted copy of the server instead.

**What was broken and what I changed:**
1. **Price:** the formula multiplied by the discount instead of subtracting it, so 1 seat showed CAD 0.00. It now takes 10% off for 3+ seats and adds 12% tax afterwards.
2. **Saving signups:** the form posted to `/api/lead`, but the server only accepts `/api/leads`. Every signup failed and nothing was saved.
3. **Bad seat counts:** blank, 0, negative, fractional and 9+ seats got a price. They now show "Enter a whole number of seats from 1 to 8." instead.
4. **Form errors:** the form now checks name, email and seats before sending and shows a visible error for each problem. Success shows "Thanks! Your workshop request is saved."
5. **Mobile:** the page had a fixed 1120 px width and always used two columns. It now fits the screen and stacks into one column on small screens.

The title, text and dark-blue/orange colours are unchanged. `server.py` is identical to the original, and no frameworks, dependencies or tracking were added.

**Checks performed:**
- **Browser, before the fix:** the original site showed CAD 0.00 for 1 seat and had horizontal overflow at 390 px.
- **Calculator:** 1, 2, 3 and 8 seats showed CAD 268.80, 537.60, 725.76 and 1935.36, matching the brief. Blank, 0, -1, 9 and 2.5 were all rejected.
- **Layout:** no horizontal overflow at either width on any test, including when errors were showing.
- **Signups:** two valid signups (one at each width) showed the success message. Two invalid attempts showed errors.
- **Stored records:** the server's file had exactly the 2 valid records and nothing from the invalid attempts. I moved that file into `output/checks/` as evidence, so the delivered site starts with no test data.
- **Server script:** `output/checks/server_check.py` calls the server's request handling directly. It got 201 for a valid signup, 404 for the old `/api/lead` address and 400 for each invalid case, with records only for the valid one. It also confirmed the four price examples.

**Limitations:**
- The browser tool returns text, not screenshots, so I haven't checked colours, spacing or readability by eye.
- The code that shows a server error message can't be reached from the page, because the page's own checks match the server's rules. I've only reviewed that code, not run it.
- I assumed "plausible email" means the server's own email rule, and that the form should clear after a successful signup.

A person would need about 15–25 minutes (my estimate, not measured) to run the server locally and look over desktop and mobile in a real browser.

Files are in `output/`:
- `site/` (`index.html`, `style.css`, `app.js`, `server.py`)
- `handoff.md`
- `checks/`
  - `server_check.py`
  - `cleanup.py`
  - `browser_test_submissions.jsonl`