Add a visual regression baseline for one screen
A committed baseline so an unintended visual change fails a check instead of shipping.
The ticket
Capture a visual regression baseline for one screen and wire the comparison into the pipeline.
Acceptance criteria
- A baseline is committed for each state of the screen
- A deliberately seeded visual change fails the check
- The comparison tolerates font rendering differences without hiding real changes
- Updating a baseline is a reviewable, deliberate step
What lands as proof
A seeded change failing the check, which is the only proof the baseline is actually comparing anything.
Why teams defer it
- A baseline that is too strict fails on font rendering and gets disabled within a week, so the first attempt often poisons the idea.
- Somebody has to own updating baselines, and that ownership is never assigned.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: capture a visual regression baseline for one screen and wire the comparison into the pipeline. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means baseline committed, a seeded change fails the check, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.