ci / bun-nix (pull_request) Successful in 23s
ci / docs-site (pull_request) Successful in 57s
ci / web (pull_request) Successful in 1m7s
ci / docs-drift (pull_request) Failing after 1m7s
macos-host / check (pull_request) Successful in 1m9s
windows-drivers / probe-and-proto (pull_request) Successful in 1m14s
ci / rust-arm64 (pull_request) Failing after 1m19s
windows-drivers / driver-build (pull_request) Successful in 1m54s
ci / rust (pull_request) Failing after 6m24s
android / android (pull_request) Successful in 6m45s
Confirmed metronomic-stall cases kept arriving after the 2026-08 priority downgrade shipped, so the A/B that blamed REALTIME recorded attenuation, not attribution. Stop telling AMD triage to clear the priority defaults first; the display-stack suspects lead again and the priority A/B is a last resort that masks at most.