oss-pr-planlisted

# OSS PR Plan Load state and determine the next batch of PRs to analyze. Generalized version of `codex-pr-plan` that works for any repository. ## When to Use Invoked at the start of each `oss-pr-lessons` iteration. ## Non-Negotiable Rules | # | Rule | Violation Example | Correct Pattern | |---|------|-------------------|-----------------| | 1 | Always read state.json before fetching PRs | Fetching PRs without checking processed list | `cat ~/.claude/{repoSlug}-pr-lessons/state.json` first | | 2 | Batch size is exactly 5 | Processing 10 or 20 PRs at once | Fetch 5 closed PRs per iteration | | 3 | Use cursor for pagination | Re-fetching from page 1 every time | Use `state.json.cursor` | | 4 | Skip already-processed PRs | Analyzing PR #123 that's in processed_prs | Filter out all IDs in processed_prs and skipped_prs | | 5 | Include both merged AND closed-unmerged PRs | Only looking at merged PRs | Closed-unmerged PRs teach what NOT to do | | 6 | Validate the batch manifest against state before critic work starts | Selecting #123, then noticing later it was already processed | Print the final 5 IDs and confirm none exist in processed_prs or skipped_prs | ## Parameters - **repoFullName**: `owner/repo` (e.g., `microsoft/vscode`) - **repoSlug**: URL-safe slug (e.g., `microsoft-vscode`) ## Pre-Plan: Registry Eligibility Check Before planning PR analysis, check if the repo is eligible. (`~/.claude/hooks/oss-registry-check` is not yet implemented; the 126/127 branch below alre