#3116 Docs: extension publishing reference is stale on bare specifiers, quality output and fmt config (swamp-club#3022)

What changed

swamp-club#3022 changes three behaviours that content/manual/reference/extensions/publishing.md describes:

1. swamp extension quality no longer fails early on bare import specifiers. It prints the rubric, marks the extension as unscorable by the registry (JSON: registryScorable: false), reports the bare-specifiers finding with the import-map replacement for each name, and exits non-zero. The page currently says quality fails early with a message listing the offending specifiers (around line 58).
2. bare-specifiers is no longer acceptable: declaring it in quality.yaml or inline is an invalid-acceptance error in both quality and push. The findings table (around line 245) should say so; push still reports it as a warning in this release.
3. When a local gate fails (safety, fmt/lint, collectives, upgrade chain, dependency trust, review errors, size), quality prints the rubric beside every gate failure (JSON: gateFailures), scoring an archive that leaves out files rejected by file-level safety checks.
4. swamp extension fmt and fmt --check use the project deno.json, found the same way push finds it, so fmt and push agree.

Suggested content

Update the quality section and the review-findings table on reference/extensions/publishing.md; mention the fmt config behaviour wherever fmt is described (how-to/extensions/create-and-publish.md, tutorials/publish-an-extension.md). Land after the swamp release that ships #3022.