queue-status

原文涵盖的主题

• queue-status
• When to load
• How to use
• What it flags
• Reading the board

Reports the board: how many tasks are open, claimed, done and blocked, and — with --detail — every task with its priority, state, and what holds it up. CANARY: queue-status-loaded-2026-06-13-fb78d23e-d4e5f6a7b8c9d0e1 The user asks how the queue stands, what tasks are left, or types /queue-status. Checking whether every task is done before closing a loop session. Diagnosing a stuck queue. Fetch the arsenal:task issues, open and closed, with whatever GitHub access this surface has, asking for number, title, state, labels, assignees (plus statereason where the surface returns it) and leaving out body — the board is derived from labels and state, and bodies are most of the fetch. Then run querystatus.py (in claude-arsenal/scripts/): It reads the same graph as the selector, so the board matches what a worker will pick next. Without --issues every task shows as open, because state lives in the issues. Problems go to stderr; --fail-on-problems makes them a non-zero exit for a make target or CI job. no-gate — no fenced bash block, so the gate runs nothing and passes everything. no-handle — no issue points at the task, so no agent can claim it. Run handlesync.py and create the missing issue

这里只展示节选，请以完整原文和当前要求为准。