red-baseThis project's own check is failing, so anything that is not the fix builds on a broken base.
Red base: the check is failing, so the run does not continue. While the project's own check is red, the next action does not start, on EVERY action for as long as it stands (a red that complains once can be waited out). The fix path stays open: reading, editing and re-running the check, which is the whole path from red to green and builds nothing on the broken base. The escape hatch is the check passing, so a flaky red clears itself when re-run, and re-running is never refused.
From the comment in native/gate_pre.h above the code that decides it.
Rendered from the strings in native/gate_pre.h, the rule and the envelope (Judge::refuse) both. A word in <angle brackets> is filled in from the command at the moment it is refused.
Only the user can switch it off, by id, in the project's guard:
or by pausing supervision with rabadon off, which records the change. Every other rule keeps running.
62 of the 778 records in the published field dataset (field.jsonl, 2026-07-27 to 2026-08-26) carry this id. STOP is a refusal in enforce mode; WOULD_BLOCK is the same verdict recorded in watch mode, where nothing is stopped.
| event | records |
|---|---|
| WOULD_BLOCK | 60 |
| STOP | 2 |
Counted from field.jsonl, the file the field page is built from.