factory-statuslisted

# Show where the pipeline stands Input: the project's files — the story journals under `tasks/<story>/.verify/`, the decision records under `.agents/factory/decisions/`, the backlog. Output: an answer in the session. You write nothing, start nothing and answer nothing on anyone's behalf. ## Do 1. **Run the one command.** From the project root: ``` bash .agents/factory/factory.sh status ``` (`python3 .agents/factory/story-gate.py --status` where the project has no runner copy.) It prints four sections — *running*, *waiting for a human*, *stories*, *cost*; the cost is a table with one row per story and the total. Asked about one story, run `bash .agents/factory/factory.sh status <story>` instead: the same look, with that story's cost per stage. Show it as it is; where the gate is not installed, say so and stop rather than reconstructing it by hand. 2. **Lead with what needs someone.** An open decision blocks its story and everything that depends on it: name it first, with the story it blocks, and point to `/factory-decisions` to answer it. 3. **Name a duplicate pipeline.** A `note:` line under *running* says the dca-factory plugin is enabled for the person while the project holds its own copy: stages run in a session may then pick the plugin's skills. Say so, and that the runner's stages see only the project's. 4. **Say whether a session listens.** `listening:` names the session that last looked at the backlog and when. A look within