MC-4303

# MC-4292: Wire Tessa as user tester (second Reviewer stage) **Priority:** medium **Assigned:** luci **Depends on:** MC-4291 (the review loop must exist first) ## What to do After the QA reviewer passes, Tessa should run a browser-based user test before the ticket is considered done. Tessa catches things the QA reviewer can't — visual bugs, broken UX, mobile issues. ## Steps 1. **Add a Tessa dispatch trigger.** After the QA reviewer verdict is `pass` AND the ticket involves UI changes (detect by checking if the diff touches `.html`, `.css`, `.js`, template files, or if the ticket has a `ui` tag), dispatch Tessa. 2. **Tessa dispatch mechanism.** Use the existing Tessa agent pattern: - If Tessa is available as a runtime profile or MC worker, dispatch via `mc_pickup.py` with a prompt that includes: the ticket description, the files changed, the QA reviewer's verdict, and the `done_sha` - Tessa opens a browser, walks the user journey, takes desktop + mobile screenshots, and returns APPROVED or an issue list - If no Tessa runtime is configured yet, skip Tessa for now and add a comment: "Tessa not yet wired — QA reviewer passed but no browser test. Manual test recommended." 3. **If Tessa says APPROVED** → proceed to the "gate to Elmar" check (MC-4291 already handles this). 4. **If Tessa returns issues** → add a comment with the issue list and screenshots, set ticket back to `todo`, increment `review_cycles`, re-dispatch to Worker (same as MC-4291 QA-fail path). 5. **Track Tessa results.** Add a `tessa_verdict` column or use the existing evidence/comment system to record: `APPROVED` / `ISSUES` with the issue list. 6. **Commit and push.** ## Acceptance criteria - UI-touching tickets trigger Tessa after QA passes - Tessa's verdict is recorded in the ticket evidence - Tessa failure sends the ticket back to the Worker (same loop as QA fail) - Non-UI tickets skip Tessa without error - If Tessa is not available, the ticket proceeds with a warning comment ## If blocked - If no Tessa runtime exists on Luci, this ticket becomes: "Configure Tessa as an MC runtime profile, then wire the dispatch." Check if Tessa already exists as a runtime in `runtime_sessions` or as a separate tmux session. - If browser testing requires headed Chrome and Luci's VNC setup is broken, flag as blocker and skip — the QA reviewer loop (MC-4290+4291) still works without Tessa. ## What NOT to do - Do not change the QA reviewer (already done in MC-4290) - Do not change the operator (MC-4293) - Do not change the inbox (MC-4294)