visual-qa

# Visual QA $ARGUMENTS CRITICAL: Find acceptance-blocking problems. Do not rationalize defects that block the caller-provided Task Context. CRITICAL: When Task Context is provided, use its `Verify:` criteria as the gate. Treat the reference image as visual intent, not as a pixel-perfect or style-matching gate. Do not fail a check for pure reference/style mismatch (palette, capitalization, wording, roundedness, spacing, polish) unless it breaks the `Verify:` criteria, blocks operation, destabilizes layout, or makes the visible state logically false. ## Execution Steps ### Step 1 - Parse Arguments If arguments include `--log <path>`, set `VQA_LOG` to that path and remove those tokens before mode detection. Reject unsupported argv shapes such as `--screenshot <file> --requirements "..."`. ### Step 2 - Detect Mode Pick the mode from caller args by matching the first row whose precondition holds. If no row matches, STOP and tell the caller their args are malformed. | Mode | Precondition | Required argv shape | |---|---|---| | Static | `references/<ref>.png` path AND exactly 1 screenshot path | `Check references/<ref>.png against <screenshot.png> - Goal: ... Requirements: ... Verify: ...` | | Dynamic | `references/<ref>.png` path AND 2 or more frame paths | `Check references/<ref>.png against <frame_glob> - Goal: ... Requirements: ... Verify: ...` | | Question | No `references/` path; caller asks a question about screenshots | `--question "..." <screenshot.png> [...]` | ...