{
  "_meta": {
    "comment": "Scenario 05: SET invalid JSON in settings file. Covers the settings category AND the brief criterion 'one finding whose v5.0.0 description contains a tier1 forbidden word' — both the v5.0.0 title and description carry tier1 'invalid'. Humanizer rewrites to plain language."
  },
  "findingId": "CA-SET-001",
  "scannerInput": {
    "id": "CA-SET-001",
    "scanner": "SET",
    "severity": "critical",
    "title": "Invalid JSON in settings file",
    "description": ".claude/settings.json contains invalid JSON and will be ignored by Claude Code.",
    "file": ".claude/settings.json",
    "line": null,
    "evidence": "Unexpected token } in JSON at position 187",
    "recommendation": "Fix JSON syntax errors. Use a JSON validator.",
    "category": null,
    "autoFixable": false
  },
  "expectedHumanized": {
    "titlePattern": "settings file isn'?t readable as JSON",
    "descriptionPattern": "Claude Code can'?t parse the file|settings are skipped",
    "recommendationPattern": "Open the file and fix the JSON syntax"
  },
  "groundTruth": {
    "what": "Your settings file can't be read as JSON, so none of the settings inside take effect.",
    "why": "Claude Code parses the settings file once at startup. When that parse fails, all settings inside are skipped silently, and you get the defaults.",
    "whatNext": "Open the file and fix the JSON syntax shown in the details (often a missing comma, an extra trailing comma, or an unterminated quote)."
  }
}
