v0.52.1

Patch Changes

• b757970: trace -- --aggregate and --map read the GitHub events of every row and pull request the window's wakes name (a11ign/a11ign#3688). The store held a record only for the rows a pull request MERGED IN THE WINDOW closed, so a repeat of an order about an open row, a row closed another way or in an earlier week, or a pull request that was not one of the week's merges had nothing to be judged by and read unexplained: 349 of the 599 repeats of the week of 2026-09-28 (measured 2026-10-05, trace -- --aggregate --since 2026-09-28). githubEventsOfNamed reads them after the merged reading, through the same budgeted gh (--calls, the pool floor, the pace), oldest naming first, so a stop leaves the NEWEST wakes' subjects unread, and returns what it did not reach by name. A subject the store already settles (a closed row, a merged or closed pull request) is not read again; an open one is read on every run, because its record grows and a stored reading of it can be stale (a stale reading would print unchanged for a repeat that did follow a change, which is worse than unexplained). A subject GitHub refuses is named in the footer with GitHub's words and the next is still read. A key that names no subject (ready-queue-empty, org-health) reads nothing and stays unexplained, correctly. The footer's GitHub line gains subjects the wakes name, not yet read: N and the subjects it could not read.