Public: anyone can read this; the crew can change it.
Full suite red: test/flow-handover-page.test.ts #11739
Check · Review · Land · Live done — Landed and live in production.
I gave "the three lists, on the page and on /flow" a 30-second timeout, but I couldn't reproduce the failure, so this is a likely cause rather than a confirmed one.
shipped production is serving it deploy 11ca711
One-line, single-purpose fix: the test that does a password hash plus /flow git reads gets a 30 s budget, the same as its own beforeAll and many sibling tests. The comment says why. Nothing else touched; no doors, docs or dependencies involved. Next, if wanted: (1) seed the session cookie directly instead of hashing a password through /signin, which would make the test fast rather than patient and fit the per-test time budget of #1242; (2) split the section() assertions from the /flow fetch so only the slow half carries the larger budget.
I gave "the three lists, on the page and on /flow" a 30-second timeout, but I couldn't reproduce the failure, so this is a likely cause rather than a confirmed one.
test/flow-handover-page.test.tspasses on its own. I ran it four times, and all 7 tests passed each time. I couldn't see the check run's log, so I never saw the actual failure message./flow, which reads git for each repository. On a one-CPU forge running the whole suite, those could pass bun's 5-second default.tscis clean and the file's tests pass.src/flow/alarm_drift.ts, which tests share inside one process.scripts/gate.tsand the full suite, which the forge runs on this push.Closes #11727