[FEATURE] Plugin directory: let the publisher change the plugin path of a published submission

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

In the plugin directory portal (claude.ai/directory/manage → a plugin → Ajustes/Settings → Origin), only the tracked branch or tag can be changed. The portal says: "Only the branch or tag can change here. To use a different repository or path, make a new submission."

That turns a routine repository cleanup into a choice between two bad options for a plugin that is already live:

• Keep the path. CSalcedoDataBI/dax-for-agents was submitted with the plugin path at the repository root, so every version ships the whole repository, 1,054 files including lab projects, docs and tests. Every version is held under "Files or downloads the validator couldn't inspect", and the waiver applies to one version only, so every release waits for a reviewer.
• Make a new submission. That creates a second record for the same plugin. #45051 shows what that can do: several "Published" entries for one plugin, with /plugin install resolving to the oldest. It is also unclear what happens to the current listing, its install history, the users who installed from it, and the plugin's name.

The fix on the publisher's side is already done and validated: the plugin now lives in plugins/dax-for-agents, with fewer files, and the repository's marketplace points at it. What is missing is a way to tell the directory.

Proposed Solution

Make Plugin path editable in Settings → Origin, the way Tracked branch or tag already is:

• Saving a new path scans the newest commit at that path as a new version, exactly as changing the branch does today.
• The listing keeps its identity, name, install history and existing installs, which update in place.
• If the new path fails validation, the live version stays up, as it does for any failed version.

Alternative Solutions

• A "move this submission" request in the portal that a directory reviewer approves.
• Today the only route is email to directory@anthropic.com. The same kind of change has been made by hand for a marketplace entry before (anthropics/claude-plugins-official#5787, Qodo moved to git-subdir packages/qodo with "Identity is unchanged… existing installs update in place"), so the backend can do it. It just isn't exposed to the publisher.

Priority

Medium - Would be very helpful

Feature Category

Plugins / Plugin directory

Use Case Example

1. A plugin is submitted from the repository root because that is where .claude-plugin/plugin.json sat at the time.
2. The repository grows a lab, docs and tests. Every version is now held for a reviewer because of the file count.
3. The author moves the plugin into plugins/<name>/ and validates it with claude plugin validate.
4. In Settings → Origin they change Plugin path to plugins/<name>, save, and the next scan validates only that folder. The listing, its name and its users carry on.

Additional Context

Related: #98317 (notes for the reviewer), #45051 (several submissions of one plugin, the oldest one installed), anthropics/claude-plugins-official#6276 (a stale submission holding a repository and path).