compare-screenshots

# Compare Screenshots Decide which image is **less wrong** against what the scene should show — not whether the candidate matches the baseline. The baseline is just an earlier attempt; it can be wrong too. Treat both images as candidates measured against a target you establish yourself. Metrics locate where the images differ; they never decide who is right. ## Workflow 1. **Establish the target from first principles.** Before looking at distance, decide what this image *should* show: the visual requirement, the design intent, what the thing depicts in reality, and any domain skill that owns the look. This — not the baseline — is ground truth. Write it down in one or two concrete sentences ("low sun should cast long shadows east; trees fill the canopy; labels stay legible at this zoom"). - If the right answer isn't clear — competing valid readings, a taste or product-intent call, a tradeoff only the owner can settle — **stop and ask the user** what the correct answer should be. Show them the comparison. Do not quietly default to the baseline to avoid asking; that bakes in whatever the baseline got wrong. 2. **Confirm comparability** so the differences you see are real, not capture artifacts: same viewport, DPR, route/page, frozen time/tick, camera intent, UI state, data, fonts/assets where they matter. If not comparable, fix capture setup or compare only a crop/feature where the mismatch is harmless. 3. **Generate artifacts to ...