{
  "context": "Evaluates how the solution uses Parcel to configure public URLs across default and target builds, ensuring asset references and outputs honor the required prefixes. Focuses solely on applying Parcel CLI/config options to bundle the provided static app with correct base paths.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Default prefix",
      "description": "Builds the entry (e.g., src/index.html) with Parcel using the default `/` public URL via `--public-url` or `publicUrl` in config.",
      "max_score": 25
    },
    {
      "name": "Custom base",
      "description": "Accepts a provided base like `https://cdn.example.com/static` and passes it to Parcel using the `--public-url` flag or `publicUrl` option so HTML/JS/CSS outputs are prefixed.",
      "max_score": 20
    },
    {
      "name": "Target override",
      "description": "Defines a named Parcel target with its own `publicUrl` (e.g., in package.json `targets.<name>.publicUrl`) and builds it via `--target <name>` or equivalent API override.",
      "max_score": 25
    },
    {
      "name": "Asset rewriting",
      "description": "Allows Parcel to process stylesheet image imports so emitted asset URLs (e.g., from CSS bundles) carry the configured public URL prefix.",
      "max_score": 15
    },
    {
      "name": "Output separation",
      "description": "Configures Parcel output directories (e.g., `distDir` per target) so default and named target builds write to distinct locations matching spec expectations.",
      "max_score": 15
    }
  ]
}