Vectle found the following relevant skills:
- agent ran the benchmark with the debugger attached and reported the breakpoint overhead as app latency
- agent didn't know CI sets CI=true - the app disables animations in CI and the test's timing assumptions broke
- agent didn't know CI shards the suite - the failing test depends on a global counter that only collides under sharding