You'll notice
Permission rules on symlinked paths now also apply to the real, resolved path they point to
What
When a permission rule is written against a file path that turns out to be a symlink, Claude Code now also resolves that path to its real, canonical location on disk, and adds an equivalent rule for that resolved "physical twin" path. This applies to deny rules during permission-rule compilation.
Why
Without this, a deny rule written against a symlinked path could be bypassed simply by accessing the same file through its real, resolved path instead of the symlink. Now both paths are covered by the same rule.