{
  "context": "Evaluates whether the solution leverages npm's built-in dependency update flow to move packages to the newest versions allowed by existing semver ranges. Focus is on correct use of npm CLI commands for full, targeted, and workspace-scoped updates plus accurate reporting of version changes.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Update command",
      "description": "Invokes `npm update` to perform semver-respecting upgrades instead of manually editing manifests, ensuring the package-lock is rewritten by npm.",
      "max_score": 30
    },
    {
      "name": "Package targeting",
      "description": "When specific packages are provided, calls `npm update <pkg…>` to limit upgrades to those modules while leaving others untouched.",
      "max_score": 20
    },
    {
      "name": "Workspace scope",
      "description": "Uses npm's workspace scoping flags (e.g., `npm update --workspace <name>`) to confine updates to the requested workspace without mutating siblings.",
      "max_score": 20
    },
    {
      "name": "Lockfile refresh",
      "description": "Relies on npm's update process to regenerate `package-lock.json` (or workspace lockfile) so recorded versions match installed updates.",
      "max_score": 15
    },
    {
      "name": "Version reporting",
      "description": "Derives before/after versions via npm tooling (`npm outdated`, `npm ls`, or lockfile reads after running `npm update`) to populate update summaries accurately.",
      "max_score": 15
    }
  ]
}