#887 Extension detail page shows deno doc module-not-found failure for published extension

The swamp.club extension detail page can show a Deno documentation generation failure for a published extension even though the extension was pushed successfully.

Example affected page: https://swamp-club.com/extensions/@evrardjp/capability-orchestrator

Observed behavior: The website displays this error on the extension page:

deno doc failed (code 1): Warning Module not found \"file:<redacted>
Warning Module not found \"file:<redacted>
error: Module not found \"file:<redacted>

Expected behavior: A successfully pushed extension should have its documentation rendered on swamp.club, or the page should show a clear actionable publishing/validation error if the extension bundle is missing something required for documentation generation.

Notes:

• The extension push completed successfully.
• The error appears to come from the website/server-side deno doc step rather than from the local push command.

Fix summary: This affects the extension registry website documentation generation path. The fix likely involves making the server-side deno doc invocation operate on the same resolved/bundled module graph accepted by extension publishing, or adding publish-time validation that rejects extensions whose generated docs would fail because of unresolved file imports.