updatelisted

# Update the studio Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. ## Phase 1: Detect the mode and versions Plugin mode: `claude plugin list --json` shows `web-studio` → current plugin version and install path. Copy mode: `.claude/.web-studio-version` exists and `.claude/agents/technical-director.md` is present → kit path from `--kit`, or ask. Read the kit's `CHANGELOG.md` (from the plugin cache or the kit repo) and show entries newer than the installed version. ## Phase 2: What will change Plugin mode: `claude plugin update web-studio` updates agents/skills/hooks automatically; then compare the plugin's `docs/` and `rules/` with `.claude/docs` and `.claude/rules` (`diff -rq`) — list files that differ and whether the difference is a local edit (present only in the project) or an upstream update. Copy mode: `install.sh <project> --dry-run`; the same diff for locally edited files. ## Phase 3: Apply "Update v[X] → v[Y]? Locally edited files [list] would be overwritten — keep copies in `.claude/local-overrides/`?" The list of locally edited files (present only in the project, or differing from the plugin in a way the plugin's own history does not explain — e.g. a project column added to `agent-roster.md`) is printed **before** the question, and the question always carries the option "keep copies in `.claude/local-overrides/` and re-apply after seeding"; the skill never decides on its own that a