My dev.to Gate Couldn't Measure, and the Suite Called It a Regression

My gate suite read almost every non-zero exit as REGRESSION, so a dev.to check that never completed its live measurement told me a fix had broken. I gave "couldn't measure" its own verdict and a suite-wide exit code, and kept a gate that actually finds a bad state as loud as before.