check summary labels failing review verdicts as stale reviews #6

Summary

npx rfc2119 check appears to summarize current failing review verdicts as stale review(s).

Observed behavior

After dispatching fresh-context reviewers with:

npx rfc2119 review --dispatch

reviewers recorded current fail verdicts for several requirements. A subsequent check printed detailed diagnostics like:

.2119/verdicts/REQ-002.1.4--50f0d0c5bf84.json:1 [REQ-003.2.4] REQ-002.1.4 has a failing review verdict: Tests assert the missing-default value and helper directory creation separately, but do not verify Settings/AppModel creates ~/Projects when no persisted default exists.
.2119/verdicts/REQ-002.2.2--eae9d29dd327.json:1 [REQ-003.2.4] REQ-002.2.2 has a failing review verdict: Test verifies docs/ for one successful promotion path only; it would pass if docs/ were omitted for other option combinations, violating the 'always' requirement.

But the final summary was:

check: FAIL — 29 violation(s), 23 uncovered, 6 stale review(s)

Expected behavior

Since these review verdicts are current and explicitly failing, the summary should distinguish them from stale/missing verdicts, for example:

check: FAIL — 29 violation(s), 23 uncovered, 6 failing review(s)

or:

check: FAIL — 29 violation(s), 23 uncovered, 6 review failure(s), 0 stale review(s)

Why this matters

The current summary suggests the next action is to rerun or refresh stale reviews. In this case the correct next action is to fix the tests/requirements that failed review, then dispatch new reviews.

Environment

• Command: npx rfc2119 check
• Review verdict files existed and contained current failing verdicts.
• Detailed diagnostics correctly said has a failing review verdict; only the summary label appeared misleading.