factory-reportlisted

# factory-report The user's accompanying request is this workflow's argument string. Wherever these instructions refer to `$ARGUMENTS`, interpret it as that request. Give a snapshot of where the factory pipeline stands, across Linear, right now. Read-only — this never claims, triages, or dispatches anything. ## 1. Resolve scope Default: every repo in `config/repos.yaml`. `$ARGUMENTS`, if present, names one repo (matches `factory queue --repo <name>`'s matching). ## 2. Gather From the factory checkout (or any cwd with `factory` on PATH): ```bash factory queue --repo <repo> # omit --repo for every configured repo factory digest --repo <repo> # omit --repo for every configured repo ``` `queue` gives per-repo counts (Triage, Todo-not-ready, READY to dispatch, In Progress, In Review, Blocked, Done/total) plus which tickets are startable right now and how many open PRs are waiting on merge. `digest` lists every `ai:blocked` hold with its age and whether a reply has landed (which means the next triage tick will re-examine it). Both are cheap, read-only, and already read the same queue snapshot the pipeline itself uses — don't re-derive counts by querying Linear directly. ## 3. Report Synthesize, don't just relay raw terminal output (the ANSI coloring won't survive into chat). Structure: - **Headline** — total tickets across scope, and the one-line pipeline constraint: is it starved for specification (deep Triage, empty ready queue), starved for dispatch slots (re