{
  "context": "Evaluates how the solution configures grunt-env to load presets with literal and function-based environment values. Checks focus on defining env targets, executing function entries at runtime, and chaining presets to reuse values.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Plugin wired",
      "description": "grunt-env is loaded into Grunt (e.g., via `grunt.loadNpmTasks('grunt-env')`) so the env multi-task is available before tasks run.",
      "max_score": 10
    },
    {
      "name": "Static preset",
      "description": "An env target (e.g., `env:static`) defines `APP_MODE` as a literal string in `grunt.initConfig`, and running that target writes the same value to `process.env.APP_MODE`.",
      "max_score": 20
    },
    {
      "name": "Function entry",
      "description": "The dynamic env target sets `RUN_ID` using a function-valued entry (supported by grunt-env) that returns a string at runtime rather than a precomputed literal.",
      "max_score": 30
    },
    {
      "name": "Re-evaluates per run",
      "description": "Invoking the dynamic env target twice shows the `RUN_ID` function executes on each run (e.g., two calls yield different values without restarting the process).",
      "max_score": 20
    },
    {
      "name": "Combines prior env",
      "description": "The dynamic target includes a function-valued `COMBINED_FLAG` that reads `process.env.APP_MODE` set by the static env target and writes a combined string after the default task chains the two targets.",
      "max_score": 20
    }
  ]
}