Request: delete io.github.siddmax/namera (all versions) - orphaned after GitHub rename siddmax -> solozerolabs

Summary

I'm the publisher of io.github.siddmax/namera. That GitHub account was renamed from siddmax to solozerolabs, so the siddmax login no longer exists and the namespace is orphaned. I've already republished under the correct namespace as io.github.solozerolabs/namera (v0.1.15), but the two old entries are still listed as active — and one is still flagged isLatest. Same pattern as #1191 and #1508.

Request

Please set io.github.siddmax/namera, all versions, to status deleted.

The entries

The first two should go; the third is the current, correctly-namespaced server.

Evidence of the rename

The old login is gone, and the renamed account carries the same user id:

$ gh api users/siddmax
404 Not Found

$ gh api users/solozerolabs
solozerolabs  id=8741659  type=User

$ gh api user            # authenticated as myself
solozerolabs  id=8741659  type=User

Why self-service doesn't work

Logged in as the same human via mcp-publisher login github:

$ ./mcp-publisher status --status deprecated --all-versions \
    --message "Moved to io.github.solozerolabs/namera" io.github.siddmax/namera
This will update 2 version(s) of io.github.siddmax/namera:
  0.1.11: active → deprecated
  1.0.0: active → deprecated
Error: server returned status 403:
{"title":"Forbidden","status":403,"detail":"You do not have publish or edit permissions for this server"}

The registry keys namespace authority on the GitHub login string, and siddmax is no longer a login that exists, so no account can prove ownership of io.github.siddmax — including the account that originally published it.

CI hits the same wall from the other direction: publishing via login github-oidc after the rename returned 403 Forbidden, with claims showing repository_owner: solozerolabs.

Why this is worth prioritising

siddmax is a freed GitHub username. If someone registers it, they can authenticate for io.github.siddmax and publish a new version under a server name that existing users may still have in their MCP config — pointing at a package those clients would install and run. An orphaned namespace after a rename isn't only untidy; it's a name I can no longer control that still resolves for downstream users.

Ownership verification

Happy to prove it however is easiest. I hold the renamed account solozerolabs (id 8741659, the same id that published the original entries), I control the source repo at https://github.com/solozerolabs/Namera, and I can push a commit, add a file at a path you specify, or publish a marker version on request.

Thanks for maintaining the registry.

Review comparable cases #1191 and #1508, then inspect the registry handling behind the shown mcp-publisher status command and GitHub authentication flow. Verify the ownership evidence and confirm that both io.github.siddmax/namera versions are deleted while io.github.solozerolabs/namera remains active; done means the orphaned entries no longer appear as active or latest.