{
  "context": "Evaluates whether the solution uses Syrupy per-assert configuration to snapshot dynamic telemetry summaries and binary thumbnails. Focuses on matcher selection, path filtering, and extension choices described in the spec.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Matcher usage",
      "description": "Snapshot assertions for summary metadata set matcher=path_type(...) or compose_matchers so generated_at, nonce, and debug.captured_at are type/pattern matched while the remaining fields are strict.",
      "max_score": 30
    },
    {
      "name": "Path filters",
      "description": "Assertions apply include/exclude controls (paths, paths_include, or props) on snapshot(...) to focus on expected sections (e.g., debug block when include_internal is true) instead of mutating the subject data.",
      "max_score": 25
    },
    {
      "name": "Extension choice",
      "description": "Binary thumbnail checks call snapshot with extension_class or use_extension to write via a non-text extension (e.g., SyrupyPNGImageSnapshotExtension or raw) rather than the default amber output.",
      "max_score": 20
    },
    {
      "name": "Scoped config",
      "description": "Matcher, filter, and extension options are applied per assertion (on each snapshot(...) call) instead of relying solely on global defaults or session-level hooks.",
      "max_score": 15
    },
    {
      "name": "Coverage asserts",
      "description": "Snapshot tests cover both include_internal true/false cases for prepare_summary and the thumbnail path, using separate snapshot calls to capture each scenario.",
      "max_score": 10
    }
  ]
}