Permission wildcard matching fails for paths with escaped quotes/backslashes

When a Bash permission rule contains a Windows path with escaped quotes and backslashes, parallel tool calls still prompt for approval even though the pattern should match.

Settings rule:

"Bash(\"C:\\\\Program Files\\\\draw.io\\\\draw.io\" --export *)"

Commands that should match but prompted anyway:

"C:\Program Files\draw.io\draw.io" --export --format png --scale 2 --output docs/diagrams/diagram-a.png docs/diagrams/diagram-a.drawio
"C:\Program Files\draw.io\draw.io" --export --format png --scale 2 --output docs/diagrams/diagram-b.png docs/diagrams/diagram-b.drawio

Both commands were sent as parallel tool calls. Each one prompted for permission despite the wildcard rule in settings.json.

Expected: Both commands auto-allowed by the existing rule.
Actual: User was prompted to approve each command individually.

Platform: Windows 11, bash shell