Home

boring / v2

publicBoring-Software-Inc/v2
Overview Code History Branches Pull requestsIssuesInsights Campfire Docs
main
HomeOverview Code PRsIssues

fix(web): say a rule couldn't run, not 'evaluation degraded'

2 months ago

016864b
Authored
grim8/23/2026, 8:34:47 AM
The old copy read:

  evaluation degraded
  2 of 3 rules skipped — the fail-closed floor sent this run to review
  instead of passing on guesswork.

Three problems. 'fail-closed floor' is our word and means nothing to a
maintainer. 'passing on guesswork' argues with the reader. And none of it says
a rule could not run, which is the only thing that happened.

Now:

  some rules couldn't run
  2 of 3 skipped. sent to review.

It also reads the enforced flag, so with the fallback off it says 'passed
anyway — the review fallback is off' rather than claiming a review that never
happened.

Each part drops out when unknown, so a malformed step reads 'sent to review.'
instead of a stray 'skipped.'

The reason a rule could not run stays on that rule's own step, which is where
a reader looks next — this step answers how many and what it cost.

Parent2c680b9

2 files changed
  • apps/web/src/lib/synthetic-steps.test.ts+27−4
  • apps/web/src/lib/synthetic-steps.ts+26−9