Bash command permission checks now report every problematic file argument, not just the first one found
When Claude Code checks whether a bash command's file arguments are covered by your allowed read paths, it used to stop and report as soon as it hit the first argument that failed the check. It now keeps checking every argument and reports the first problem found only after examining them all. It also now skips paths that already match an allowed pattern before falling back to checking whether the file actually exists on disk.
This makes the permission check more thorough and consistent, so it doesn't miss other problematic arguments in the same command just because it stopped early, while still avoiding unnecessary filesystem checks for paths already known to be allowed.