fix: correct stale hook script paths in policy.yaml#2
Merged
Conversation
The hooks: block referenced hooks/pre_exec_guard.py and hooks/post_exec_receipt.py; actual modules are hooks/guard.py, hooks/receipts.py, and hooks/governor.py. Declarative only -- runtime wiring lives in .claude/settings.json via entry.py, so no behavior change. Narrowed from the v0.1.1 auto-mode-hardening patch after the guard surfaced additional scope/policy mismatches during implementation (writable_paths gap for repo-root CHANGELOG.md, restricted-pattern coverage of **/*.schema.json, governor-CLI classification as SHELL_DANGEROUS, pytest env missing PyYAML). All tracked for v0.1.2.
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
2 participants
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 hooks: block referenced hooks/pre_exec_guard.py and hooks/post_exec_receipt.py; actual modules are hooks/guard.py, hooks/receipts.py, and hooks/governor.py. Declarative only -- runtime wiring lives in .claude/settings.json via entry.py, so no behavior change.
Narrowed from the v0.1.1 auto-mode-hardening patch after the guard surfaced additional scope/policy mismatches during implementation (writable_paths gap for repo-root CHANGELOG.md, restricted-pattern coverage of **/*.schema.json, governor-CLI classification as SHELL_DANGEROUS, pytest env missing PyYAML). All tracked for v0.1.2.
Independent of PR #1 (v0.1.2): that PR edits different sections of policy.yaml (writable_paths, schema path, test_runner) and does not touch the hooks: block. Either merge order works; no conflict expected.