feat(release): use extracted CHANGELOG notes instead of --generate-notes

[asachs01]

Identical pass following the canary (WYRE-AI/node-datto-rmm#77, murph-reviewed and merged) for task_1788458278413_29823067.

Adds scripts/extract-release-notes.mjs and rewires PUBLISH mode's gh release create to use --notes-file from it instead of --generate-notes, falling back to --generate-notes on any read/parse failure or empty output (fail-open, boss's requirement). Byte-identical diff to the canary, which includes the fix for the single-# minor/major heading bug murph caught in review.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• Chores
  • Release creation now uses the curated notes for the matching version from the changelog when available.
  • If curated notes cannot be extracted, release creation automatically falls back to generated GitHub release notes.
  • Release note extraction validates version formatting and reports errors clearly when changelog content is unavailable or invalid.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 980c93bf-a741-4b9e-b6dc-f0a91ec88051

📥 Commits

Reviewing files that changed from the base of the PR and between ed10f7f and 5c92d8c.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• scripts/extract-release-notes.mjs

Included review availability: Your plan provides up to 10 included reviews per hour; 5 remain after this review.

---

📝 Walkthrough

Walkthrough

The release workflow now extracts the requested version’s notes from CHANGELOG.md. It uses those notes for GitHub releases and falls back to generated notes when extraction fails or returns no content.

Changes

Release notes extraction

Layer / File(s)	Summary
Changelog extraction and validation scripts/extract-release-notes.mjs	The CLI validates the version, reads CHANGELOG.md, supports one- and two-level version headings, and outputs a non-empty notes section.
Release creation integration .github/workflows/release.yml	The workflow uses --notes-file for successful extraction and --generate-notes after extraction failure or empty output.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 5c92d

Release publishing now uses curated changelog notes when available and retains generated GitHub notes as a fallback, with no current merge-blocking risk identified.

Sequence Diagram(s)

sequenceDiagram
  participant ReleaseWorkflow
  participant ExtractReleaseNotes
  participant CHANGELOG
  participant GitHubRelease
  ReleaseWorkflow->>ExtractReleaseNotes: extract notes for the release version
  ExtractReleaseNotes->>CHANGELOG: read CHANGELOG.md
  CHANGELOG-->>ExtractReleaseNotes: changelog content
  alt notes are non-empty
    ExtractReleaseNotes-->>ReleaseWorkflow: release notes
    ReleaseWorkflow->>GitHubRelease: create release with --notes-file
  else extraction fails or notes are empty
    ExtractReleaseNotes-->>ReleaseWorkflow: exit with status 1
    ReleaseWorkflow->>GitHubRelease: create release with --generate-notes
  end

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: release publishing now uses extracted CHANGELOG notes instead of GitHub-generated notes by default.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/release-notes-extraction

---

_{Comment @coderabbitai help to get the list of available commands.}

[asachs01]

Reviewed on behalf of murph (formal approval blocked -- shared wyre-agent-fleet identity can't approve its own PR, same wall as usual).

Confirmed byte-identical (diff-verified, not just visually) to the murph-reviewed canary WYRE-AI/node-datto-rmm#77, which included a real content-correctness fix I found and independently re-verified: the CHANGELOG heading regex now matches both ## (patch) and # (minor/major) headings semantic-release emits, fixing a bug where a minor/major release's notes either failed to extract or bled the wrong section's content (including BREAKING CHANGES) into an adjacent patch's release notes.

LGTM. Needs an actual approving click from Aaron -- this repo's branch protection requires 1 distinct-identity approval and no fleet agent can satisfy that here.