Adding GP_OPTIONS put 14 screens into verify-screen's population that have never
been compared by anyone. All 14 read DIFFERS at means of 10-60 against 0.02-7.3
for the calibrated set -- which says nothing yet, because nobody has looked at
one of them, and because both the allowance AND the reference renderer were
built against GP_TITLE.
Failing on them would put the suite red for an uninvestigated state -- the wall
of meaningless failures the display guard exists to prevent. Adding them to the
allowed set would assert they are explained; verify-screen's own header is
emphatic that 'allowed' means 'measured, cause open', not 'ignore'.
So they get their own line naming them as NEVER COMPARED. The discriminator is
the sprite group in the manifest path, so a screen becomes assertable when
somebody moves it into the calibrated population deliberately, rather than by an
export widening underneath the check.
This is the risk I flagged before creating it, measured rather than assumed.