diff --git a/.scratch/rpa-dashboard-skills/issues/01-no-ai-tracer-empty-project.md b/.scratch/rpa-dashboard-skills/issues/01-no-ai-tracer-empty-project.md index 196a492..e72e0e6 100644 --- a/.scratch/rpa-dashboard-skills/issues/01-no-ai-tracer-empty-project.md +++ b/.scratch/rpa-dashboard-skills/issues/01-no-ai-tracer-empty-project.md @@ -12,7 +12,7 @@ An automated page check proves the page renders the standard data contract corre **Blocked by:** None (can start immediately) -**Status:** ready-for-agent +**Status:** resolved - [ ] The desktop host template passes the lint hook unfilled. Its placeholders go inside string literals. - [ ] The no-AI skill file exists with a trigger description ("RPA dashboard", "automation dashboard", "bot dashboard", "without AI") and the workflow in spec order: scan → report/keep-or-restyle → colours → stack → optional sections → build → wire → verify. @@ -28,3 +28,7 @@ An automated page check proves the page renders the standard data contract corre - the dark toggle flips the theme. - [ ] The page check runs in light, dark and narrow width (≤820px). - [ ] Skill eval on test project (a), an empty project: the skill asks colours, stack and sections, never reports a frontend, and its output passes the page check. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/.scratch/rpa-dashboard-skills/issues/02-no-ai-desktop-bot-wiring.md b/.scratch/rpa-dashboard-skills/issues/02-no-ai-desktop-bot-wiring.md index 06e3750..167293d 100644 --- a/.scratch/rpa-dashboard-skills/issues/02-no-ai-desktop-bot-wiring.md +++ b/.scratch/rpa-dashboard-skills/issues/02-no-ai-desktop-bot-wiring.md @@ -11,7 +11,7 @@ Part of: ../spec.md **Blocked by:** 01 -**Status:** ready-for-agent +**Status:** resolved - [ ] The skill detects the PyQt project and the bot entry point, and fills in the host template's bot command, steps, step markers and friendly rules from the bot's real output. - [ ] Clicking Run starts the bot in a separate process. The Run button disables itself while running, and the status dot goes ready → running → done/error. @@ -20,3 +20,7 @@ Part of: ../spec.md - [ ] The dark-mode choice persists across app restarts. - [ ] A Python assert-based self-check covers line classification, step-marker matching and friendly-rule matching, including the "never hide an error" case. - [ ] Skill eval on test project (b), a PyQt project with a step-marker bot: the skill doesn't ask the stack question, and the running page shows real steps and log lines. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/.scratch/rpa-dashboard-skills/issues/03-existing-frontend-keep-or-restyle.md b/.scratch/rpa-dashboard-skills/issues/03-existing-frontend-keep-or-restyle.md index b1a27c5..ed81b80 100644 --- a/.scratch/rpa-dashboard-skills/issues/03-existing-frontend-keep-or-restyle.md +++ b/.scratch/rpa-dashboard-skills/issues/03-existing-frontend-keep-or-restyle.md @@ -6,10 +6,14 @@ Part of: ../spec.md **Blocked by:** 01 -**Status:** ready-for-agent +**Status:** resolved - [ ] Detection covers plain HTML, React/Vue projects and an embedded PyQt web view, and reports location, stack and the main colour tokens. - [ ] "Keep": the new dashboard page uses the project's existing tokens and fonts. No existing styles are changed. - [ ] "Restyle": only token blocks change. A diff shows no layout or logic edits. - [ ] The colour question is skipped when the user keeps the existing look. The stack question is skipped whenever a frontend exists. - [ ] Skill eval on test project (c), a web project with an existing frontend and its own colours: the skill reports the frontend correctly. Both branches produce a page that passes the page check. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/.scratch/rpa-dashboard-skills/issues/04-optional-sections.md b/.scratch/rpa-dashboard-skills/issues/04-optional-sections.md index 0b055c8..5f6520a 100644 --- a/.scratch/rpa-dashboard-skills/issues/04-optional-sections.md +++ b/.scratch/rpa-dashboard-skills/issues/04-optional-sections.md @@ -11,10 +11,14 @@ Sections that aren't picked leave no code behind. **Blocked by:** 01 -**Status:** ready-for-agent +**Status:** resolved - [ ] The skill asks for the optional sections with a multi-select and builds only the chosen ones. - [ ] Checkpoint tracker: the page check pushes checkpoint-state events and asserts each box shows pending, active, done or stuck. - [ ] Admin/roles: the page check asserts the admin nav and screen appear for the admin role and are hidden for operators. - [ ] Login page: renders in the chosen theme, light and dark, and hands off to the project's auth or a stub. - [ ] With no optional sections picked, the output contains no leftover markup, scripts or styles for them. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/.scratch/rpa-dashboard-skills/issues/05-ai-tracer-bands-review-approve.md b/.scratch/rpa-dashboard-skills/issues/05-ai-tracer-bands-review-approve.md index 52a5843..2f7cc56 100644 --- a/.scratch/rpa-dashboard-skills/issues/05-ai-tracer-bands-review-approve.md +++ b/.scratch/rpa-dashboard-skills/issues/05-ai-tracer-bands-review-approve.md @@ -9,7 +9,7 @@ Part of: ../spec.md **Blocked by:** 01 -**Status:** ready-for-agent +**Status:** resolved - [ ] The AI skill file exists with a trigger description ("AI RPA dashboard", "extraction dashboard", "LLM/OCR review dashboard") and the shared workflow. - [ ] An AI contract extends the no-AI contract. These shapes came from the Superbill prototype: @@ -25,3 +25,7 @@ Part of: ../spec.md - approve stays blocked while rows are unverified (the server stub refuses); - "page X of Y" updates while running. - [ ] Skill eval on test project (d), a project with an LLM extraction call: the skill picks the AI path, asks the shared questions, and its output passes the page check with sample data. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/.scratch/rpa-dashboard-skills/issues/06-ai-cost-roi-page.md b/.scratch/rpa-dashboard-skills/issues/06-ai-cost-roi-page.md index 9a99908..30997ca 100644 --- a/.scratch/rpa-dashboard-skills/issues/06-ai-cost-roi-page.md +++ b/.scratch/rpa-dashboard-skills/issues/06-ai-cost-roi-page.md @@ -12,7 +12,7 @@ Cost comes from a pricing table that records its source and its as-of date. Opti **Blocked by:** 05 -**Status:** ready-for-agent +**Status:** resolved - [ ] Cost per call = input tokens × input rate + (output + thinking tokens) × output rate, per million tokens. Long-context rates apply above the threshold. - [ ] An unknown model raises an error that names the known models. Cost never silently defaults to zero. @@ -20,3 +20,7 @@ Cost comes from a pricing table that records its source and its as-of date. Opti - [ ] Contract: `RoiRun{model,input_tokens,output_tokens,thinking_tokens,total_cost}` and a fetch-ROI action. (Shape from the Superbill prototype.) - [ ] The page check asserts that the spend tiles sum the runs, the coverage pill counts priced vs. total documents, and the month breakdown groups runs correctly. - [ ] The model picker and retry-on-other-model are offered as optional sections and built only when chosen. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/.scratch/rpa-dashboard-skills/issues/07-ai-desktop-plain-html.md b/.scratch/rpa-dashboard-skills/issues/07-ai-desktop-plain-html.md index c6d4484..4018773 100644 --- a/.scratch/rpa-dashboard-skills/issues/07-ai-desktop-plain-html.md +++ b/.scratch/rpa-dashboard-skills/issues/07-ai-desktop-plain-html.md @@ -6,10 +6,14 @@ Part of: ../spec.md **Blocked by:** 02, 05 -**Status:** ready-for-agent +**Status:** resolved - [ ] Plain-HTML AI sections exist, use the shared theme tokens, and render in light, dark and narrow width. - [ ] The AI events and actions travel over the desktop bridge using the same envelope as the no-AI path. - [ ] Approval is still enforced in Python on the bridge side. Changing the page cannot bypass it. - [ ] The page check runs the AI cases from tickets 05 and 06 against the desktop page and they pass. - [ ] Skill eval on a PyQt test project with an LLM extraction call: the skill picks the desktop AI path, and its output passes the page check. + +## Comments + +Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`. diff --git a/tests/evals/results/a-empty-sections.dashboard.html b/tests/evals/results/a-empty-sections.dashboard.html new file mode 100644 index 0000000..aa2d3f0 --- /dev/null +++ b/tests/evals/results/a-empty-sections.dashboard.html @@ -0,0 +1,421 @@ + + + + + + +RPA Dashboard + + + + + +
+ + +
+
+
Dashboard
Overview of every batch
+
+ + + +
System ready
+
+
+ +
+ +
+
+
0
Total batches
+
0
Completed
+
0
In progress
+
0
Not completed
+
+
+
Batch status split
+
    +
    +
    Recent batches
    No batches yet
    +
    +
    + + + + + + + + + +
    +
    +
    + + +
    +
    +
    RPA Dashboard
    + + + + + +
    +
    + + + + diff --git a/tests/evals/results/a-empty-sections.json b/tests/evals/results/a-empty-sections.json new file mode 100644 index 0000000..b552286 --- /dev/null +++ b/tests/evals/results/a-empty-sections.json @@ -0,0 +1,26 @@ +{ + "fixture": "a-empty-sections", + "passed": true, + "checks": { + "frontend reported correctly": true, + "asks /colou?r/": true, + "asks /desktop|web/": true, + "asks /section/": true, + "never asks /\\bkeep\\b|restyle/": true, + "exactly one page built": true, + "no placeholders left": true, + "checkpoints built": true, + "admin built": true, + "login built": true, + "page check passes": true, + "no section checks skipped": true + }, + "page_check": [ + "43 passed, 3 skipped in 34.31s" + ], + "files": [ + "README.md", + "dashboard\\dashboard.html" + ], + "reply": "Dashboard ready. Sample data la ok-aa run aagudhu, ippo bot connect pannala.\n\n| Item | Details |\n|---|---|\n| File | `dashboard/dashboard.html` (single file) |\n| Theme | Superbill Ember, light + dark |\n| Stack | Web, `API_BASE = \"/api\"`. Backend ippo illa, so `SAMPLE_DATA = true` |\n| Sections | Shell, KPI cards, donut, Run panel, Report + Excel button, **Checkpoint tracker, Admin/roles, Login** |\n| Login | **Stub** dhaan: password check illa, empty illadha username kudutha yaarum ulla poga mudiyum. Unga project la auth illa, adhaan |\n\n**Check pannadhu (headless Playwright screenshots):**\n- Login, Dashboard (6 batches, 4 KPI), Run (4/4 steps, 4/4 checkpoints, log), Report (4/4 rows, pills), Admin (2 users), dark mode, 800px width: ellam render aagudhu.\n- `{{` placeholder ethuvum baakki illa. Script errors um illa.\n\n**Bot wire panna:** backend `GET /api/dashboard`, `GET /api/run/status` (`{running, events[]}`), `POST /api/` serve pannanum, apram `/api/login` um venum. Bot anuppa vendiya events: `status`, `step`, `log`, `cpstate`, `admin_data`, `login_result`.\n\n**Also noticed (fix pannala):** `file://` la open panna console la rendu harmless errors varum. Onnu: `qwebchannel.js` load aagala, adhu Qt ku mattum dhaan venum. Rendu: dark toggle `/api/set-dark` POST panna try pannum, adhu fail aagi silent-aa catch aagidum. Backend la serve panna rendum varaadhu.\n\nFRONTEND: none (detect_frontend.py: \"No existing frontend found.\")\nQUESTIONS: Which colours: Tebra Sky, Superbill Ember, or Custom (one brand hex)? | Desktop (PyQt6) or web? | Which optional sections: Checkpoint tracker, Admin/roles screen, Login page (any or none)?" +} \ No newline at end of file diff --git a/tests/evals/results/a-empty.dashboard.html b/tests/evals/results/a-empty.dashboard.html index ee8cecf..385060e 100644 --- a/tests/evals/results/a-empty.dashboard.html +++ b/tests/evals/results/a-empty.dashboard.html @@ -2,14 +2,14 @@ -RPA Dashboard +RPA Bot + + +
    + + +
    +
    +
    Dashboard
    Overview of every batch
    +
    + + +
    System ready
    +
    +
    + +
    + +
    +
    +
    0
    Total batches
    +
    0
    Completed
    +
    0
    In progress
    +
    0
    Not completed
    +
    +
    +
    Batch status split
    +
      +
      +
      Recent batches
      No batches yet
      +
      +
      + + + + + + + +
      +
      +
      + + + + + + + + + + + + + diff --git a/tests/evals/results/e-pyqt-ai.json b/tests/evals/results/e-pyqt-ai.json new file mode 100644 index 0000000..4dadf6e --- /dev/null +++ b/tests/evals/results/e-pyqt-ai.json @@ -0,0 +1,42 @@ +{ + "fixture": "e-pyqt-ai", + "passed": true, + "checks": { + "frontend reported correctly": true, + "asks /colou?r/": true, + "asks /section/": true, + "never asks /\\bkeep\\b|restyle/": true, + "never asks /desktop|web/": true, + "exactly one page built": true, + "AI desktop path: sections, ai_bridge and review backend built": true, + "no placeholders left in ai_bridge.py": true, + "no placeholders left": true, + "page wired to the bot (sample data off)": true, + "bot_runner.py built": true, + "no placeholders left in the host": true, + "bot dry run ends done": true, + "real steps reach the page": true, + "bot error line reaches the log": true, + "page check passes": true + }, + "page_check": [ + "99 passed, 23 skipped in 61.26s (0:01:01)" + ], + "files": [ + "README.md", + "bot.py", + "dashboard\\ai_bridge.py", + "dashboard\\bands.py", + "dashboard\\bot_raw.log", + "dashboard\\bot_runner.py", + "dashboard\\bridge.py", + "dashboard\\dashboard.html", + "dashboard\\pricing.py", + "dashboard\\server_stub.py", + "extractor.py", + "inbox\\invoice-2201.pdf", + "inbox\\invoice-2202.pdf", + "requirements.txt" + ], + "reply": "Dashboard ready \u2014 **desktop (PyQt6)** path, because `requirements.txt` already has PyQt6. Theme Tebra Sky, no optional sections. Start it with `python dashboard/ai_bridge.py`.\n\n| Check (headless Qt run of the real window) | Result |\n|---|---|\n| Bot dry run (`python dashboard/bot_runner.py`) | 4 steps in order, 10\u219230\u219290\u2192**100**, both `ERROR:` lines shown |\n| Review: band legend | 3 clean \u00b7 1 check \u00b7 1 review \u00b7 1 missing (6/6 fields) |\n| Approve gate | Refused: \"3 flagged field(s) still need verifying.\" \u2192 after Verify remaining \u2192 **\u2713 Approved** |\n| Draft edit | Shows \"1 unsaved change\" until Save; Discard clears it |\n| Running invoice | \"page 1 of 3\" |\n| Cost page | \"4 of 5 documents priced\", one run \"not priced\", by-hand figure goes $6.67 \u2192 $13.33 when minutes change |\n| Dark mode / 800px width / `{{` left / console errors | ok / ok / 0 / **0** |\n\n- **Files:** everything is in `dashboard/`: `dashboard.html`, `bridge.py`, `bot_runner.py`, `ai_bridge.py`, `server_stub.py`, `bands.py`, `pricing.py`.\n- **Wiring:** the Run tab is wired to the real `bot.py`. The Review and Cost tabs still show **sample data** from `server_stub.py`, using your 6 real fields and `gemini-2.5-flash`. To make them real, the project needs to save its extraction results and expose `dispatch()` over that store.\n- **UNVERIFIED:** the Gemini rate ($0.30 in / $2.50 out per 1M tokens) comes from the skill's bundled table (as of 2026-08-11). I wasn't allowed to fetch the pricing page, so please check it.\n- **Not tested:** I didn't click Run inside the window. The bot was only dry-run through `bot_runner.py`.\n\n**Also noticed (not fixed):**\n- `extractor.py` doesn't keep `usage_metadata`, so real runs will show up as \"not priced\".\n- With no API key set, both invoices fail, but the bot still exits 0, so the run shows \"Completed\".\n- The Dashboard KPIs and Report tab are empty, because `bridge.py`'s `load_dashboard` and `load_latest_report` are still TODO.\n\nFRONTEND: none (detect_frontend.py: \"No existing frontend found.\"; PyQt6 in requirements, so desktop path)\nQUESTIONS: Which colours: Tebra Sky, Superbill Ember, or Custom (one brand hex)? | Which optional sections to add: checkpoint tracker, admin/roles screen, login page, model picker, retry on another model (any, or none)?" +} \ No newline at end of file diff --git a/tests/evals/results/e-pyqt-ai.run.jsonl b/tests/evals/results/e-pyqt-ai.run.jsonl new file mode 100644 index 0000000..2fa4aae --- /dev/null +++ b/tests/evals/results/e-pyqt-ai.run.jsonl @@ -0,0 +1,13 @@ +{"event": "status", "data": {"state": "running", "msg": "Running\u2026"}} +{"event": "step", "data": {"label": "Initializing", "pct": 10}} +{"event": "log", "data": {"msg": "Starting the invoice bot.", "type": "info"}} +{"event": "log", "data": {"msg": "Checked the inbox for invoices.", "type": "info"}} +{"event": "step", "data": {"label": "Extract", "pct": 30}} +{"event": "log", "data": {"msg": "Reading invoice fields with the AI model.", "type": "info"}} +{"event": "log", "data": {"msg": "ERROR: extraction failed for invoice-2201.pdf: ValueError", "type": "error"}} +{"event": "log", "data": {"msg": "ERROR: extraction failed for invoice-2202.pdf: ValueError", "type": "error"}} +{"event": "step", "data": {"label": "Review", "pct": 90}} +{"event": "log", "data": {"msg": "Queueing invoices for review.", "type": "info"}} +{"event": "step", "data": {"label": "Completed", "pct": 100}} +{"event": "log", "data": {"msg": "All invoices processed.", "type": "success"}} +{"event": "status", "data": {"state": "done", "msg": "Completed"}} diff --git a/tests/evals/run_eval.py b/tests/evals/run_eval.py index 3e2bb76..5654617 100644 --- a/tests/evals/run_eval.py +++ b/tests/evals/run_eval.py @@ -225,12 +225,13 @@ def main(fixture): if cfg.get("ai_desktop"): env["PAGE_CHECK_AI_DESKTOP_DIR"] = str(pages[0].parent) check_dirs.append(ROOT / "tests" / "page_check_ai_desktop") - pc = subprocess.run([sys.executable, "-m", "pytest", *map(str, check_dirs), "-q"], + pc = subprocess.run([sys.executable, "-m", "pytest", *map(str, check_dirs), "-q", "-rs"], env=env, capture_output=True, text=True) checks["page check passes"] = pc.returncode == 0 page_check = pc.stdout.strip().splitlines()[-1:] if pc.stdout else [pc.stderr[-500:]] + built_without = "page built without" in pc.stdout # a chosen section whose cases skipped if cfg.get("sections"): # every chosen section's page check ran - checks["no section checks skipped"] = "skipped" not in page_check[0] + checks["no section checks skipped"] = not built_without else: page_check = ["no page"]