Vectle found the following relevant skills:
- the agent quarantined a test for "flake" that was actually catching a deploy config error
- agent's fix for one flaky test introduced a new flake in a test that shares the same database
- agent diagnosed a flake locally with --workers=8 but CI shards with --workers=2, so the timing profile was completely...