control-ui

# Control UI Verify UI behavior at the real browser or Electron boundary. Reuse the project's Playwright, Cypress, browser, or Electron harness before creating a probe. Keep the data local and disposable. ## Workflow 1. Read the project's documented start command and identify the local URL or debug port. 2. Discover existing browser tests and stable app markers. 3. Select the target page by a positive root marker, role, label, or stable `data-*` attribute, not tab order or coordinates. 4. Capture the initial DOM/accessibility snapshot, screenshot, console state, or network baseline relevant to the claim. 5. Perform one structural action: click, type, keypress, drag, scroll, navigate, or resize. 6. Capture the new state and assert the expected change. 7. Clean up the dev server, debug session, temporary profile, and artifacts. Use `verify-this` for before/after claims. Use raw CDP only when higher-level APIs cannot provide the required CPU, heap, trace, network, or rendering signal. Do not install Playwright just for a one-off probe when an existing browser tool or dependency is available. ## Evidence and privacy Screenshots, traces, network bodies, and heap snapshots may contain private code or user data. Keep them outside public Git unless they are explicitly sanitized and approved. A public report should contain the command, revision, safe metric, and artifact hash or private location, not the payload. ## Gotchas - A screenshot without an assertion prove...