{
  "context": "This criteria evaluates how well the engineer uses Snowpack's error handling APIs and infrastructure to build custom error management utilities. The focus is on proper integration with Snowpack's error types, server APIs, and error handling patterns.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Error Logging Implementation",
      "description": "Uses proper error inspection to extract error.name, error.message, error.stack, and creates JSON entries with timestamp, error type, message, and file path. Should write to error-log.json using file system operations.",
      "max_score": 25
    },
    {
      "name": "NotFoundError Handling",
      "description": "Specifically checks for and handles Snowpack's NotFoundError type differently from other errors. Should use instanceof or error type checking to distinguish NotFoundError.",
      "max_score": 15
    },
    {
      "name": "Stack Trace Preservation",
      "description": "Preserves the full error.stack property in logged entries, maintaining source-mapped stack traces without modification or truncation.",
      "max_score": 10
    },
    {
      "name": "HMR Server Integration",
      "description": "Correctly uses the Snowpack server instance to send HMR error notifications, utilizing the server's WebSocket or HMR communication mechanism to broadcast error details to connected clients.",
      "max_score": 20
    },
    {
      "name": "Fallback Module Creation",
      "description": "Creates a stub module object that can safely replace a failed module. Should return an object structure compatible with JavaScript module exports (e.g., empty object or object with default properties).",
      "max_score": 15
    },
    {
      "name": "Error Report Generation",
      "description": "Reads and parses error-log.json, aggregates error data by type, counts occurrences, identifies affected files, and returns a structured report object with error statistics and frequency information.",
      "max_score": 15
    }
  ]
}