deploy-setuplisted

# Deploy this setup into a project You are installing guardrails into **someone else's working project**. The failure mode is not "install too little" — it is destroying a config that took them months. Eight such incidents are documented publicly; in one, an installer removed an MCP server and reduced four custom agents to stubs, losing ~600 lines while reporting "preserving configuration". Read `docs/instruction-mechanics.md` if you have not. It explains why these specific hooks exist. Do not install mechanisms you cannot explain to the user. ## Hard rules 1. **Never write before showing a plan and getting a yes.** Not a flag, not a default — a stop. 2. **Never overwrite an existing `CLAUDE.md`.** Append inside a marked block, or write alongside. Same for any file the user already has. 3. **Never edit their `settings.json` if the plugin path is available.** Hooks ride in `hooks/hooks.json` inside the plugin. That file is the whole reason this bundle is a plugin. 4. **Install the smallest thing that solves their stated problem.** A profile is a starting point, not a target to fill. 5. **Never claim it works until you have run `tests/run-all.sh` and shown the output.** ## Phase 0 — snapshot Before touching anything: - if the project is a git repo with a clean tree, note the current SHA so the user can revert with one command; if the tree is dirty, say so and ask whether to continue - if `.claude/` exists, copy it to `.claude.backup-<timestamp>/` C