{
  "context": "Evaluates how well the solution leverages Plotly.js schema and validation APIs to drive the schema helper. Summaries should come from schema metadata, array-aware paths from schema utilities, and figure issues from the built-in validator outputs; general coding style is out of scope.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Schema fetch",
      "description": "Uses PlotSchema.get() (or equivalent Plotly schema accessors) to retrieve trace attribute definitions instead of duplicating or hardcoding metadata.",
      "max_score": 25
    },
    {
      "name": "Summary fields",
      "description": "Pulls valType, description/text, and arrayOk/array acceptance directly from the schema when building ordered attribute summaries for requested paths.",
      "max_score": 20
    },
    {
      "name": "Array discovery",
      "description": "Derives array-accepting paths via PlotSchema.findArrayAttributes or schema-driven arrayOk flags (not manual lists), ensuring scatter outputs include entries like x, y, and marker.color from the schema.",
      "max_score": 20
    },
    {
      "name": "Validator call",
      "description": "Invokes Plotly.validate on the composed figure (data/layout/config) to surface issues rather than implementing custom type/unknown checks.",
      "max_score": 25
    },
    {
      "name": "Validator mapping",
      "description": "Maps Plotly.validate results into the requested {path,message}-style issues using the library-provided path/schemaPath/message details, capturing both unknown attributes and wrong types (e.g., string width or invalid marker size).",
      "max_score": 10
    }
  ]
}