# Screenshots we deliberately do not try to solve

Kept for the record, excluded from the evaluation set. These fail for reasons
that are properties of the screenshot, not of the algorithm, so working around
them would mean guessing:

- `06.png`, `14.png` — exactly ONE grid label visible. A single label cannot be
  cross-checked, so a misread would silently shift the whole board with nothing
  to contradict it. Two mutually consistent labels is the minimum safe anchor.
- `12.png` — 710x594 native. Too few pixels per cell for the label glyphs to
  correlate; measured, the best label score stays ~0.44 at every working
  resolution, so it is not a tuning problem.
- `17.png`-`24.png` — same class as `12.png`: native resolution too low (605-1789px
  wide, vs. 1392-2400px for the fixtures that do solve) for the label glyphs to
  correlate once warped to the canonical cell size; measured, the best label
  score stays ~0.45-0.52 at every working resolution tried (including the
  2400px retry pass), well short of LABEL_ACCEPT (0.62) and inside the
  documented "wrong read" band (0.40-0.56), not close enough to call it a
  tuning problem. Two of the ten screenshots this batch came from (now
  `15.png`/`16.png` in the main set) were high enough resolution to solve --
  the same camera distance/game zoom just wasn't consistent across the batch.

"Too zoomed in" and "too low resolution" are legitimate hard rejections.