The repaired site is in `output/site/`: signups now save through the supplied server, the calculator matches all four brief examples, and the page no longer overflows at 390 px. I could not start `python3 server.py` myself because the sandbox blocks sockets, so page checks went through the browser tool and its trusted `/api/leads` server.

## What was fixed
- **Signup endpoint:** `app.js` posted to `/api/lead`; it now posts to `/api/leads`, which is the only path `server.py` accepts.
- **Price formula:** the total is now CAD 240 per seat, less 10% for 3+ seats, plus 12% tax after the discount.
- **Seat validation:** blank, 0, negative, fractional and 9+ seats show "—" and an error instead of a total.
- **Form validation:** an empty or whitespace-only name, an implausible email or bad seats show visible errors and nothing is posted.
- **Mobile layout:** the fixed 1120 px width is now a maximum, with a single column at 760 px and below.

`server.py` is a byte-identical copy, and the existing title, text and dark-blue/orange style are kept. No framework, dependency, external service or tracking was added.

## Checks actually performed
- **Before the fix:** the original site overflowed at 390 px, showed "CAD 0.00" for 1 seat and "CAD 80.64" for 3, and a valid signup failed.
- **Layout:** no horizontal overflow reported at 390 px or 1280 px on any load or interaction.
- **Calculator:** 1 seat showed CAD 268.80, 2 showed 537.60, 3 showed 725.76 and 8 showed 1935.36. Blank, 0, -2, 2.5 and 9 were each rejected.
- **Valid submissions:** three succeeded with a visible confirmation (one at 1280 px, two at 390 px), and the trusted server stored exactly three records.
- **Invalid submissions:** eight attempts each showed an error and created no record. They covered all-blank, whitespace-only name, two bad emails, seats of 9, 2.5 and 0, and one bad email that was then corrected and resubmitted.
- **Server handler:** driven in-process with a fake socket, it returned 404 for the old `/api/lead` path, 201 with a record for valid payloads, and 400 with no record for invalid ones.

## Remaining limitations
- **No visual check:** the browser tool returns text, control state and an overflow flag, not screenshots, so colours, spacing and tap-target size are unconfirmed.
- **Untested code paths:** the server-400 message, the network-failure message and the double-click guard in `app.js` were never triggered.
- **No JavaScript unit tests:** Node is not installed, so pricing was checked only through the page.
- **Test records moved:** I moved the three test records out of `output/site/` into `output/evidence/` so the delivered site starts empty.
- **Assumptions:** the form is not cleared after success (as in the original), and seats accept plain digits only, so "1.0" is rejected.

Estimated human time to finish: about 10–15 minutes (an estimate, not measured), to run `python3 server.py` and look at the page at phone and desktop widths.

## Files are in `output/`
- `handoff.md`
- `site/index.html`
- `site/style.css`
- `site/app.js`
- `site/server.py`
- `evidence/submissions_from_browser_checks.jsonl`
- `evidence/server_handler_check.py`