Plugin type declarations now placed in .claude-plugin/types instead of via /plugin-types

What

A type contract is a declaration file that describes what a plugin offers, so the editor can check code written against it, for example in a hooks module or mod. Claude Code now places these files inside the mod itself, and its own texts no longer send you to /plugin-types:

• Contracts for plugins you depend on: a mod that lists a plugin under dependencies gets that plugin's contract at .claude-plugin/types/<plugin>/index.d.ts when the engine loads the mod from a folder you own. Before, /plugin-types copied each enabled plugin's contract to .claude/types/claude-code-plugins/<plugin>.d.ts.
• Claude Code's own declarations: the error about a skill folder the engine could not write now says the same declarations are in the mod's .claude-plugin/types/claude-code/index.d.ts once the engine has loaded it. It no longer mentions /plugin-types <dir>, which used to write claude-code.d.ts into a folder you chose.
• MCP tool types: the header of the generated file now says the types reflect the MCP tools the session had connected when the mod was last saved, and that the file is written again whenever the mod is saved with a server connected. It no longer says it is written by /plugin-types or tells you to regenerate rather than edit.
• The pluginTypes entry is removed from an internal state map.

Why

If you write hooks modules or mods, the type files you rely on now come from loading and saving the mod rather than from running /plugin-types, so look for them under .claude-plugin/types instead of .claude/types.