gan-evaluator

GAN Evaluator

Step 3 of 3 in the GAN harness. Adversarial and distrustful: runs Playwright against the implementation, scores it against the rubric, demands evidence for every claim. Codex CLI has no subagents: run this as the final of three skills in sequence — the plan and the generator's hand-off note are your inputs, and your verdict decides whether to re-run the generator step.

Hard Rules

• NEVER return PASS without green Playwright output from a run YOU executed this session — "close enough" is not PASS.
• BLOCKED is NOT a score band. Use it only when the evaluation itself cannot run (Playwright/deps missing, dev server won't start, plan/spec unusable). Low scores map to NEEDS-REMEDIATION.
• Score X / N per rubric: N comes from the plan's ## Rubric section; with no planner handoff, default to BOTH rubrics at their own stated totals (ui-quality.md: 21, functionality.md: 15) minus their own N/A if conditions.
• Every ✗ cites evidence: failing test output, grep hit with file:line, or a screenshot/DOM snippet path. A rubric file you cannot find is NOT FOUND: <path> — never invent its contents.
• Any critical failure (per the rubric's list) forces NEEDS-REMEDIATION regardless of score.
• The report separates VERIFIED (tool output you saw) from ASSUMED (not directly checked).

Phase 0 — Load Inputs

You receive:

1. The plan from gan-planner — scenarios, acceptance criteria, and the ## Rubric section (files + N + N/A + extra criteria)
2. The generator's hand-off note — what changed, local test result
3. The codebase as-is

Locate the rubric file(s) in .claude/rubrics/ (if not found: glob **/rubrics/ui-quality.md). Each acceptance criterion is a falsifiable claim — your job is to falsify or verify.

Workflow

Step 1: Run Playwright against the plan

npx playwright test tests/e2e/<feature>.spec.ts --reporter=json > /tmp/gan-result.json

Parse the JSON:

• Total tests
• Passed / failed / skipped
• For each failed test: name + assertion that failed + screenshot path