cdp-verification

# CDP UI Verification "Rules" below is what counts as valid evidence. "Mechanics" is how to attach to the right renderer and repair auth. `apps/desktop/scripts/cdp-smoke-integrations.ts` is a working example script. ## Rules 1. **Target the correct app instance.** Confirm and report the worktree, renderer URL/port, and active route before testing. Follow any task-provided CDP/auth guidance and verify the expected signed-in session. Another running desktop instance is not equivalent. 2. **Reproduce the exact user journey.** Use real browser input and visible UI navigation for the steps the user performs. Assigning DOM properties, invoking internal app APIs, or running component-only scripts is diagnostic support, not proof of end-to-end behavior. 3. **Capture visual and numeric evidence.** Take before/after screenshots paired with relevant CDP measurements (`scrollTop`, focused element, route, persisted state). Confirm the screenshot and the measured state agree. 4. **Exercise the relevant lifecycle.** Include the actual route change, workspace/pane/file switch, remount, or close/reopen from the report. A narrower synthetic flow cannot substitute for the reported interaction. 5. **Treat a mismatch as an incomplete reproduction.** If the test passes but the user still observes the bug, re-check the target instance, exact steps, input method, persisted keys, and lifecycle timing. Reproduce the failure before changing code; a synthetic smoke t...