Twinned from https://github.com/cfsh/ninefold/issues/887 by tools/beads/import_github.py's reconcile pass.
Implement T2 from design_docs/007-reviewer-verdicts-for-readers.md (§8, decision D2). Split out of the umbrella #872 (see also T1, #878, merged as PR #879). Independent of T1 — different file (CHARTER.md vs dispatch.py) — but T3/T4 stack on top of this one, so land it before picking those up.
Goal: every verdict opens with a plain-English lead and puts findings before bookkeeping, so a reader can see in seconds what the review concluded and what the dev must do.
Context. Verdicts average 1,233 words and open with rebase archaeology or ledger tables; the substance (which is good) is buried. This card restructures CHARTER.md's "What to produce" and "Verdict format" sections. The REVIEWER-VERDICT first line, the label-writing block, and the notes-file list (gated by test_charter_notes.py) must survive verbatim.
Files: tools/reviewer/CHARTER.md.
Change — the new verdict body order, after the verdict line: 1. Lead (new, mandatory): 2–3 plain sentences — what the review concluded, exactly what the dev must do next, anything that needs @aedanpope. No shas, no hashes, no section-number references, no labels. 2. Findings (charter section C, moved up): most severe first. Each finding opens with one bold plain sentence naming the failure *as behavior* ("the command the operator pastes does not run"), then file:line, then the fix. When a finding is one instance of a class, say so and instruct the dev to sweep every other site in the same pass. 3. Ask ledger (section A): rules unchanged — verbatim quotes, the six statuses, the denominator rule. Full table on pass 1. 4. Gates + B2 (section B): one line per passing gate; prose only for flags. B2's "say the body is current when it is" rule stays. 5. Writing rules (new charter block): write for a reader who has not read the thread; never introduce a label (F1, C2, A1) without stating in place what it refers to; short sentences; a table only where it beats prose; never restate the PR description; as short as fidelity allows.
Test plan: ./presubmit.py green (test_charter_notes.py proves the notes list survived). Then one real --force review on any open PR; eyeball that the verdict follows the new shape.
PR shape: first PR of the T2→T3 charter stack. Done when: a real verdict posts in the new shape with all ledger statuses intact.
None.
No comments.