tooling(qa): roll-up script over qa-run records — area × latest-verdict × staleness matrix for the wave anchor #9486

Maintainer authorization (2026-08-18, PM chat, skills-seat session session_01Rn7aaamsR99FXRqLcpL99q): 「同意你的落地动作」, approving the QA management-loop design, item 4.

What

A small script (suggested home scripts/qa/qa-rollup.mjs) that answers the one question no current view answers: "what is the latest verdict for every checklist item/area, and is it stale?" — today that takes reading 14 issues by hand.

• Input: qa-run issues (open and closed), read via the GitHub API — title convention QA run · <selector> · <judged>/<total> · <sha8> · <date> · <counts> plus the per-item verdict tables the records carry.
• Output: a markdown matrix — area × latest verdict counts (PASS/PARTIAL/FAIL/BLOCKED/NOT-RUN) × the subject sha it was measured on, flagged stale when that sha is behind the current comparison target; plus the open-record (close-out debt) count. Suitable for pasting as a wave-anchor comment.
• Latest-per-selector wins: a superseded record never shadows its replacement.
• It is a generated VIEW, not a tracker (one board rule): no state is written anywhere; the run records stay the only source of truth.

Readers (named, per the label/reader rule): the wave PM planning the next round's selectors; the maintainer reading test status.

Triage note: routing suggestion domain:devx (general scripts/ tooling) or domain:skills (PM-loop adjacent) — triage decides; not scripts/pm/**, so no fable path mandate.