#3725 Docs: extension manual pages describe push and quality resolving only the deno.json import map

swamp-club#3612 changes extension push and quality to resolve bare imports the way Deno does: deno.json or deno.jsonc, importMap file references, scopes and workspace members, read from the deno info module graph. Quality's local scorer stops receiving the import map, matching the registry's scorer.

Stale manual text once 3612 ships:

• content/manual/reference/extensions/publishing.md, around line 128: says quality still prints the rubric, which resolves the import map locally, and that the bare-specifiers finding names each import's target from the import map. Since swamp-club#3637 push rewrites every import the config resolves, so a bare import left as written is one the config does not resolve; after 3612 the local rubric uses no import map, as the registry does. The sample output near line 206 quotes the same claim.
• content/manual/reference/extensions/manifest.md, lines 915 to 928: the bare-specifier row says a bare import requires a deno.json import map. It should say the project's Deno config (deno.json or deno.jsonc imports, an importMap file, or a scope covering the module), and that push writes the target Deno resolves for that module in the shipped source.
• Check how-to/extensions/improve-score.md line 133 and reference/extensions/scorecard-rubric.md line 85 for consistency (both say no import map at score time, which stays true).

Suggested content: one short paragraph on config discovery (deno.json, then deno.jsonc, walking up from the manifest) and resolution (as Deno resolves it, per importing module); an unresolved bare import ships as written and raises the bare-specifiers warning.

---

2026-10-22 (Seth): on hold for one dependency-trust docs update, done after #3630 (now including #3632) and #3662 ship. That update covers #3725, #3728 and those two issues.