{
  "context": "Evaluates how the solution configures and runs grunt-env to apply environment variables from Grunt config targets for development and production task flows, including runtime function values and target isolation.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Plugin loaded",
      "description": "grunt-env is registered with Grunt (e.g., via grunt.loadNpmTasks('grunt-env') or load-grunt-tasks) so the env multi-task is available for use in task chains.",
      "max_score": 20
    },
    {
      "name": "Target config vars",
      "description": "The env task configuration declares dev and prod targets whose key/value pairs map directly into process.env when invoked, using the env multi-task rather than manual mutation.",
      "max_score": 25
    },
    {
      "name": "Function values",
      "description": "Target entries use function values executed by grunt-env at runtime to derive PORT defaults and RELEASE strings, confirming dynamic value support inside env targets.",
      "max_score": 20
    },
    {
      "name": "Task chaining",
      "description": "Dev and prod task aliases invoke their respective env targets before subsequent tasks, ensuring env:dev and env:prod run in the correct order within the Grunt task sequences.",
      "max_score": 15
    },
    {
      "name": "Target isolation",
      "description": "Running env:dev followed by env:prod leaves process.env reflecting only prod-specified values (e.g., APP_DEBUG overridden, dev defaults replaced), showing reliance on env target overrides instead of ad-hoc cleanup.",
      "max_score": 20
    }
  ]
}