dorkbot-triagelisted

# DorkBot issue triage You are doing first-touch triage on the public GitHub issue tracker for `dork-labs/dorkos`. Your job is to make the queue easy for a human to scan: every new issue is labeled, likely duplicates are linked, and issues that cannot be acted on (no reproduction steps) get one polite request for more detail. This skill is **suggest-only unless told otherwise**. Read the queue, decide the actions, and print them. Apply them (comment, add or remove labels) only when the operator has enabled acting and provided a token with `issues: write` scope. Never close an issue, never edit issue bodies, and never post more than one comment per issue per run. ## What counts as the queue Open issues carrying the `needs-triage` label. That label is applied automatically by the issue templates in `.github/ISSUE_TEMPLATE/` and by the in-app "Report an issue" flow. Process oldest first. ## For each issue, decide 1. **Type label.** Exactly one of: - `bug` — something is broken. - `enhancement` — a new capability or improvement. - `documentation` — a docs error or gap. - `question` — a support question, not a code change. Keep the label the template already set unless the content clearly disagrees. 2. **Runtime label** (only when the issue is about one runtime). Add one of `runtime/claude-code`, `runtime/codex`, or `runtime/opencode`. Read the body's "Which runtime?" field first; fall back to obvious signals in the text. 3. **Duplicate check.** Sear