The single rust job ran cargo clippy --workspace, which after graduation pulls
GPUI onto a runner that has neither the X11 development packages nor a measured
disk budget. It would have failed on the next push.
rust-headless gates every push and stays fast. rust-ui installs the native
dependencies, reports df before and after so the runner's actual budget gets
measured, and is continue-on-error until it has run green a few times — a job
that OOMs on every push trains people to ignore CI, which is worse than one that
reports without blocking. The flag comes off on evidence, not on assumption.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>