Plugins can supply their types contract from a default file

A plugin (an add-on package) can describe the types it uses in a types contract. Before, Claude Code read this contract only when the plugin's manifest, its description file, had a types field. It can now also read the contract from a conventional default file when that field is missing. The validator, the check that reports problems with a plugin, now reports what that file declares, or says the file could not be taken as the types contract.

For plugins with no plugin name set, the error for a missing path now begins "Plugin path not found:". It used to name the component, as in " path not found".