{
  "context": "Evaluates how well the solution uses @semantic-release/release-notes-generator and its conventional-changelog-writer pipeline to render Markdown release notes from conventional commit data. Focuses on configuring plugin context and writer options to group commits, normalize repository links, and surface breaking changes that align with the spec scenarios.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Generate notes API",
      "description": "Uses @semantic-release/release-notes-generator generateNotes (or the plugin's default export) to render release notes instead of manual formatting, supplying the commit list and semantic-release style context objects.",
      "max_score": 20
    },
    {
      "name": "Compare link context",
      "description": "Passes previousTag/currentTag and repositoryUrl (or host/owner/repo) into the plugin context so conventional-changelog-writer produces a compare range header built from the tag pair.",
      "max_score": 20
    },
    {
      "name": "Section mapping",
      "description": "Configures writerOpts or presetConfig (such as transform/types) so feat and fix commits render under Features and Bug Fixes, chore types are renamed to 'Maintenance', and test commits are filtered out before writing.",
      "max_score": 20
    },
    {
      "name": "Link formats",
      "description": "Normalizes repository URLs (including stripping .git and enforcing https when appropriate) and sets commitUrlFormat/linkCompare/linkReferences to emit working commit links and compare URLs based on the repo path.",
      "max_score": 20
    },
    {
      "name": "Breaking changes",
      "description": "Ensures notes titled 'BREAKING CHANGE' surface under a BREAKING CHANGES section via writerOpts (e.g., noteGroupsSort/transform), preserving the note text and commit reference in the rendered output.",
      "max_score": 20
    }
  ]
}