[BUG] Settings parser incorrectly validates glob syntax inside SQL command strings

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

---
Title: Settings parser incorrectly validates glob syntax inside SQL command strings

Description:

Settings that worked in previous versions now fail validation. The parser is treating * characters inside SQL queries as glob patterns, even when they're
clearly part of a literal command string.

Example of broken config:
"Bash(PGPASSWORD=xxx psql -h host -U user -d db -c \"SELECT COUNT(*) FROM table\")"

Error message:
Use ":" for prefix matching, not just "". Change to ... "SELECT COUNT(:*) FROM ..."

Expected behavior: The parser should treat the entire command as a literal string, not scan for * characters inside quoted SQL.

Version: 2.0.72 (npm-global)

What Should Happen?

My settings are not invalid..

Error Messages/Logs

Invalid Settings in settings.local.json

Steps to Reproduce

Use glob in SQL

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.72

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_