> I'd say that such check can confuse users. "UNSTABLE" is not successful in Jenkins terms.

Actually, both stable and unstable are considered *successful*. See permalinks. Funnily enough, *unsuccessful* refers to "worse than stable". So *successful* and *unsuccessful* have a non-empty intersection.

So any user confusion is a result from confusion caused by the existing situation rather than from my choice of terms (which is consistent with the rest of Jenkins).