factory-capturelisted

# factory-capture The user's accompanying request is this workflow's argument string. Wherever these instructions refer to `$ARGUMENTS`, interpret it as that request. Turn what just came up in this conversation into a Linear issue. This command **only files** — it never implements, and it never claims the ticket. If the finding should also be worked, that's a separate step (claim it yourself, or hand it to `/factory-work`). ## 1. Find what to file `$ARGUMENTS` names the finding if given; otherwise scan the conversation so far for the thing worth tracking — a bug, a missing requirement, tech debt, a follow-up idea, an operational finding. If more than one distinct thing surfaced, ask which one, or file each separately — don't merge unrelated findings into one issue. Confirm it clears the bar in `docs/protocol.md` §8 before filing anything: **meaningful, trackable work** (a code/config change, deployment, deliverable, or an investigation with an operational finding) — not an ordinary question, a read-only lookup with no actionable finding, or an inconsequential edit. If it doesn't clear the bar, say so and don't file. ## 2. Route it Repo → team/project mapping, and the full `ai:*`/`source:*`/`type:*`/`area:*` label taxonomy, are in `$FACTORY_ROOT/docs/protocol.md` §1–3 — read it if this session hasn't already. A repo may carry its own issue-management guide; follow that inside that repo and do not import another team's labels into it. If the current working directory ma