A whole-tree address form for marketplace clone files exists with no caller in this build.
What
Claude Code's governed storage layer, which names files it is allowed to touch, previously named only the two engine-written files of a plugin marketplace. It now also has a form that names any file inside a marketplace clone by relative path under <configHome>/plugins/marketplaces/<marketplace>/. Nothing in this build calls the builder for it, so no marketplace file is addressed this way today.
Details
- Supporting machinery is complete: a schema variant, a symlink policy that follows links only for the tree form and refuses them otherwise, a per-tree link budget, and a guard so
plugins/marketplacesitself cannot be treated as a scope. - Creating a scope for the namespace is refused: a marketplace tree is produced by cloning or publishing, not by the scope creator.
- Deleting the namespace's scope is refused outright, with a message saying the retirement path does not exist yet.
Evidence
a marketplaceCache tree is made by its clone or publish, not by ensureScope
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed plugin skills whose frontmatter name already includes the <plugin>: prefix showing it doubled in the slash menu (e.g…