Preserve Claude plugin rename across v2 migration

[devantler]

🤖 Generated by the Agentic Engineer

Description

agent-plugins v2.0.0 removed the marketplace identity automated-ai-engineer and moved its resources into agentic-engineering, but the marketplace does not declare Claude Code's top-level renames migration map. Existing consumers therefore retain an enabled automated-ai-engineer@devantler-plugins key that no longer resolves after refresh.

This was observed in the monorepo consumer immediately after PR #80 merged: Claude Code skipped the configured plugin as orphaned and reported that it was not found in any registered marketplace. A clean install of agentic-engineering@devantler-plugins v2.0.0 succeeds, proving the published v2 plugin payload itself is valid.

Steps to Reproduce

1. Install and enable automated-ai-engineer@devantler-plugins from marketplace v1.
2. Refresh the marketplace to the v2 default branch after feat!: consolidate autonomous agents into agentic-engineering #80.
3. Start Claude Code with the old enabled-plugin key still present.
4. Observe that the old plugin identity cannot be resolved; the consumer must migrate manually.

Expected Behavior

Claude Code follows an append-only marketplace rename from automated-ai-engineer to agentic-engineering, loads the surviving plugin, and rewrites editable settings scopes automatically.

Actual Behavior

The old enabled-plugin key is orphaned because .claude-plugin/marketplace.json has no renames entry. Consumers see a missing or failed plugin until they manually register the marketplace and install the new identity.

Environment

• OS: macOS
• Claude Code: 2.1.206
• Marketplace revision: 31df7adb59f12f635c5fc7be13e09e61bc5f731a
• Related consumer issue: chore(agents): migrate consumer to agentic-engineering plugin v2.0.0 monorepo#2403

Acceptance Criteria

• Both marketplace manifests contain the append-only mapping automated-ai-engineer → agentic-engineering and remain in parity.
• The repository guard rejects a missing, malformed, cyclic, or dangling rename migration.
• The guard's hermetic self-test covers valid and invalid rename cases.
• claude plugin validate . passes against the released marketplace shape.
• A v1-style enabled plugin setting is exercised through Claude Code and migrates to the v2 identity without manual uninstall/reinstall.

Additional Context

Claude Code documents renames specifically for plugin removal or identity changes and says the history should remain append-only: https://code.claude.com/docs/en/plugin-marketplaces#rename-or-remove-a-plugin

Rough size: S.

[coderabbitai]

🔗 Related PRs

#32 - ci: guard README plugin table ↔ filesystem parity [merged]
#35 - refactor: rename the copilot plugin to agentic-engineering [merged]
#36 - feat: bundle in-house agent-skills into category plugins [merged]
#46 - feat(gitops-kubernetes): bundle the flux-troubleshooter custom agent (first agents/ resource) [merged]
#53 - fix: omit skills/agents path fields so plugins install in Claude Code [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!