ci-quarantinelisted

# /ci-quarantine One in four merge-queue builds fails, and most of those failures are not bugs. A build that dies on a flake costs about thirty minutes of queue time for every PR behind it. The quarantine lane takes one named test out of the blocking path while it is being fixed. **A quarantined test still runs, still retries and is still reported.** It only loses the power to fail the queue. Nothing is skipped, deleted or filtered out, so the day it stops flaking is visible in the same reports. **It is debt, not a fix.** Every entry expires after 7 days, at most 10 can exist at once, and adding one writes a `proposed` ledger entry that says to fix or delete the test. ## Look before you add ```bash git fetch --quiet origin ci-steward-data || true pnpm ci:flaky ``` It lists every test that failed and then passed on the same merge-group tree, with counts and dates, and says which qualify. Read the status column before anything else: - **QUALIFIES** — flaked on at least two different trees, recently enough that nothing suggests it was fixed. This is the only thing that may be added. - **COOLING** — it flaked often and has now been quiet for longer than its own gap between flakes. That is the shape of a test somebody fixed; quarantining it spends a slot on nothing. The add path refuses it. - **BELOW-THRESHOLD** — one bad runner. Not a classification. **Right now, `--fetch` is the only path that returns anything.** `pnpm ci:flaky` reads per-test flake names out of the dail