wporg-mcp-server creates duplicate plugin submissions instead of updating existing ones

[raftaar1191]

While testing the wporg-mcp-server integration with plugin submissions, I encountered an issue where re-uploading a plugin ZIP does not update the existing submission. Instead, it creates a new plugin entry in the review queue.

This behavior can easily lead to accidental duplicate submissions.

During testing, I unintentionally created multiple submissions (currently 4) for similar plugins.

Affected Plugins

• *AI Provider for llama.cpp* Slug: ai-provider-for-llama-cpp Note: This is a duplicate submission and should be withdrawn (the intended plugin is ai-provider-for-llamacpp).

• *Disable AI Toolkit 2* Slug: disable-ai-toolkit-2 Note: This is a duplicate submission. The intended plugin to keep is disable-ai-toolkit.

Steps to Reproduce

# Submit a plugin via wporg-mcp-server.
# Attempt to re-upload the plugin ZIP for the same plugin.
# Observe that a new plugin submission is created instead of updating the existing one.

Expected Behavior

Re-uploading a plugin ZIP should update the existing submission (or provide an option to do so), rather than creating a new entry in the review queue.

Actual Behavior

Each upload creates a separate plugin submission, even when it appears to be the same plugin.

Additional Observations

• There does not appear to be a submission limit (I may be mistaken, but I was able to submit 4 plugins consecutively).
• No validation exists to detect similar plugin names/slugs under the same author.
• This can lead to accidental flooding of the review queue.

Suggested Improvements

• Add a pre-submission validation to detect similar plugin slugs/names for the same author.
• Introduce a submission rate limit or cap.
• Provide support for updating/re-uploading an existing submission instead of always creating a new one.

Notes

I have already requested removal of the duplicate submissions mentioned above.

[obenland]

This was fixed in [14769]. Sorry, I missed adding the reference in the commit, still getting back up to speed with svn committing.