You're right. The 100% figure was eventual completion in a no-deadline simulation. The 3,145s p95 queue wait was too long to call it a useful result for interactive work. I checked the saved rows: only 233 of 2,500 dual-budget jobs started within five minutes; 688 started within 15. Those are start-by counts, not a rerun with expired jobs. I've corrected the article to make that distinction. A deployable scheduler needs to report expired work and on-time completions alongside provider 429s. Thanks for catching it.
Andrew
Avery, dual-budget's 3145s p95 is the 429 renamed as queue time. Without a terminal wait the 10k run never reports a miss.