happier-issue-triage

# Happier Issue Triage Turn a raw issue set into coherent diagnosis bundles and select who owns each diagnosis. Triage routes work; `skills/happier-issue-diagnose` establishes technical truth. The triage lane may become the diagnosis lane when all requested issues form one coherent bundle. For multiple materially independent bundles, use the topology the user requested or ask once when the choice between native subagents and independent Happier sessions would change where results arrive. ## 1. Normalize the request Resolve four independent facts: - **Issue set:** explicit issue URLs/numbers, query, label, milestone, or backlog scope. - **Depth:** triage only, triage plus diagnosis, or triage plus proposed fixes. None authorizes implementation. - **Topology:** main lane, native subagents, independent Happier sessions, or not specified. - **Authority:** read-only by default; GitHub write-back and repository changes require separate explicit authority. A broad request to triage, organize, update, or clean up issues does not authorize a GitHub mutation without the exact preview and human approval required by `skills/happier-github-ops`. If the issue set is ambiguous, resolve it before retrieval. If only one issue is requested, use `skills/happier-issue-diagnose` directly unless corpus-level duplicate or relationship analysis is material. ## 2. Retrieve efficiently and safely Use `skills/happier-github-ops`. Batch-fetch compact issue metadata for the corpus first, then dee...