Migrate AssetFare registry namespace after GitHub organization transfer

[odaiin]

Summary

AssetFare moved its public repository from the personal GitHub namespace to the official assetfare organization. The Official MCP Registry still has the historical identities, and their remote URL reservation blocks publication under the organization namespace.

Existing Registry identities

• io.github.odaiin/assetfare
• io.github.odaiin/assetfare-bridge
• Remote: https://api.assetfare.dev/mcp
• Latest existing Registry release: 0.4.11

Canonical organization identity

• Public repository: https://github.com/assetfare/assetfare-mcp
• Requested names: io.github.assetfare/assetfare and io.github.assetfare/assetfare-bridge
• Current package/release: assetfare-mcp@0.4.12
• The old GitHub repository URLs redirect to the organization repositories.

I am the owner of both the former personal repository and the assetfare organization.

Reproduction

OIDC publication from assetfare/assetfare-mcp validates the new metadata, but Registry publication fails closed because the existing record owns the same remote URL:

remote URL https://api.assetfare.dev/mcp is already used by server io.github.odaiin/assetfare

Failing migration run: https://github.com/assetfare/assetfare-mcp/actions/runs/35873878154

Request

Please migrate the existing Registry identity/ownership to the io.github.assetfare/* names while preserving history, or release the remote-URL reservation so the organization names can be published. Until migration is available, AssetFare will keep the historical io.github.odaiin/* names as compatibility identifiers and will not create a duplicate endpoint.

[odaiin]

Additional reproduction after retaining the historical names (no duplicate namespace publication attempted):

• Source: assetfare/assetfare-mcp main at 3f2d79df16287bf694332b2f6b2c38ad3f8981f5
• Metadata: io.github.odaiin/assetfare and io.github.odaiin/assetfare-bridge, version 0.4.22, repository https://github.com/assetfare/assetfare-mcp
• mcp-publisher: pinned v1.8.1 with the release SHA-256 verified; both manifests validated successfully locally and in CI
• OIDC login: succeeded for both matrix jobs
• Publish result: both failed with HTTP 403. The Registry says the token may publish io.github.assetfare/* but not io.github.odaiin/assetfare or io.github.odaiin/assetfare-bridge.

Reproduction run: https://github.com/assetfare/assetfare-mcp/actions/runs/35965122298

This confirms that publishing a new 0.4.22 version under the existing historical identities from the transferred canonical repository is also blocked. No io.github.assetfare/* duplicate was submitted.