update-review-checklistlisted

# DLC: Update Review Checklist Cluster recurring reviewer themes across recent merged PRs and open a PR that proposes new entries for the target repo's `docs/code-review-checklist.md`. The skill never auto-merges — every proposal is human-reviewed. **Standalone:** `/dlc:update-review-checklist [<owner>/<repo>] [--lookback 30d] [--threshold 2] [--dry-run] [--unattended]` **Scheduled (recommended monthly cadence):** ```text /schedule '0 0 1 * *' /dlc:update-review-checklist <owner>/<repo> ``` ## Why This Matters A `docs/code-review-checklist.md` doc decays without a forcing function. Manual curation lapses after the first few months and the checklist drifts away from what reviewers are actually catching in PRs. Reviewer attention is the most expensive resource on the team — when the same class of finding shows up in two or more PRs, the checklist deserves an entry so the next author catches it before review. The recurring nature is the entire signal. A one-off finding is noise; a finding that recurs across multiple PRs is a pattern. Monthly cadence gives enough signal to cluster without flooding the checklist with low-recurrence entries. A run that finds zero promotable clusters is a healthy result — it means recent reviews have surfaced novel issues, not the same ones again. ## Notification Rules `PushNotification` fires only for **terminal states that benefit the user knowing about**: - `pr_opened` — a checklist update PR was opened (include the PR URL) - `pending_hu