{
  "context": "Evaluates how the solution applies @expo/config-plugins to set Android identity, labels, resources, and Gradle defaults from the spec. Checks for reliance on the library's manifest, strings, and build.gradle helpers instead of ad-hoc edits.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Manifest package set",
      "description": "Uses `withAndroidManifest` plus `AndroidConfig.Package.setPackageInAndroidManifest` (or equivalent helper in that module) to write the provided applicationId onto the manifest package while keeping the main application entry intact.",
      "max_score": 25
    },
    {
      "name": "Gradle applicationId",
      "description": "Runs `withAppBuildGradle` to sync `defaultConfig.applicationId` with the requested id, using config-plugins utilities from `AndroidConfig.Package` instead of manual string replacement so manifest and Gradle stay aligned.",
      "max_score": 20
    },
    {
      "name": "Label via resources",
      "description": "Sets the display name through strings helpers such as `withStringsXml`/`AndroidConfig.Strings.setStringItem` and points `android:label` at `@string/app_name` in the manifest using `AndroidConfig.Manifest.getMainApplicationOrThrow`.",
      "max_score": 20
    },
    {
      "name": "Version setters",
      "description": "Applies `AndroidConfig.Version.setVersionCode` and `AndroidConfig.Version.setVersionName` inside the Gradle mod (not manual file edits) so versionCode/versionName reflect the options in app/build.gradle.",
      "max_score": 15
    },
    {
      "name": "Extra strings merge",
      "description": "Adds optional extra string resources through `AndroidConfig.Strings.setStringItem` (or similar merge helper) to avoid overwriting unrelated keys in strings.xml while inserting every provided pair.",
      "max_score": 20
    }
  ]
}