#3689 Docs: extension publishing reference quotes stale bare-specifiers and quality messages

The swamp-club manual's extension reference quotes swamp CLI output that has changed twice since it was written:

• content/manual/reference/extensions/publishing.md (around lines 127-217) and content/manual/reference/extensions/manifest.md (around line 926) say an extension with bare specifiers would publish unscored. Since swamp-club#3370 the registry publishes a scorecard with the documentation factors at 0, and since swamp-club#3669 the CLI says so: the bare-specifiers message reads 'Extension has bare imports that ship as written, which the registry's scorer cannot resolve, so it would score the documentation factors 0: "zod". Push rewrites a bare import only when the deno.json import map resolves it to an npm:, jsr:, node: or URL specifier; add such an entry for each, or write the specifier in its place.'
• The sample quality output (bare-specifiers line, the 'The registry cannot score this extension' error line, and the 'Extension quality failed: the registry cannot score this extension' line) predates swamp-club#3637 and swamp-club#3669. Current lines: 'The registry cannot resolve this extension's bare imports: they ship as written, so it would score the documentation factors 0. Push rewrites only the bare imports the deno.json import map resolves.' and 'Extension quality failed: the registry cannot resolve its bare imports, which ship as written, so it would score the documentation factors 0.'
• The quality --json field table should add docAnalysisError: why deno doc could not analyse the source (null when it ran); quality scores the documentation factors 0, as the registry does, and fails. The status row should list a deno doc failure as a failing reason.

Source of truth: swamp's .claude/skills/swamp/references/extension-publish/references/publishing.md, updated in swamp PR 3241.