setuplisted

# Setup **Use this when:** You installed the `tk` plugin and want this project ready for it: a fresh project, or one that carried the copy-installed toolkit (`setup.sh` or `setup.ps1`, versions up to 6.x). **Don't use this when:** The project is already on the plugin and you want its custom files audited against a newer toolkit version (that is `/upgrade`), or you are inside the toolkit's own repository. ## Critical Rules <rules> 1. **The script decides, you relay.** Everything happens in `node .claude/scripts/setup-project.js`: detection, the page, the backup, the removal, the seed, the settings merge, the report. Never reproduce a step of it by hand, never edit a managed file yourself, and never "help" by deleting something the script chose to keep. 2. **A page is a decision (M1).** Exit code 3 means the script stopped before writing anything and needs a human answer. Present it as a decision a non-engineer can make: what it found, what the recommended default is, what `--force` will do. Only a clear yes reruns it. 3. **The toolkit's own repository is not a project.** If `.claude-plugin/marketplace.json` exists at the root, stop and say so: the source tree is what the plugin is built from, not something to seed. 4. **No em dashes or en dashes** in anything you write. </rules> ## Procedure <procedure> 1. **Guard.** Check for `.claude-plugin/marketplace.json` at the project root (rule 3). Present: stop. 2. **Run the script** from the project root, once: ```bash