AI desktop path: plain-HTML Review and Cost tabs over the Qt bridge, gate in Python

ai_sections.html pastes into the no-AI dashboard.html; ai_bridge.py adds one
ai_request slot that hands every AI contract request (incl. GET /roi) to the
review backend's dispatch(). Desktop page check reruns the web review and cost
cases plus a tampered-page gate case. Eval fixture e-pyqt-ai added.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

tests/README.md

@@ -29,6 +29,12 @@ uv run --with pytest --with playwright pytest tests
   by-hand assumptions), plus every no-AI case. Tests set run and review state on the stub
   directly (the `stub` fixture). To check a generated dashboard folder instead, set
   `PAGE_CHECK_AI_DIR=path/to/dashboard`. Needs npm on PATH, else it skips.
+- `page_check_ai_desktop/`: **Seam 1, AI desktop page.** The no-AI `dashboard.html` with
+  `ai_sections.html` pasted in, loaded from `file://` with a fake Qt bridge whose
+  `ai_request` slot goes to `server_stub.dispatch()` in this process (what `ai_bridge.py`
+  does). Runs the AI web page's review and cost cases and the no-AI cases unchanged, plus
+  a tampered page calling the slot directly (still refused). To check a generated folder,
+  set `PAGE_CHECK_AI_DESKTOP_DIR=path/to/dashboard`; `PAGE_CHECK_WIRED=1` as above.
 - `test_pricing.py`: the AI cost function (normal, long-context, thinking tokens,
   unknown model).
 - `test_reference_scan.py`: no patient data, internal IPs, credentials or keys in any
@@ -45,7 +51,9 @@ uv run --with pytest --with playwright pytest tests
   fixture folder with different answers: `c-keep` and `c-restyle` both run on
   `c-web-existing-frontend`, and also check what changed in the files it already had.
   An `"ai": True` entry (`d-ai-extraction`) expects the AI skill's React starter and
-  runs `page_check_ai/` on the folder it built.
+  runs `page_check_ai/` on the folder it built. An `"ai_desktop": True` entry
+  (`e-pyqt-ai`) expects the desktop AI page and runs `page_check/` (with the bot replay)
+  and `page_check_ai_desktop/` on it.
   For a bot fixture (`b-pyqt-bot`), the eval also dry-runs the generated
   `bot_runner.py`, saves its events to `evals/results/<fixture>.run.jsonl`, and
   replays them in the page check.