{
  "context": "This criteria evaluates how effectively the engineer uses @mdx-js/mdx package capabilities to track and extract source position information during MDX compilation. The focus is on utilizing the unified processor ecosystem and AST traversal to access position data.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses createProcessor",
      "description": "Creates a unified processor using createProcessor() from @mdx-js/mdx to parse MDX source into an AST that preserves position information",
      "max_score": 20
    },
    {
      "name": "AST traversal",
      "description": "Uses unist-util-visit or similar unified ecosystem utilities to traverse the AST and access nodes with their position data",
      "max_score": 25
    },
    {
      "name": "Position data access",
      "description": "Correctly accesses position properties on AST nodes (node.position.start, node.position.end) including line, column, and offset values",
      "max_score": 25
    },
    {
      "name": "Node type filtering",
      "description": "Properly filters nodes by type using the nodeTypes configuration to extract only the requested node types from the AST",
      "max_score": 15
    },
    {
      "name": "VFile handling",
      "description": "Processes input through the unified processor pipeline appropriately, handling VFile objects that contain the parsed AST with position information",
      "max_score": 15
    }
  ]
}