autoresolve-oldest-github-issuelisted

## Constraints - Apply `@rules/git/general.mdc` - Apply `@rules/reports/general.mdc` - Operate on the current Git repository's GitHub remote only — refuse if the remote is not GitHub - Process exactly **one** issue per invocation; never loop into a second issue - Never bypass quality gates of the delegated skills (`resolve-issue`, `code-review-github`, `process-code-review`, `merge-github-pr`) - **Code review is a hard merge gate** (`@rules/git/general.mdc` *Merging*): never reach step 6 (merge) until steps 4–5 have run a code review on the PR's final diff and driven it to **0 Critical + 0 Moderate**. A merge without a converged code review is forbidden — do not skip or reorder steps 4–5 to merge sooner. - Never force-merge: stop on merge conflict, failing CI, missing approvals, or unresolved Critical/Moderate CR findings - Never alter the original issue body, labels, or assignees outside what the delegated skills already do. Exception: `resolve-issue` applies the `Resolve_by_AI:in-progress` claim label at the start of work and releases it on a pre-PR Blocked/abort — this is a sanctioned write owned by the delegated skill, not a constraint violation. - Do not expose sensitive/internal details in user-facing messages ## Use when - The user wants the oldest open GitHub issue auto-resolved end-to-end (resolve → review → process feedback → merge) - A scheduled or batch workflow needs a single deterministic entry point that chains the four skills ## Inputs - `LABEL` (optional) —