{
  "context": "Evaluates how the solution uses babel-plugin-react-transform to initialize file-scoped transforms and surface their options. Focus is on correctly wiring plugin config, executing generated initialization, and exposing metadata captured by the plugin.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Plugin setup",
      "description": "Babel compilation registers babel-plugin-react-transform (default export) rather than custom wrappers, ensuring the plugin drives component detection and transform wiring.",
      "max_score": 20
    },
    {
      "name": "Transform options",
      "description": "Transform configurations are passed via the plugin's `transforms` array so ReactTransformBuilder.assertValidOptions/normalizeOptions handle `transform`, `imports`, and `locals` instead of manual option shaping.",
      "max_score": 20
    },
    {
      "name": "Per-file init",
      "description": "Execution flows through the plugin's initTransformers path (or generated `_transformers` variable) so each transform module is invoked once per file with shared `_components` metadata and reused wrappers, not re-invoked per component.",
      "max_score": 25
    },
    {
      "name": "Metadata passed",
      "description": "Options objects handed to transform modules include the `filename` from Babel's `state.file.opts.filename` and the components map produced by the plugin (displayName and isInFunction values from component detection).",
      "max_score": 20
    },
    {
      "name": "Injected deps",
      "description": "Transform functions receive resolved `imports` and `locals` in the order declared (plugin-created arrays passed into the transform factory), rather than custom dependency plumbing.",
      "max_score": 15
    }
  ]
}