{
  "context": "Evaluates whether the solution builds a config plugin that leverages @expo/config-plugins build property helpers to map project settings into gradle.properties and Podfile properties. Scoring focuses entirely on correct, idiomatic use of the factory utilities for writing and cleaning build properties on both platforms.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Gradle factory",
      "description": "Plugin is constructed with createBuildGradlePropsConfigPlugin (not manual file edits) to target gradle.properties for Android build properties.",
      "max_score": 30
    },
    {
      "name": "Hermes mapping",
      "description": "Factory maps android.hermesEnabled to the gradle property expo.jsEngine, writing hermes when true and jsc when false through the helper's property mapping.",
      "max_score": 15
    },
    {
      "name": "Kotlin property",
      "description": "Factory mapping includes android.kotlinVersion and writes expo.kotlinVersion to gradle.properties via createBuildGradlePropsConfigPlugin.",
      "max_score": 15
    },
    {
      "name": "Podfile factory",
      "description": "Uses createBuildPodfilePropsConfigPlugin to target Podfile properties, mapping ios.useFrameworks to use_frameworks and ios.flipperEnabled to flipper_configuration values (dynamic/static and flipper/disabled) instead of manual JSON manipulation.",
      "max_score": 25
    },
    {
      "name": "Cleanup logic",
      "description": "Employs the removal/empty-handling options provided by the build property factories so missing inputs delete expo.jsEngine, expo.kotlinVersion, use_frameworks, and flipper_configuration entries rather than leaving stale values.",
      "max_score": 15
    }
  ]
}