marketplace.json: plugin name "claude-in-chrome-troubleshooting" uses the reserved claude- prefix, failing strict validation for any PR that touches the manifest

Summary

.claude-plugin/marketplace.json declares a plugin whose name uses the reserved claude- prefix, so strict manifest validation fails for any PR that touches that file — even one that only bumps an unrelated plugin's version.

Evidence

Validator output from the Validate plugins and skills job:

✘ Found 1 error:

  ❯ plugins[3].name: Plugin name "claude-in-chrome-troubleshooting" is reserved:
    it passes as one of Anthropic's own. A third party's plugin name cannot start
    with "claude-", "anthropic-", "anthropics-", or "cc-plugin-", be "claude",
    "anthropic", "anthropics", "claude-code", or "claude-mods", or put "official"
    beside "claude" or "anthropic". Name it for what it does.

plugins[3] resolves to .claude-plugin/marketplace.json line 40:

{
  "name": "claude-in-chrome-troubleshooting",
  ...
  "source": "./plugins/claude-in-chrome-troubleshooting"
}

The entry and the plugin directory both exist on main unchanged, so this is pre-existing rather than introduced by any recent PR.

Impact

Any pull request that modifies .claude-plugin/marketplace.json — including a one-line version bump for an unrelated plugin — triggers whole-manifest strict validation and fails on this entry. Contributors cannot tell from the check summary that the failure belongs to a different plugin than the one they changed.

Suggested fix

Rename the plugin to drop the reserved prefix, e.g. chrome-mcp-troubleshooting or chrome-extension-connectivity. That means updating, consistently:

• .claude-plugin/marketplace.json — name (line 40) and source (line 46)
• plugins/claude-in-chrome-troubleshooting/.claude-plugin/plugin.json — name (line 2)
• the directory itself, and its README.md install/command references (lines 26, 31)
• the root README.md table entry (line 139)
• CODEOWNERS (line 10) — currently @dguido @kz-tob, hence this issue rather than a drive-by PR

Note

Surfaced while fixing an unrelated version bump in a public PR. I did not fold the rename into that PR, since it changes a plugin owned by others and is outside the scope of a version bump.