{
  "context": "Evaluates whether the solution uses temporal-polyfill's Temporal-aware Intl.DateTimeFormat wrapper to render locale- and timeZone-aware strings for single values and ranges as defined in the spec. Scoring focuses solely on calling the package's formatting APIs with Temporal inputs rather than manual string manipulation.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Package Intl",
      "description": "Imports Intl from temporal-polyfill (or relies on temporal-polyfill/global) so DateTimeFormat comes from the package rather than the built-in Intl.",
      "max_score": 20
    },
    {
      "name": "Temporal inputs",
      "description": "Passes Temporal objects (e.g., Instant or PlainDateTime from temporal-polyfill) directly to DateTimeFormat without converting them to strings or legacy Date before formatting.",
      "max_score": 20
    },
    {
      "name": "Single format",
      "description": "Calls the package's DateTimeFormat.prototype.format (or formatToParts) with the provided locale/options to produce single-value output instead of assembling the string manually.",
      "max_score": 20
    },
    {
      "name": "Range formatting",
      "description": "Uses DateTimeFormat.prototype.formatRange for start/end Temporal values so shared segments collapse automatically, avoiding concatenating two format calls or custom joins.",
      "max_score": 20
    },
    {
      "name": "Range parts",
      "description": "Builds the parts output via the package's DateTimeFormat.prototype.formatRangeToParts to populate startRange/endRange/shared entries rather than constructing the array by hand.",
      "max_score": 20
    }
  ]
}