UX: disabling a project-scope plugin you're actively developing triggers an unexpected model-elevation safeguard

What happened

While developing a plugin and iterating on its project-scope install (plugin enabled via a checked-in .claude/settings.json, enabledPlugins), attempting to disable/uninstall it at the project level triggered a safeguard that switches the session model to Opus.

Why it's strange

For a plugin author iterating on their own plugin — install, test, disable, edit, reinstall is a normal inner-loop — a model-elevation safeguard fired by a routine disable action is surprising and feels misplaced. Disabling a project-scope plugin is a config edit (it ultimately resolves to a settings.json/settings.local.json change), not a high-stakes action that warrants escalating the model.

Expected

Disabling/uninstalling a project-scope plugin should be a plain config action with no model switch, especially in a plugin-development context. If the safeguard exists for a specific risk (e.g. project-shared settings affecting collaborators), it would be clearer to surface that reason explicitly rather than silently elevate the model.

Environment: Claude Code 2.1.175, macOS.