Under the hood
Write-permission checks gain a dedicated claudeSettingsFile circuit breaker, separate from the Windows-path check.
What
The logic that classifies write permission requests now has its own claudeSettingsFile circuit breaker (a check that can halt or flag a risky action), distinct from the existing suspicious-Windows-path check. When a path both looks like a suspicious Windows path and looks like a Claude settings file, the suspicious-Windows-path result is now also tagged with also: ["claudeSettingsFile"].
Why
Writes to Claude's own settings files can now be flagged specifically as such, rather than only being caught incidentally by the Windows-path check, and a path that trips both checks is now labeled as doing so.