Stale pre-migration submission blocks re-listing: scalixworld/scalix-cloud-mcp

Hi team,

We submitted our plugin repo (https://github.com/scalixworld/scalix-cloud-mcp) through the previous cursor.directory submission flow on 20 July 2026. It confirmed receipt (scan queue) but never went live - searching the directory for "scalix" returns no results today.

Since the relaunch under the Open Plugins standard, attempting to resubmit the same repo via /plugins/new fails with "A plugin with this name or repository already exists" - so the pre-migration record appears to survive as an unpublished row that blocks the repo slot, with no way for us to manage or publish it from an account.

Could you either publish the existing entry or clear the stale record so we can resubmit cleanly through the new flow?

Listing details, for reference:

• Name: Scalix Cloud
• Repo: https://github.com/scalixworld/scalix-cloud-mcp (conforms to Open Plugins; auto-scan detects the MCP server component correctly)
• Component: hosted remote MCP server (HTTP), https://api.scalix.world/v1/mcp
• Also listed in the official MCP registry as world.scalix/cloud

Happy to provide anything else needed. Thank you!

Start at the /plugins/new submission entry point and trace the duplicate name or repository check back to the pre-migration record lookup. Reproduce the failure with scalixworld/scalix-cloud-mcp, then verify that the stale entry can be published or removed and that a clean resubmission succeeds.