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

• Release Improvements
  • GitHub releases now use the curated notes for the corresponding version when available.
  • If curated notes are unavailable or cannot be read, release creation falls back to automatically generated notes.
  • Release note extraction supports standard one-level and two-level version headings in the changelog.
  • Clear warnings are provided when curated notes cannot be used.

[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: a3a451e8-7e27-40f2-9a42-d5732b5af58a

📥 Commits

Reviewing files that changed from the base of the PR and between 8bc15cd and e2ec95e.

📒 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; 4 remain after this review.

---

📝 Walkthrough

Walkthrough

The release workflow now extracts the target version’s notes from CHANGELOG.md. It passes nonempty notes to GitHub release creation and falls back to generated notes when extraction fails or returns no content.

Changes

Release notes flow

Layer / File(s)	Summary
Extract and publish release notes scripts/extract-release-notes.mjs, .github/workflows/release.yml	The extractor validates the version, reads CHANGELOG.md, and returns the matching one- or two-level release section. The workflow uses the extracted notes with --notes-file and falls back to --generate-notes when extraction fails or returns empty output.

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

Merge Risk: ⚪ Minimal · up to e2ec9

GitHub releases now use the matching curated changelog section when available and retain generated release notes as a fallback. The change is ready to merge with no identified release-blocking risk.

🚥 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 identifies the main change: release publishing now uses extracted CHANGELOG notes instead of GitHub's --generate-notes.
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.