You'll notice
Plugin settings migration now checks policy before assuming an already-installed plugin can be skipped
What
When migrating plugin settings, Claude Code previously took a fast path that skipped migration entirely if all plugins already appeared to exist. Now it also cross-checks each managed-scope entry against policy rules (such as managed MCP or marketplace source restrictions). If a plugin is blocked by policy, Claude Code no longer writes a record for it and logs a short message: "Skipping [name]: blocked by policy, not writing a record."
Why
This prevents a plugin that policy would otherwise disallow from being treated as validly installed just because a record already existed.