docs(permissions): align release guidance with P7 policy - #385
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.
After the P7 cutover, remote MCP and bot agent instructions still promised read-only defaults, safety recipes used retired setters, and deletion guidance ignored explicit permission overrides. Describe the actual defaults, resource restrictions, most-specific overrides and confirmation behavior across user docs and the bundled skill. No runtime, version or release changes.
Validation: fresh main parity/coverage and release checks passed except the expected already-published version gate. Documentation corrections passed lint, types, 1361 tests (2 existing skips), docs and parity. Changelog drafts and publication are handed to the releasing agent separately.