Repository navigation
NAP-RESOURCE: use BUD-10 Blossom URIs - #121
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dskvr
requested review from
dskvr
and
a balanced review from Copilot
and removed request for
Copilot
October 14, 2026 16:35
Copilot stopped reviewing on behalf of
dskvr due to an error
October 14, 2026 16:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the
blossom:row of the NAP-RESOURCE Schemes table:blossom:sha256:<hex>blossom:<sha256>.<ext>The runtime MUST still verify SHA-256 before delivery. The row also says BUD-10's
xs,asandszhints are advisory. They never bypass policy, size limits or the hash check.Targets
nub-resource, so it lands in #80. The changelog bullet is in its own commit.Why
blossom:sha256:<hex>is not the Blossom URI that BUD-10 defines. Downstream SDK docs are moving to BUD-10 in napplet/web#246, which depends on this revision.Open question (not decided here)
Should runtimes keep accepting legacy
blossom:sha256:<hex>references while content migrates? That would be a new normative rule, so this PR leaves it out.🤖 Generated with Claude Code