pipeline-statuslisted

# Pipeline Status Treat conversation as the primary interface. The user does not need to know or run pipeline commands. Inspect the deterministic state behind the scenes and answer in human language. ## Inspect 1. Resolve the project root with `git rev-parse --show-toplevel`; otherwise use the current directory. 2. If `.pipeline-state.json` is absent, report that the repository is not yet connected to the setup pipeline. Do not create or modify anything during a status request. State one next action: invoke `startup` for a new project, or ask the agent to adopt the existing repository. 3. Run `setup-pipeline status` from the project root. It executes the read-only validator bound to the current phase in `.pipeline-state.json`; a phase-process failure overrides global READY. If the command is missing, report a setup installation/discovery problem and point to `~/setup/docs/human/SETUP.md`; do not guess. 4. Read the phase from `.pipeline-state.json` and run `setup-preflight <phase> <project-root>`. Preflight is read-only and checks the core entry contract. A nonzero result means BLOCKED, not that the project is broken. The specialized validator is an exit/readiness check in status, not an entry guard: otherwise invalid in-phase state could not be repaired. 5. At Phase 7, if entry preflight passes, also run `setup-preflight 7 <project-root> --completion` to distinguish “review can start” from “delivery accepted and complete”. 6. If `.workctl/tasks/`