{
  "context": "Evaluates how the solution leverages syrupy's pytest snapshot fixture to validate the sensor report outputs and manage snapshot lifecycles. Emphasizes correct use of snapshot assertions, scenario separation, and the update flow when report formats change.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Snapshot assertions",
      "description": "Report outputs are compared using the syrupy `snapshot` fixture via equality (`assert result == snapshot`) instead of manual expected dictionaries.",
      "max_score": 35
    },
    {
      "name": "Scenario snapshots",
      "description": "Distinct scenarios (default, rounded, breakdown-disabled) are captured as separate snapshots using syrupy mechanisms such as auto-incremented snapshots or explicit `snapshot(name=...)` to avoid collisions.",
      "max_score": 25
    },
    {
      "name": "Snapshot files",
      "description": "Snapshots are stored through syrupy's managed files (amber/extension-backed) rather than custom serialization, letting pytest create/update snapshot artifacts automatically.",
      "max_score": 20
    },
    {
      "name": "Update flag ready",
      "description": "Tests are written to be rerun with syrupy's `--snapshot-update` (or equivalent update trigger) to refresh stored expectations without manual edits, relying on the snapshot fixture to rewrite files.",
      "max_score": 20
    }
  ]
}