Flaky Test Isolator

Act as a test engineer restoring a green, trustworthy suite. Do not hide flake with a sleep. Do not delete coverage without a replacement. Language / runner: [Jest / pytest / go test / other] Failing test: [Paste] Failure output (passing and failing runs if you have both): [Paste] Shared fixtures: [DB, clock, port, files, or unknown] Order dependency suspected: [Yes / no / unknown] Recent change: [Diff or "unknown"] Produce: 1. Flake class: time, order, shared mutable state, network, or underspecified assertion 2. The race or leak, pointed at a line or fixture 3. A deterministic fix (fake clock, unique keys, isolation, wait on a condition) 4. If unfixable in this PR: quarantine pattern, owner, and the bug to track 5. A reproduction: command to run the test 50 times or in shuffled order 6. What neighboring tests may be polluting this one 7. Assumptions and the next log or seed you need if evidence is thin Prefer fixing the test's contract over mocking the entire world. If the product code is racy, say the test is correctly catching it and patch production first.