{
  "context": "Evaluates how the solution uses @expo/config-plugins to read and write the Android manifest while enforcing location and notification requirements. Focuses on applying manifest, permission, metadata, and service helpers rather than manual XML edits.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Manifest IO",
      "description": "Loads and saves AndroidManifest.xml through @expo/config-plugins APIs such as AndroidConfig.Manifest.readAndroidManifestAsync and writeAndroidManifestAsync instead of manual file parsing.",
      "max_score": 20
    },
    {
      "name": "Permission helpers",
      "description": "Adds ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, and POST_NOTIFICATIONS using AndroidConfig.Permissions.ensurePermissions or ensurePermission to avoid duplicates.",
      "max_score": 25
    },
    {
      "name": "Background gate",
      "description": "Conditionally inserts ACCESS_BACKGROUND_LOCATION only when requested, still leveraging AndroidConfig.Permissions helpers for the addition.",
      "max_score": 10
    },
    {
      "name": "Service insertion",
      "description": "Retrieves the main application with AndroidConfig.Manifest.getMainApplicationOrThrow (or equivalent) and appends the foreground service entry with exported:false and the supplied intent-filter action.",
      "max_score": 15
    },
    {
      "name": "Metadata helper",
      "description": "Uses AndroidConfig.Manifest.addMetaDataItemToMainApplication (or equivalent) to set com.example.maps.API_KEY and overwrite existing values as needed.",
      "max_score": 15
    },
    {
      "name": "Idempotent writes",
      "description": "Relies on config-plugins utilities (e.g., ensurePermissions plus manifest write) to keep permissions, service, and metadata single-instanced across repeated runs without manual deduplication.",
      "max_score": 15
    }
  ]
}