{
  "context": "Evaluates whether the solution wires npm's CI-focused workflow correctly: lockfile-only installs with npm ci and test execution via npm scripts. Emphasizes deterministic installs and surfacing npm failures for CI.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses npm ci",
      "description": "Invokes `npm ci` (or `npm install --ci`) in the target project to perform a clean, lockfile-only install that removes any existing node_modules instead of falling back to plain `npm install`.",
      "max_score": 35
    },
    {
      "name": "Lockfile required",
      "description": "Checks for `package-lock.json` and fails fast with a clear message when it is missing or out of sync, relying on npm ci's lockfile validation rather than bypassing it.",
      "max_score": 20
    },
    {
      "name": "Lockfile untouched",
      "description": "Keeps the existing lockfile intact by avoiding commands that rewrite it (e.g., plain `npm install`, `--package-lock=false`), demonstrating reliance on the pinned dependency graph.",
      "max_score": 15
    },
    {
      "name": "Tests via npm",
      "description": "Runs the project's tests through npm's runner (`npm test` / `npm run test`) after install so npm-provided environment and lifecycle hooks are used instead of calling test binaries directly.",
      "max_score": 20
    },
    {
      "name": "Exit propagation",
      "description": "Propagates the non-zero exit statuses from `npm ci` and `npm test` back to callers, rather than masking or overriding npm's failures.",
      "max_score": 10
    }
  ]
}