[Bug] PowerShell tool blocks reads in working directory with non-ASCII characters (umlaut)

Bug Description
PowerShell tool: blockReadsOutsideWorkingDirectories blocks a path INSIDE the working directory (Windows, path with umlaut) Environment: - Claude Code version: 2.1.284 - OS: Windows 11 - Mode: auto mode - Setting: permissions.blockReadsOutsideWorkingDirectories = true - Working directory (session started here): C:\CLAUDE\Clickdummy Änderung Command (PowerShell tool): Get-ChildItem -Path "C:\CLAUDE\Clickdummy Änderung" -Recurse -File -Exclude *.pyc | Sort-Object LastWriteTime -Descending | Select-Object -First 12 LastWriteTime, Length, FullName | Format-Table -AutoSize -Wrap Result: "Reads outside the working directories are blocked (permissions.blockReadsOutsideWorkingDirectories). Add the directory with /add-dir, or remove that setting." Expected: The command should be allowed, since the target path is the working directory itself. Suspected cause: The PowerShell path check likely fails to match the path against the working directory due to the non-ASCII character (Ä), the space and/or backslash separators. Other tools (Read/Edit/Glob, Bash with forward-slash paths) work fine in the same directory. Possibly related: #95806, #91650

Environment Info

• Platform: win32
• Terminal: null
• Version: 2.1.284
• Feedback ID: 935d86fe-2ef2-4ffc-8738-5357eaefb62d

Errors

[]