{
  "context": "Evaluates how well the solution leverages @tailwindcss/node's path normalization utilities to produce consistent absolute paths. Checks focus on proper use of the library API rather than custom string handling. Scoring prioritizes correct application of normalizePath to all inputs, including UNC paths.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Library import",
      "description": "normalizePath is imported directly from @tailwindcss/node rather than reimplemented or pulled from another source.",
      "max_score": 10
    },
    {
      "name": "normalize usage",
      "description": "Every path is passed through normalizePath after resolution so outputs match the library's forward-slash canonical form instead of custom replacements.",
      "max_score": 45
    },
    {
      "name": "UNC handling",
      "description": "normalizePath is used on UNC inputs to preserve the leading double-slash share prefix (e.g., //Server/Share) without collapsing or altering it.",
      "max_score": 20
    },
    {
      "name": "Canonical output",
      "description": "Final returned paths match normalizePath output (no backslashes or un-normalized segments) for all tested cases, including Windows drive letters.",
      "max_score": 15
    },
    {
      "name": "No custom normalizer",
      "description": "No alternative normalization logic (regex replacements, manual separator swaps, other libraries) is used in place of normalizePath for cross-platform normalization.",
      "max_score": 10
    }
  ]
}