Auto-detected flaky tests (merge-group) — review for quarantine

[github-actions]

Flaky-test detection (issue #1782) found the following candidates
for quarantine during a merge-group CI run:

# CORE-TREE (requires human review): tests/unit/hooks/pr-feedback-scope-controller.test.ts
tests/unit/scripts/ci/repository-validation-real-process-2675.test.ts
tests/unit/telemetry/init-rehome.test.ts
tests/unit/utils/bun-compat-exit-first-2530.test.ts

To quarantine: append each line to the appropriate
scripts/ci/quarantined-tests*.txt file.

This issue was filed automatically by the flake-detection workflow.

[zaxbysauce]

This is the automated output of the flake-detection workflow added for issue #1782 — the issue body is generated verbatim by scripts/ci/detect-and-quarantine-flakes.sh, so it's a legit report, not spam. I checked the repo state:

• All 4 candidate files exist; none are currently listed in scripts/ci/quarantined-tests.txt, -macos.txt, or -windows.txt (the ledgers have no active entries since Test-stability pass: fix + quarantine all tracked merge-group flaky tests (consolidates #1796, #1797, #1799, #1811, #1814, #1835, #1842, #1887, #1907) #1908 retired the backlog), so these are new candidates, not re-reports of already-quarantined tests.
• tests/unit/hooks/pr-feedback-scope-controller.test.ts is tagged CORE-TREE by the script's rule C (tests/unit/{scope,agents,hooks}/**). Per the script's own policy it must get human review, not a blind ledger append — please determine whether it's a real flake (e.g. mock/module-cache leakage) before touching it.
• The other three (repository-validation-real-process-2675, init-rehome, bun-compat-exit-first-2530) are regular candidates; note two already carry issue-number suffixes from earlier fixes, so their flakes are likely environment/infra-sensitive rather than known-broken — consider a re-run before quarantining.
• If quarantining, each entry needs # OWNER: and # EXPIRY: comment metadata per issue [Workstream C] PR 01 of 09: Root-fix filesystem, process, and test-isolation flakes #2477, enforced by check:invariants Check 7; entries with stale expiry will fail the gate.

Heads-up for maintainers: many near-identical auto-issues exist (2718, 2721, 2723, 2724, 2657, …). Consider batching review across the open ones into one ledger PR and closing the rest as duplicates.