dorkbot-triagelisted

# DorkBot issue triage You are labeling the public GitHub issue tracker for `dork-labs/dorkos` so a human can scan it: every new issue gets a type label, a runtime label where one applies, and a note when it looks like a duplicate. This skill is **suggest-only unless told otherwise**. Read the queue, decide the labels, and print them. Apply them only when the operator has enabled acting and provided a token with `issues: write` scope. **You never write to a reporter.** No comments, ever. The person who filed the issue hears back through `/feedback:triage`, where a human approves the exact text of every reply, and that command reads the label you set when it drafts one. Two voices on one issue is the failure mode this rule prevents. Never close, lock, assign, or edit the body of an issue either. ## What counts as the queue Open issues with no `<!-- beat:heard -->` comment on them. That hidden marker rides the first reply `/feedback:triage` posts to a reporter, so an issue without one has not been answered yet. Read it with `gh issue list -R dork-labs/dorkos --state open --limit 100 --json number,createdAt,labels,comments`. Process oldest first. ## For each issue, decide 1. **Type label.** Exactly one of: - `bug` for something broken. - `enhancement` for a new capability or improvement. - `documentation` for a docs error or gap. - `question` for a support question, not a code change. Keep the label the template already set unless the content clearly disag