{
  "context": "This checklist evaluates how well the solution uses Parcel's feature flag override capability when running builds or the dev server. It checks that feature flag arguments are forwarded via the CLI `--feature-flag` option or the `featureFlags` option in @parcel/core, and that runs remain correct with and without overrides.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Flag forwarding",
      "description": "Each provided override becomes a Parcel feature flag argument (e.g., `--feature-flag name=value` on the CLI or the `featureFlags` option in @parcel/core) when invoking the bundler.",
      "max_score": 35
    },
    {
      "name": "Pre-run validation",
      "description": "Empty flag names or missing values are rejected before starting Parcel, and no bundler process is spawned when validation fails.",
      "max_score": 20
    },
    {
      "name": "Dry-run command",
      "description": "Dry-run mode returns the exact Parcel command string including feature flag arguments and avoids executing Parcel or creating bundles.",
      "max_score": 15
    },
    {
      "name": "Mode and outputs",
      "description": "Build or serve runs are issued through Parcel (e.g., `parcel build`/`serve` or `Parcel.run`/`Parcel.watch`) using the provided entries and mapping the output directory via Parcel's output option (such as `--dist-dir` or `defaultTargetOptions.distDir`).",
      "max_score": 20
    },
    {
      "name": "No-flag run",
      "description": "When no flags are given, Parcel runs without `--feature-flag` arguments yet still produces bundles and reports the resulting output directory.",
      "max_score": 10
    }
  ]
}