Flaky test fixer

Establish whether a failure is caused by the current change, deterministic, infrastructure, or genuinely flaky. “Flaky”, “pre-existing”, and “unrelated” are conclusions that require evidence. Treat a failure on the current change as caused by that change until evidence identifies another mechanism; otherwise call it unknown.

Never make CI green by weakening or deleting assertions, filtering unexpected inputs, increasing timeouts, or adding unexplained retries.

Classify once

Spend one evidence pass on the exact failing command, test name, assertion or error, environment, first actionable error, last meaningful log line, whether the test process started, and the current diff. Do not reproduce or search test code before this gate.