fix(cli): show context permissions and preserve server errors - #20
Merged
Merged
Conversation
realmroot
Bot
changed the title
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.
The ordinary Context list now shows each Context’s stable ID, identity type, Agent-granted scopes, requestable scopes, and published scopes not currently requestable. The complete list appears in one call, without extra flags or a separate precheck command. External permissions reflect the current account authorization and can change after connection or expansion.
Access requests continue directly to the server. With
--json, failures preserve the server error body, including its code, message, request ID, and details; the exit status remains nonzero. No client permission gate, new error codes, automatic Context switching, or matching-status enums are added.Validation:
go test ./...passed, including ordinary list output and HTTP error transport. Also called the local CLI against the live Realmroot Context directory and verified the ordinary list exposes permission names for all three Contexts. The new backend rejection has not been deployed.Companion server PR: realmroot/realmroot#244
🤖 Created by Jarvis via Realmroot