Installed plugin layout doesn't match marketplace.json/docs (stale aidlc-inception/construction + agentic-platform vs current aidlc/ai-infra)

[devfloor9]

Summary

After installing via the documented flow, the plugin set present locally does not match the plugin set defined by .claude-plugin/marketplace.json and described in the docs.

Evidence

Repo / docs say — 4 plugins (.claude-plugin/marketplace.json, plugins/, getting-started.md):

Plugin	Source
ai-infra	./plugins/ai-infra
agenticops	./plugins/agenticops
aidlc	./plugins/aidlc
modernization	./plugins/modernization

Local install actually has — 5 plugins, different names (~/.claude/plugins/ symlinks + ~/.claude/plugins/cache/oh-my-aidlcops/, v0.1.0):

Local plugin	Note
agentic-platform	not in current marketplace.json
agenticops	matches
aidlc-construction	current repo merged this into aidlc
aidlc-inception	current repo merged this into aidlc
modernization	matches
(missing) ai-infra	present in repo, absent locally

So: aidlc-inception + aidlc-construction were consolidated into a single aidlc plugin, agentic-platform was dropped, and ai-infra was added — but an installed environment from the earlier structure still carries the old layout, and there is no migration note covering the rename/consolidation.

Additional structural inconsistency (independent of staleness)

The docs describe two install paths that produce different results:

1. Native marketplace (/plugin install …) → recorded in installed_plugins.json, shows in /plugin list.
2. scripts/install/claude.sh / oma setup → creates symlinks under ~/.claude/plugins/<name>/ pointing at ~/.oma/plugins/…, which (the docs admit) do NOT appear in /plugin list.

In my environment only path 2 is present: the OMA plugins exist as legacy symlinks but are absent from installed_plugins.json (which lists only non-OMA plugins). The result is a confusing split where "installed" depends on which method you used, and the symlink layout reflects the pre-restructure plugin granularity.

Suggested actions

• Add a migration note: old aidlc-inception / aidlc-construction / agentic-platform → current aidlc / ai-infra, with cleanup steps for stale symlinks + cache.
• Reconcile the two install methods in the docs (which is canonical; what /plugin list should show after each).
• Consider having the install script detect and warn about pre-restructure layouts.

Verification notes

• Verified against repo main: marketplace.json and plugins/ both list exactly the 4 current plugins.
• Verified locally: symlinks + cache under ~/.claude/plugins/ carry the 5 old-named plugins (v0.1.0, dated 2026-04-30); installed_plugins.json contains no OMA entries.
• Inferred (not fully verified): part of the mismatch is a stale local install predating the repo restructure. I did not re-read the current scripts/install/claude.sh to confirm whether it still emits the old plugin names today — maintainers should confirm whether this is purely stale local state or the current script also reproduces it.

[devfloor9]

Re-verified against repo main today — confirming the repo-side root causes behind this mismatch, filed as focused issues:

• Plugin version skew: /plugin list shows 0.1.0, docs claim 0.4.0-preview.1 #58 — all four plugin.json still pin version: 0.1.0 (marketplace/tag say 0.4.0-preview.1). Per the CC spec plugin.json wins, so even a fresh native install shows 0.1.0 in /plugin list, independent of any stale symlinks. This explains the v0.1.0 you observed.
• Ontology runtime is not delivered by /plugin install (schemas + seed + session hook live outside plugins) #60 — the two install paths diverge by design: the marketplace path ships only plugin-root dirs, while ontology runtime (schemas/seed/session-hook) lives at repo root and is delivered only by scripts/install/claude.sh / oma setup. That is the structural source of the "installed depends on which method" split this issue notes.

The current scripts/install/claude.sh does emit the 4 current plugin names (not the old aidlc-inception/aidlc-construction/agentic-platform), so the 5-old-name layout you saw is purely stale local state predating the restructure — a migration/cleanup note is still warranted as you suggest.