[hzrd149]

What

Replaces every blossom:sha256:<hex> reference in the repo with the BUD-10 Blossom URI form, blossom:<sha256>.<ext>. The extension is .bin when unknown, and BUD-10 discovery hints (xs, as, sz) are optional.

• Scheme lists in the @napplet/sdk, @napplet/shim and @napplet/nap READMEs, apps/docs, specs/SHELL-RESOURCE-POLICY.md and the napplet-sdk skill now link BUD-10.
• Resource JSDoc in @napplet/core, @napplet/sdk and @napplet/nap/resource gains a BUD-10 @see tag and uses BUD-10 examples.
• Test fixtures and archived v0.28.0 planning notes use the new form.

Why

blossom:sha256:<hex> is not the Blossom URI defined by BUD-10, so new content should not teach it.

⚠️ Surfaced decision: upstream NAP-RESOURCE conflict

The canonical NAP-RESOURCE text (napplet/naps#80, head 2529209, Schemes table) still says: "Canonical form blossom:sha256:<hex>". Until that NAP is revised to reference BUD-10, these docs disagree with the living spec. The NAP-RESOURCE revision should land first, or alongside this PR.

Verification

• pnpm type-check: green
• pnpm -r test:unit: green (core 35, nap 188, vite-plugin 54, conformance 101, shim 17, apps/conformance 9, conformance-cli 22)
• pnpm build: green for every package except @napplet/docs. Its vitepress build fails identically on unmodified main because of a local vue symlink environment issue, unrelated to this change.

Out of scope

• No changeset. Only docs, JSDoc comments and tests changed, with no runtime behavior change.
• No parser changes were needed, since the resource API passes the URL string through unchanged. Host-side BUD-10 parsing and legacy-read compatibility belong to shell implementations.

🤖 Generated with Claude Code

[dskvr]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved the conflict with main and pushed merge commit c9b123d. The merge includes current main and keeps the PR-specific status in .planning/STATE.md.

[dskvr]

Reviewed c9b123d0: 33 targeted tests passed, all four CI checks were green, and the changed implementation files have no runtime code changes. One introduced planning-state regression is flagged inline.

• The upstream-conflict warning in this PR description and .planning/quick/261014-fuc-replace-blossom-sha256-uris-with-bud-10-/261014-fuc-SUMMARY.md is stale. The current NAP-RESOURCE Schemes section already specifies BUD-10 blossom:<sha256>.<ext>. Update both to remove the obsolete blocker.
• Separate follow-up, pre-existing and outside this diff: resource-transport.ts resolves wire blob values directly and sends requests for resource.bytesMany. The current NAP-RESOURCE wire protocol specifies urls and canonical padded base64 bytes decoded into Blob by the web binding. Correct the transport and its fixtures in a separate change.