gh-triagelisted

# gh-triage Walk the `type:request` queue and convert each item into a decision: real work, rejected, or punt for later. Closes the loop on `gh-request`'s deferred captures. ## When to use - User says "triage requests", "drain the inbox", "review the queue" - The request count in `gh-context` / `gh-status` is creeping up - Pre-planning: before cutting a milestone, drain the requests so anything urgent gets folded in ## What it does ### Step 1 — List the queue ```bash gh issue list --repo {owner}/{repo} --label type:request --state open --limit 100 \ --json number,title,body,createdAt,labels,assignees \ --jq 'sort_by(.createdAt)' ``` Oldest first — the longer something has sat unpromoted, the higher the priority on triage. If the queue is empty, report `No requests to triage. ✓` and exit. ### Step 2 — For each item, ask the user Use `AskUserQuestion` with four options. Title shown is the request body's first line, plus the days-since-filed: ``` Request #{N}: "{first line of body}" Filed {days} days ago by @{author}. [a] Accept as feature → run /gh-pms:gh-feature with this body as objective [b] Accept as bug → run /gh-pms:gh-bug with this body as steps_to_reproduce [r] Reject → close with reason (you'll be asked for the reason) [d] Defer again → leave it; increment a `Deferred` counter in the body ``` ### Step 3a — Accept as feature 1. Call `/gh-pms:gh-feature` with: - `title` = request title (strip `[Request]` prefix if prese