What
Settings files that fail to parse or validate are now reported with structured error information instead of being silently skipped.
Details
- New structured error fields:
path(dot-notation to field),message(human-readable),severity(set to"warning") - Settings errors section: "Settings parse and validation errors. When non-empty, the listed files were skipped during the merge above — their settings are not reflected in
effectiveorsources." - Error types include invalid JSON, JSON comments, and schema mismatches
- File path of the failing settings file is included in error output
Evidence
Settings validation (search for "Settings parse and validation errors", "severity")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.