Plugin submissions reach "Published" but never propagate to the directory — request: remove stuck duplicate cortex/Cortex entries, publish hypermnesia-mcp

Root cause found: the community catalog already contained a plugin named cortex (source: alphaaiservice/cortex) before my Jul 12 submission was published — verified against .claude-plugin/marketplace.json at commit c0a7785d (Jul 11 state). Both of my "Published" submissions (cortex, Jul 12; Cortex, today) therefore collide with an occupied name slug, which would explain why neither propagates to the public directory while showing Published in the Console.

Suggested resolutions:

• surface name-collision failures to the submitter at review time instead of publishing silently;
• advise whether I should resubmit under a distinct name (e.g. cortex-memory) or whether the pipeline can disambiguate.

I plan to resubmit under cortex-memory with my next release unless the pipeline can resolve the collision on your side.

Correction to the above: the resubmission name will be hypermnesia-mcp (matching the existing PyPI package and official MCP-registry entry io.github.cdeust/hypermnesia-mcp), not cortex-memory.

Update (Jul 23) — status changed, revised ask

The console now shows three submissions for the same plugin:

| Submission | Status | Date |
|---|---|---|
| cortex | Published | Jul 12 |
| Cortex | Published | Jul 22 |
| hypermnesia-mcp | Submitted and pending review | Jul 23 |

The "Cortex" resubmission was approved and now also shows Published — yet neither published entry has propagated to the plugin directory. Verified independently:

1. In-app plugin directory search for "cortex" / "persistent memory": zero case-insensitive occurrences of "cortex" in the results.
2. anthropics/claude-plugins-official/.claude-plugin/marketplace.json (main): no "cortex" entry.
3. This appears to be a known, recurring disconnect between the submission portal's "Published" state and the searchable directory index: anthropics/claude-plugins-official#984 (open since March, same symptom, no team response) and anthropics/claude-plugins-official#1272 (identical symptom, closed without documented resolution).

Revised ask

Since "Published" status evidently does not propagate, I have submitted a third entry, hypermnesia-mcp, whose name matches the plugin's MCP registry identifier (io.github.cdeust/hypermnesia-mcp). Please:

1. Delete the two earlier submissions — cortex (Published, Jul 12) and Cortex (Published, Jul 22). They are stale duplicates and should never reach the directory.
2. Keep and process only hypermnesia-mcp (pending review, submitted Jul 23) as the single canonical listing.
3. Investigate why Published entries do not reach the directory index (same root cause as claude-plugins-official#984 / #1272).

This supersedes the dedupe preference stated in the original issue body (which said to keep cortex — that entry is now known to be stuck and should be removed instead).

Correction + probable root cause (Jul 23)

Support clarified that the submission form feeds the community catalog (anthropics/claude-plugins-community), not claude-plugins-official (which is curated separately, no application process). Earlier evidence in this issue checked the official manifest — the wrong target. Re-checking the community catalog changes the diagnosis:

The community catalog already contains a plugin named cortex — and it is not mine. It is "Cortex — SDLC Automation Engine" by Alpha AI (source: https://github.com/alphaaiservice/cortex.git).

Since the plugin name is the unique identifier (per support), my two submissions were structurally unable to propagate:

• cortex (Published Jul 12) — name collision with the existing Alpha AI entry; the sync presumably dropped it silently.
• Cortex (Published Jul 22) — no catalog entry; likely lost to the same collision if name matching is case-insensitive.
• hypermnesia-mcp (pending review) — collision-free; the only submission that can actually land.

Refined asks

1. Bug: the Console shows "Published" for a submission the nightly sync silently discards on name collision. Surface collision failures in the Console at submit time (or at sync time) — this single gap produced three duplicate submissions and this issue.
2. Delete/void my cortex and Cortex submissions (support confirmed there is no self-service deletion).
3. hypermnesia-mcp remains the canonical submission to review and publish.

Happy to close this issue once hypermnesia-mcp lands in the community catalog; the collision-visibility bug in ask 1 is the part that outlives my case.

Root cause confirmed by support (Jul 23)

Anthropic support confirmed the collision diagnosis from the previous comment:

• The duplicate-plugin-name check runs at the marketplace level during the nightly sync, not at submission time in Console.
• A submission is therefore marked "Published" in Console before the duplicate check runs; when the sync then hits an existing name (here: the Alpha AI cortex), the entry is blocked from the catalog with no feedback to the submitter.
• Support acknowledged the workflow should surface name conflicts earlier in the process.
• hypermnesia-mcp (unique name) is expected to propagate normally once it clears review and the nightly sync runs.

So the remaining actionable item for the team is ask 1 from the issue body: validate submission names against the community catalog at submit time (or at minimum flip/annotate the Console status when the sync rejects an entry), so "Published" cannot mean "silently discarded". The stuck cortex/Cortex entries remain as duplicates on my account with no self-service deletion.

Will report back once hypermnesia-mcp lands in the catalog (or fails to).

Cross-reference: this bug has also been reported through the in-product /bug command — feedback report ID 186831c3-5ffa-45a8-99b7-3b34a4c87be9 (filed Jul 24, from a session containing the full verified evidence chain: catalog greps, the colliding Alpha AI cortex entry, and support's confirmation of the sync-time duplicate check). A support ticket covers the account-level cleanup. The scoped review request for hypermnesia-mcp is #80423.

Blast-radius data: this is a funnel defect, not one developer's problem

Measured against the community catalog today: 2,269 plugins, 780 of them (34%) single-token generic names — first-come-first-served collision magnets. Every future submitter who picks an already-taken name hits this exact path: Console says "Published", the nightly sync silently drops the entry, and the developer ships to zero installs with no signal. The probability of that collision rises monotonically with catalog size.

Known victims so far are just the ones who debugged it themselves: anthropics/claude-plugins-official#984 (March, still open), #1272 (April, closed unresolved), and this case (three duplicate submissions produced before support explained the mechanism). The silent-failure design guarantees an unknown number of others simply concluded the directory didn't work and left.

The fix remains one validation call at submit time — the name-uniqueness check already exists in the sync; it runs at the wrong end of the pipeline.