| name | deckforge-visual-evidence |
| description | Start a DeckForge application in an isolated browser session, exercise editor/presenter/viewer/export capabilities, capture screenshots, console errors, failed requests, accessibility results, and traces, generate machine-readable evidence, and stop every process the run created. Use for visual QA of generated applications; do not use for slide art direction. |
| version | 1.0.0 |
| user-invocable | false |
| license | MIT |
deckforge-visual-evidence
Verification worker. Prove a generated DeckForge application works by executing it.
- Determine changed surfaces and the required capabilities from the capability catalog.
- Start the target application on an isolated port (do not reuse a shared server).
- Run behavior-focused editor, presenter, viewer, and export-preview scenarios via Playwright.
- Capture the required viewports and a reduced-motion run.
- Record console errors, failed requests, and timing.
- Retry each candidate defect once before reporting.
- Annotate evidence with slide, block, and capability IDs.
- Generate
browser-evidence-report.json and per-capability evidence entries.
- Stop all created processes and browser contexts.
- Mark unavailable checks
unverified, never passed.
Read references/browser-evidence-contract.md and the report schema at
../../schemas/browser-evidence-report.schema.json. Map Playwright tests to
capabilities with assets/evidence-capability-map.json.
Never claim a check ran when the browser, runner, or port was unavailable.
