{
  "context": "Evaluates how well the solution leans on @expo/config-plugins helper utilities to load, validate, warn on, and persist Android manifest adjustments tied to the XML helper capability. Checks emphasize use of built-in XML readers/writers plus the warning tools instead of custom parsing or logging.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "XML read",
      "description": "Uses `XML.readXMLAsync` with the provided manifest path and `fallbackXml` to load the manifest instead of manual file or XML parsing.",
      "max_score": 20
    },
    {
      "name": "XML write",
      "description": "Persists the updated manifest via `XML.writeXMLAsync`, delegating formatting to the helper rather than constructing XML output manually.",
      "max_score": 15
    },
    {
      "name": "Min SDK warning",
      "description": "Records the minSdk bump with `WarningAggregator.addWarningAndroid` (or equivalent Android-scoped helper) instead of console logging when `minSdkVersion` is raised.",
      "max_score": 20
    },
    {
      "name": "Metadata warning",
      "description": "Uses `WarningAggregator.addWarningAndroid` to note adding or correcting the `com.example.feature.ENABLED` meta-data value rather than applying the change silently.",
      "max_score": 15
    },
    {
      "name": "Flush warnings",
      "description": "Calls `WarningAggregator.flushWarningsAsync` after manifest writes so aggregated warnings surface before returning.",
      "max_score": 15
    },
    {
      "name": "Clear error",
      "description": "Surfaces the missing-manifest-without-fallback case using package facilities such as `PluginError` instead of a generic error.",
      "max_score": 15
    }
  ]
}