{
  "context": "Evaluates how the solution orchestrates config plugins using @expo/config-plugins helpers, including ordered application of mixed plugin entries, run-once protection, and clear reporting of applied plugins. Scoring focuses solely on whether the package APIs are used correctly to meet the behaviors described in the spec.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "withPlugins flow",
      "description": "Uses withPlugins to apply the provided plugin array so string module entries and inline ConfigPlugin functions run in order and return the final config.",
      "max_score": 30
    },
    {
      "name": "Static resolution",
      "description": "String plugin entries are resolved relative to projectRoot through withStaticPlugin or resolveConfigPluginFunctionAsync, and missing modules surface a PluginError or equivalent message that names the entry.",
      "max_score": 20
    },
    {
      "name": "Run-once guard",
      "description": "Wraps the default plugin with createRunOncePlugin or withRunOnce keyed by options.onceKey so the guarded plugin body executes only the first time even across repeated pipeline invocations.",
      "max_score": 20
    },
    {
      "name": "ConfigPlugin typing",
      "description": "Inline plugin implementations are typed as ConfigPlugin (or exported as such) and include a stable name used for appliedPlugins reporting rather than ad-hoc shape.",
      "max_score": 15
    },
    {
      "name": "Applied history",
      "description": "Collects appliedPlugins from the names on ConfigPlugin entries or the history exposed by withPlugins/withStaticPlugin instead of manual bookkeeping that ignores package-provided identifiers.",
      "max_score": 15
    }
  ]
}