fix(dwn): reject record-limited roles#1480
Merged
Merged
Conversation
|
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
1 participant
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.
Summary
$roleand$recordLimiton the same protocol path with a typed configuration errorNo shipped protocol definition combines these directives. This takes #1444's explicit greenfield alternative: bounded role membership needs a purpose-built policy rather than allowing hidden records to remain capabilities.
Closes #1444.
Test plan
bun test tests/interfaces/protocols-configure.spec.tsbun run lintbunx turbo run build --filter=@enbox/dwn-sdk-js...bunx turbo run build --filter=@enbox/agent...Migration
Affected definitions must move to a corrected protocol under a new URI, migrating only intended role assignments. Existing definitions and records are not rewritten.