[netomi]

The "Namespace not verified" notice on the admin extension page and on a publisher's own extension settings stayed after the namespace gained an owner and the extension was activated. One example is jay-boo/gitland: the public API reports both it and its namespace as verified: true.

Cause

namespaceOwnershipConflict was taken only from the threat the NamespaceOwnershipCheckScanner recorded on the latest version's scan. Nothing clears that record, neither adding an owner nor activating the extension, so the flag stayed true for good. The namespace page uses repositories.isVerified(namespace) and correctly showed the namespace as verified.

Fix

Report the conflict only while the namespace is still unverified (!repositories.isVerified(namespace)). This applies in AdminAPI (GET /admin/extension/{namespace}/{extension}) and in UserAPI (GET /user/extensions and GET /user/extension/{namespace}/{extension}). The scan threat stays recorded as history.

Testing

• New regression tests in AdminAPITest and UserAPITest: a recorded ownership threat on a namespace that has an owner reports no conflict. Both fail without the fix.
• The existing tests for an unresolved conflict still pass.
• ./gradlew test (full suite) and spotlessCheck pass.

🤖 Generated with Claude Code