wpf-visual-quality-gatelisted

# WPF Visual Quality Gate Closes the gap between "it compiles and the tests pass" and "the change is actually visible and works in the running app." Build and test success can miss clipping, overlap, invisible controls, misleading status, and interactions that only fail on the live desktop. The gate gives visible UI work a concrete stop condition, with an independent evaluator — not the implementing agent — delivering the verdict. The full procedure, runner order, pass criteria, attempt loop, and report format are in `references/wpf-visual-quality-gate.md`. That document stays in the plugin and is updated through the marketplace; never copy it into a project. ## Adopting the gate in a project (once) 1. Create `harness/wpf-visual-quality-gate/defaults.md` in the target project containing the filled Project Defaults table from the gate document: visual launch command, window title, cleanup command. This file is the entire per-project seam. 2. Wire the trigger into the project's `AGENTS.md` (or `CLAUDE.md`) so the gate is mandatory rather than advisory: > - For any change affecting visible WPF UI, run the > `wpf-visual-quality-gate` skill before declaring the work done, using > an independent evaluator sub-agent when available. ## Running the gate (per UI story) 1. Write an evaluator packet — task goal, expected visible behavior, launch command, window title, interaction path, pass criteria, cleanup command, commands already run, files chang