[refactor][#488] Fix permission evaluation ordering with clear rule priority #489
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
Fixed the permission evaluation order to ensure global rules take priority over workflow-specific permissions, with clear fall-through behavior and unified Telegram escalation. The previous implementation allowed workflow auto-allow to bypass global deny rules, which was a security concern.
Changes
.claude-plugin/lib/permission/determine.py:435-491to reorder evaluation flow:docs/feat/permissions/rules.mdwith explicit evaluation order diagram and stage documentationdocs/feat/permissions/telegram.mdto clarify Telegram as the final escalation pointdocs/feat/core/handsoff.mdto correct hook location and permission module pathstests/cli/test-hook-permission-matching.sh:317-433with 4 new ordering tests:tests/fixtures/test-pre-tool-use-input.jsonwith ordering test fixturesTesting
Related Issue
Closes #488