upgradelisted

# Upgrade **Use this when:** The toolkit plugin moved to a new version and this project has files of its own under `.claude/` (commands, skills, agents, rules) or a `CLAUDE.md` that mention toolkit pieces; or `/setup` just migrated a copy-install and handed off here. **Don't use this when:** The project is not on the plugin yet (`/setup` first), or you are inside the toolkit's own repository. Every convention this run checks is written down once, with its id, the version it arrived in, the signal that finds a file behind it, and the shape of the fix: !`cat .claude/skills/shared/conventions.md` ## Critical Rules <rules> 1. **The script finds, the loop judges.** Candidates come from `node .claude/scripts/upgrade-audit.js` plus your own pass over the `manual` conventions. You are M2's runner: every candidate is audited before anything is fixed, and a hit that turns out to be the project's own file dies there with its receipt. 2. **Prompt-file edits page once, as a batch (M9).** The files this run edits are the project's own commands, skills, agents, and rules, which are always-ask. List every file and its finding ids in one page before the first edit; apply on approval, per file where the user says so. 3. **Never edit the plugin.** The fix for a convention is always in the project's file, by the fix shape the convention names. If a fix seems to need a change in the toolkit, that is an issue against the toolkit, and the finding lands in the digest as open. 4. **The toolkit'