What
With the v5 plugin storage layout pinned on for a session, a plugin whose copy into the versioned cache fails is no longer run from the marketplace clone; it fails to load with an error suggesting a reinstall. Without that layout, the old warn-and-continue behaviour is unchanged.
Details
- The fallback that ran the plugin directly from the marketplace clone is what the strict path removes.
- Separately and unconditionally,
claude pluginCLI failures are now split into expected failure results, which are logged, and unclassified errors, which are reported with a label naming the subcommand that produced them.
Evidence
Not loading it from the marketplace clone (strict plugin cache).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.