chameleon-initlisted

# /chameleon-init Bootstrap a chameleon profile for the current repo, then auto-apply rename proposals so the archetype labels match the team's vocabulary without a user interview. Profile artifacts are written atomically via the commit-marker pattern. ## When to use User runs `/chameleon-init` in a TypeScript or Ruby on Rails repo that does not yet have a `.chameleon/` directory. If `.chameleon/profile.json` already exists, suggest `/chameleon-refresh` instead — running init twice would overwrite the existing profile. ## The flow (overall) 1. Confirm the repo's language: TypeScript (`tsconfig.json` or TS in `package.json` deps) or Ruby on Rails (`Gemfile` with rails, or `config/application.rb`). 2. Call `chameleon-mcp::bootstrap_repo(path=<repo_root>)`. 3. The tool runs the full pipeline (workspace detection, tool config reading, discovery, AST parse, clustering, canonical selection, atomic profile commit). Archetypes start out with heuristic names like `controller`, `react-component`, `service`, `migration`. 4. **Auto-apply rename proposals** (see below) so cluster-* / class-* / numeric-suffix fallback names get replaced with the team's vocabulary. 5. Report the BootstrapReport to the user: archetype count, files processed, duration, profile path, and what got renamed. 6. Suggest the user run `/chameleon-trust` to approve the profile for their session. ## Default: auto-apply renames (no user interview) Renames are purely cosmetic — they just rek