Developers want a CLI that auto-detects and triages flaky tests instead of manually rerunning whole CI suites

Across major test toolchains, maintainers and users keep asking for first-class handling of flaky tests: automatic detection of nondeterministic failures, quarantining them, and retrying only the failed tests rather than re-running the entire suite. The Go team's own issue to add flaky-test support has 115 reactions and 36 comments and is still open; the JUnit request to retry flaky tests has 94 reactions and 78 comments. Today teams hand-roll retry wrappers, grep CI logs, and argue over whether flakiness is a test, product, or infra problem. The gap is a standalone tool that ingests CI test history, flags the flaky ones statistically, and gates merges on real failures only.