bug

# Bug Reporting Report and manage bugs for Runners via GitHub Issues with the `bug` label. ## Usage `/bug <action> [args]` ### Actions #### `new` Report a new bug. 1. Ask the user to describe the bug: what happened, what was expected, and steps to reproduce (if known). 2. Investigate the codebase to confirm the area of code involved. Note relevant file paths. 3. **Pick a priority** (see Priority below). If the user didn't state one, propose one based on the bug's severity and the rubric, and confirm before filing. Don't file unlabeled. 4. Create a GitHub Issue with labels `bug` and the chosen `P0`/`P1`/`P2`/`P3`: - Title: `bug: <short description>` - Body using this template: ``` ## Description <what's wrong> ## Expected behavior <what should happen> ## Steps to reproduce <if known> ## Relevant code <file paths and brief pointers to the affected area> ## Environment - OS: <if relevant> - Version: <app version from `crates/runner-app/Cargo.toml`> ``` - Command shape: `gh issue create --label bug --label P1 --title "…" --body "…"` 5. Report the issue URL and the assigned priority. #### `list` Show all bugs, sorted by priority. 1. Fetch open bugs with priority + metadata as JSON so they can be sorted: `gh issue list --label bug --state open --limit 50 --json number,title,labels,createdAt,assignees` 2. Sort the rows by priority (`P0` first, then `P1`, `P2`, `P3`, then unlabeled-by-priority l...