{
  "context": "Evaluates whether the solution uses @semantic-release/release-notes-generator to build release notes while controlling compare/reference linking and keyword customization required by the spec. Scoring checks correct mapping of the spec options into the plugin configuration and context so generated changelog URLs match expectations.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses generateNotes",
      "description": "Calls the package's generateNotes (or equivalent plugin export) instead of recreating changelog logic, providing commits, repositoryUrl, previousTag/currentTag, and version via the expected semantic-release context.",
      "max_score": 25
    },
    {
      "name": "Compare toggle",
      "description": "Maps includeCompareLink into pluginConfig.linkCompare so the emitted notes respectively omit or include the compare/vX...vY hyperlink exactly as the boolean dictates.",
      "max_score": 20
    },
    {
      "name": "Reference toggle",
      "description": "Drives pluginConfig.linkReferences from includeReferenceLinks to switch issue/commit references between hyperlinks and plain text rather than manually stripping links.",
      "max_score": 20
    },
    {
      "name": "Custom keywords",
      "description": "Uses pluginConfig.commit and pluginConfig.issue to apply the caller's commitKeyword/issueKeyword so generated commit and issue URLs contain those path segments (e.g., /changeset/<sha> or /tickets/<id>).",
      "max_score": 20
    },
    {
      "name": "Repository context",
      "description": "Supplies repositoryUrl, lastRelease, and nextRelease in the context passed to generateNotes so host/owner/repo resolution and compare tagging come from the package rather than hardcoded strings.",
      "max_score": 15
    }
  ]
}