mesh-issues: review — one judgement at a time with new issues first, one verdict applied at a time, a resolved issue left alone on redelivery, the pass's answer a copy (hq ADR 0278)

An independent review found a pass could starve new issues' checks, two writers could apply one verdict twice, a judged issue resolved by a person could still be linked, and the dry run's answer raced its pass.
2026-10-10 17:20:07 +02:00
parent f58840b8a6
commit a5c38892a7
3 changed files with 118 additions and 13 deletions
@@ -63,6 +63,10 @@ older ones not resolved and not found a duplicate in the same pass. It writes on
 `grooming` (the last pass, one key), and applies that pass's findings on `confirm` — never a fresh judgement.
 A finding whose issues have moved on is skipped and said. It adds no "none" note to the backlog.

+The tracker asks one judgement at a time; the pass waits while a new issue's check is waiting, and one verdict is
+applied at a time. A check may take up to a minute (two judgements of at most 25 seconds each), which the tool
+runner allows a handler while keeping its event alive (hq issue 387).
+
 ## The import of hq's issues (slice 3)

 `issue-tracker.import` reads every `04-ISSUES/NNN-slug/00-report.md` of hq **through the records module