Merge integration/rpa-dashboard-skills into ticket 04

Keeps both sides: frontend detection and bot wiring from tickets 02/03, optional
sections from ticket 04. The a-empty-sections eval now uses the shared "fixture" key.

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

tests/README.md

@@ -15,6 +15,11 @@ uv run --with pytest --with playwright pytest tests
     generated page instead, set `PAGE_CHECK_HTML=path/to/dashboard.html`.
   - The page sees a fake Qt bridge. Every action the page sends is recorded in
     `window.__calls` as `[slot, ...args]`.
+  - `PAGE_CHECK_WIRED=1`: the page is wired to a bot (sample data off). Sample-data
+    cases skip, and a case checks that the page's actions go to the bot. With no
+    `PAGE_CHECK_HTML`, the template is checked with `SAMPLE_DATA` switched off.
+  - `PAGE_CHECK_REPLAY=run.jsonl`: replay a real bot run (the JSON lines that
+    `python dashboard/bot_runner.py` prints) instead of the built-in run.
   - To add a case, write a `test_*.py` file in `page_check/` that uses the `page`
     and `push(event, data)` fixtures from `conftest.py`.
   - Optional-section cases (`test_optional_sections.py`) skip on a generated page
@@ -30,5 +35,10 @@ uv run --with pytest --with playwright pytest tests
   ```
 
   Results go to `evals/results/<fixture>.json`. To add a fixture, add an entry to
-  `FIXTURES` in `run_eval.py`.
+  `FIXTURES` in `run_eval.py`. An entry with a `"fixture"` key reuses another
+  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.
+  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.
 - `fixtures/<letter>-<name>/`: small test projects for the evals.