v0.51.0

Minor Changes

• df2ead4: trace -- --aggregate and trace -- --map no longer read GitHub through the search API (30 calls a minute per user, 1,000 results at most), and trace -- <row-or-pr> finds a row's pull requests without it too. The merged pull requests of a window come from each repository's pull-requests list, newest update first, read until a page reaches a pull request last updated before the window (a list not finished in 30 pages is refused, naming --since, rather than cut short); the pull requests that close a row come from the row's own timeline. The first line a run prints, before its first call, now says what it may spend: at most --calls gh api calls, all on the REST core pool (a reply from any other pool is refused), at least 250 ms apart, and a stop when X-Ratelimit-Remaining falls under 500. At that floor a run stops, says "STOPPED AT THE FLOOR" in its footer beside the X-Ratelimit-Remaining it saw at its first and last reply, and the weeks that depend on what it did not read are PARTIAL, exactly as when --calls is spent; with --json 1 the line goes to stderr so stdout stays the JSON. Merged pull requests are taken in order of merge, so the rows a report lists (and the first eight of a "and N more" list) no longer depend on the order GitHub happened to return them. The weekly figures of a complete week are unchanged: measured on one store, the old and the new reader print the same 73 non-row-list lines of the complete week and the same current week, and differ only in which rows the truncated row lists show first.