Development record

2026-10-18 — The check job's macOS leg takes a 70-minute ceiling, with its warning at 60, raised from 60 and 50 by the coordinating session on delegation from the technical facilitator, who is away until 2026-10-23 (iss-2610181711260494). Across ten merge-group runs on 2026-10-18 the leg took 35.1 to 49.3 minutes, and one came within 0.7 minutes of its 50-minute warning. Its one race-enabled pass keeps a steady 2.80 to 2.85 of the runner's three test slots busy, so the leg is set by its total work rather than by one package: the slowest, internal/core/implement/loop, starts 8 to 12 minutes in and ends 2.5 to 4.2 minutes before the pass does. Its time varies with the runner, since the same tree's package times summed to between 5,738 and 8,050 seconds. The new ceiling stays under the merge queue's 90-minute check response timeout, and the warning keeps its 10-minute lead. The per-package -timeout stays at 40 minutes: the slowest package under race took at most 1,901 seconds, 31.7 minutes, a margin of 8.3. release.yml's verify job is not touched, since it runs the ubuntu race lane, about 21 minutes, under its 55-minute ceiling, not this pass. Starting the loop package first was not taken (at most 2 to 3 minutes, against a list pinned in three files), nor was running it without the race detector on macOS (the macOS-only flakes seen so far came from the race leg). Cutting the pass's total work is the longer lever, captured on its own.