{
  "context": "Evaluates whether the solution uses the npm CLI to install packages for a workspace or the global environment and reports those actions accurately. Focus is on correct npm commands for production, development, and global targets plus a non-mutating dry-run path. Outputs should come directly from npm behaviors rather than manual manifest edits.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Local install",
      "description": "Runs npm install in the specified workspace for regular packages (e.g., npm install name@version) and relies on npm to populate dependencies and node_modules instead of editing files manually.",
      "max_score": 25
    },
    {
      "name": "Dev deps",
      "description": "Uses npm install --save-dev/-D (scoped to the workspace) for packages marked as dev so they land under devDependencies without touching production entries.",
      "max_score": 20
    },
    {
      "name": "Global install",
      "description": "Installs requested packages with npm install --global/-g and ensures no workspace manifest changes occur while marking installed items as global in the returned summary.",
      "max_score": 20
    },
    {
      "name": "Dry run commands",
      "description": "Implements dry-run by emitting the npm commands that would be executed (including local/global and dev flags) and either invoking npm with --dry-run or skipping execution entirely while still producing the command list.",
      "max_score": 20
    },
    {
      "name": "Action summary",
      "description": "Builds the returned actions list directly from the npm commands used or planned (including package names, versions, and flags for dev/global) so dry-run output matches real execution steps.",
      "max_score": 15
    }
  ]
}