Script: checks/test_server_and_math.py (run via local Python tool, stdlib only)
Exit code: 0

server.py identical to input: True
seats=1: computed CAD 268.80, brief CAD 268.80, match=True
seats=2: computed CAD 537.60, brief CAD 537.60, match=True
seats=3: computed CAD 725.76, brief CAD 725.76, match=True
seats=8: computed CAD 1935.36, brief CAD 1935.36, match=True
parseSeats('') -> None
parseSeats('0') -> None
parseSeats('-1') -> None
parseSeats('2.5') -> None
parseSeats('9') -> None
parseSeats('1') -> 1
parseSeats('8') -> 8
parseSeats(' 3 ') -> 3
parseSeats('abc') -> None
parseSeats('1e1') -> None
LIVE SERVER TEST NOT RUN / FAILED: URLError <urlopen error [Errno 1] Operation not permitted>

Notes:
- The pricing/parse checks above are a Python mirror of the exact formula and
  regex in output/site/app.js, compared against inputs/brief.md examples.
  The real JS was additionally exercised in the browser (see browser-checks.md).
- The attempted live test spawned output/site/server.py on PORT=8799 and tried
  loopback POSTs (valid, blank name, bad email, seats 0/9/2.5/'3'/-2, and the
  old /api/lead endpoint). The sandbox blocks socket connections
  ("Operation not permitted"), so NONE of those HTTP cases ran. Server-side
  behavior was instead observed through the browser tool's trusted server,
  which implements the original /api/leads logic.
