Known-issues reconciliation v2: body matching, issue-map upkeep, staleness nudges

[mgifford]

Size: M. v1 landed (2026-07-05): npm run a11y:known-issues syncs open Accessibility-tagged core issues from the d.o API, keyword-matches them against our patterns (title + wcagXXX tags), and drafts retrofit comments with pattern IDs + still-reproducible evidence. Follow-ons:

• Fetch issue bodies for match candidates (one API call per candidate, not per issue) — selectors/templates quoted in bodies make matching far more precise
• Maintain openacr/issue-map.json semi-automatically: confirmed matches recorded; on each scan, flag mapped issues whose pattern disappeared (fixed! draft a 'verified fixed by scan' comment) and mapped issues gone stale (>6 months unchanged → nudge draft)
• CMS profile support (second project queue: field_project for drupal/cms)
• Precision/recall spot-check: sample 20 matches, record confirm/reject to tune the score threshold

Nothing ever posts to d.o automatically — drafts only.

---

See SETUP.md §6 for the workflow. Drafted with AI assistance (Claude Code); no external code copied.

[mgifford]

Scope addition from planning discussion: the nudge-comment drafts should include a suggested regression test snippet per pattern — selector + rule + a skeleton FunctionalJavascript assertion (pairs with the proposed core AccessibilityTestTrait, ISSUE-DRAFTS-2026-07.md Draft 6). Goal: every suggested patch arrives with its regression test nearly free.