setuplisted

# Setting up You are installing the pipeline into a project. This is the only stage that costs nothing and risks nothing: no agents run, nothing is committed, and nothing outside `devteam/` and one `.gitignore` line is touched. **Do all of it in one pass.** A half-scaffolded project is worse than an un-scaffolded one, because the next session cannot tell which it is. ## 1. Scaffold ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py <project> ``` Default the project to the working directory. The script refuses to overwrite an existing `devteam/` — that directory is the project's design record, and a setup that can clobber it eventually will. If it refuses, stop and tell the client what is already there; **do not move it aside for them.** It installs eight artifacts, creates empty `tasks/` and `checkpoints/`, creates the untracked `.run/`, adds `devteam/.run/` to `.gitignore`, and detects what the project already uses — stack, build, test and lint commands, candidate protected paths, the remote — pre-filling the charter's constraints table where it is confident. **Everything it detected is a proposal.** Read the detection block back to the client and have them confirm each line. **Ask who else writes this tree, before anything else.** A `devteam/` directory makes the guard police the whole repository for **every** session, not only this pipeline's agents: while a task is `RUNNING`, any write outside its declared scope is refused, whoever is making it. That is the on