{
  "context": "Assesses how well the solution uses the npm CLI to publish package versions, handle dry-run previews, and roll back recent releases per the spec's release helper requirements. Emphasizes correct CLI invocation for publish, dry-run, and scoped unpublish flows.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "npm publish",
      "description": "Invokes `npm publish` from the provided package directory, targeting the specified version and registry rather than manually crafting HTTP requests.",
      "max_score": 30
    },
    {
      "name": "Tag & access",
      "description": "Applies `--tag` and `--access` flags on `npm publish` when tag or access options are provided so the registry reflects the requested channel and scope.",
      "max_score": 15
    },
    {
      "name": "Dry run flag",
      "description": "Uses `npm publish --dry-run` (or equivalent CLI option) when `dryRun` is requested, ensuring no artifacts are uploaded while still producing publish output.",
      "max_score": 15
    },
    {
      "name": "Auth & OTP",
      "description": "Passes the provided auth token and one-time password through npm CLI options (`--otp`, `--registry`, env config) instead of hardcoding credentials or skipping 2FA flows.",
      "max_score": 15
    },
    {
      "name": "Rollback unpublish",
      "description": "Performs rollbacks via `npm unpublish <name>@<version>` (with `--force` when needed) scoped to the target version, avoiding full package removal and honoring the 24-hour window check.",
      "max_score": 25
    }
  ]
}