Qt's fetch under its grant, and the comment-count probe its build waits on¶

Qt's fetch under its 2026-10-15 grant finished the same day: the pilot, train and development months, 2024-10 to 2025-10, from the collector at the announced address, at 2 s, one client, with no stop. A first probe asked Qt for the comments of 60 changes its snapshots record at total_comment_count 0 and of 10 above zero: all 60 returned none and all 10 returned some. Sixty empty answers bound the share of zero-count changes that carry comments only at about 5% (95%, one-sided), too loose for a skip applied to about half of Qt's changes, and the script that wrote that result was edited after it ran, so the result is not kept.

scripts/comment_count_probe.py now samples the rows the build skips: every month's rows the build's own cli.uncommented reads as uncommented, a change recorded at zero in one month and with comments later included as its zero row, 300 of them spread over the months in proportion to each month's zero rows, and three rows above zero from every month as a control. It records a failed request rather than stopping, resumes from the answers it has kept, and writes the 95% upper bound on the share of skipped rows that carry comments (about 1% for 300 empty answers) and the digest of the raw snapshots it asked from. build --fewer-requests refuses to run without --count-probe: a probe for that organization that holds, bounds the share at 1% or less, and asked the snapshots the build reads. Qt's build started at 13bd2a4 with the flag, before that refusal existed; the probe runs from committed code once the build releases Qt's single-client claim. If it does not hold, Qt is built again without the flag, which the build's mode check makes a rebuild of every month.