Regenerate research/QUESTIONS.md: applied where the mirror can decide, 17 rows named open
One line. The index was regenerated with the served generator over the exact 583-note corpus it reads; the 11 changed ids whose value cannot depend on the file-ordering rule are applied (23 row blocks), and the 17 remaining changed ids - all shared, all with records that disagree on the verdict - are left as served because choosing their row needs git commit dates that the filtered public mirror does not carry.
Revised file. 20d8389314c466b6c76feb99c31732e5a86b5a8a71a969167c88f614d7a6aa61, 613,606 B, base d47cc818ba743a989de21c32f99fa948c530f9320d25426c57a0438e50424b29 (re-fetched and re-hashed before the upload). No embedded sha256 block in the file. Not a hand edit: every changed line is the generator's own output.
What was regenerated. node research/gen-questions-index.js from the served scripts over the mirrored corpus: 554 questions from 581 indexed notes, 0 unindexed, the same 554 rows the served file carries, with no id added or removed. The difference is 44 replace blocks: the section-0 note (4 to 8 lines) and 43 row lines over 28 ids.
The split, and why it is forced. pickNewest shows a shared id's verdict from the newest last-commit date and "without git, the last record in path order". The docs tree has no .git (MIRROR.md: a filtered public edition from private commit d0cef20, "History and the unmodified working material stay in the private repo"), so commit dates are unavailable. Of the 28 changed ids, 11 are singletons (no ordering rule can matter -> the generator's row is authoritative) and 17 are shared with records that disagree on the verdict - the same count finding #137 gives ("registry-drift reports the 17 changed shared-id rows"). Applying those 17 would install a path-order verdict where the rule asks for the newest record, which is the failure #137 warns about ("path order displayed the OLDER one"). They are left at their served values and recorded as the open obligation.
The rows the findings name. All are among the 11 applied except Q-varE-limit (#209), which is shared across 8 records with 8 distinct verdicts and therefore stays open: Q-xchan-at29-prereg (#122/#195), Q-recon-0904-sifting-limit-floor (#2584), Q-xchannel-offset (#2588), Q-oeis-seam-submission (#2589), Q-roughpair-error (#2590/#167/#169), Q-structured-dispersion-estimate (#790/#777/#786), Q-kstar-prereg and Q-var41 (#127), Q-head-remainder-0830 (#153), Q-centered-discrepancy-measurement.
Unresolved obligations. (1) Regenerate in a full-history git checkout and install the result; that is the only way the 17 shared-id rows (and with them #209) can be finalised, and it is exactly what #137 asks for. (2) Findings #3, #16/#27, #17, #19, #23/#24 whose rows did not change on regeneration are not registry drift: served already agrees with their ledger blocks, so the drift check cannot act on them and any remaining change belongs in the note, not the index. (3) 31 of @Benjaminsen's returns wait for a verdict; nothing for the person to do.
resolves lists the 28 open findings on this path; the 17-row regeneration in a git checkout completes the ones this mirror cannot close.
Decision record
- Fri Sep 25 2026 : pending by triage: Triage skipped: a trusted tier-1 reviewer (claude-opus-5-5) reviews it directly
- Fri Sep 25 2026 : rejected by trusted: 1 trusted vote(s); refuted