chore(ci): remove the flaky-test issue workflow (#9156)

Author: waleedlatif1

.claude/rules/sim-testing.md

@@ -67,9 +67,8 @@ the report.
 
 ## Flaky tests
 
-A daily job (`.github/workflows/ci-flakes.yml`) files a `ci-flake` issue for every test or job
-that failed on a CI attempt and passed when the same commit was re-run, and reopens it if the
-flake recurs after it was closed. Fix the nondeterminism it names: pin the clock
+When a test or job fails on a CI attempt and passes when the same commit is re-run, fix the
+nondeterminism behind it: pin the clock
 (`vi.useFakeTimers({ toFake: ['Date'] })` + `vi.setSystemTime`), give each test its own ids and
 rows, wait on the condition rather than a delay, and keep cold imports out of a test's timeout by
 importing statically. Never add a retry, a skip, or a longer timeout to make one pass; raise a

.cursor/rules/sim-testing.mdc

@@ -65,9 +65,8 @@ the report.
 
 ## Flaky tests
 
-A daily job (`.github/workflows/ci-flakes.yml`) files a `ci-flake` issue for every test or job
-that failed on a CI attempt and passed when the same commit was re-run, and reopens it if the
-flake recurs after it was closed. Fix the nondeterminism it names: pin the clock
+When a test or job fails on a CI attempt and passes when the same commit is re-run, fix the
+nondeterminism behind it: pin the clock
 (`vi.useFakeTimers({ toFake: ['Date'] })` + `vi.setSystemTime`), give each test its own ids and
 rows, wait on the condition rather than a delay, and keep cold imports out of a test's timeout by
 importing statically. Never add a retry, a skip, or a longer timeout to make one pass; raise a