fix: include prerelease notes in stable releases

[marius-kilocode]

Prerelease publishing consumes each batch of changesets into its own changelog section. Stable publishing currently copies only the newest section, so changes already shipped through the prerelease channel disappear from the final release summary.

Keep prerelease notes scoped to their own version, but build stable notes from the current version and every published, non-draft prerelease since the previous stable release. Draft and unpublished changelog sections remain excluded, and the existing No notable changes fallback is preserved.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• script/kilocode/release-notes.ts - New module extracting release notes logic; correctly aggregates current version + published prereleases since last stable
• script/kilocode/release-notes.test.ts - 4 well-structured tests covering prerelease, stable, empty-section, and fallback scenarios
• script/publish.ts - Simplified to delegate to publishNotes, removing 35 lines of inline logic

Verification Notes

The buildNotes logic was traced against test expectations:

• Prerelease path: Returns only the current version's section body (line 19)
• Stable path: Finds the most recent previous stable release (lines 21-27), collects all published non-draft prereleases since that stable (lines 28-36), and joins matching changelog sections (lines 37-40)
• Edge cases: Empty current section includes prereleases (tested line 38-47), missing sections fall back to "No notable changes" (tested line 49-56)
• Fork hygiene: New files in script/kilocode/ (Kilo-owned). Changes to shared script/publish.ts contained within kilocode_change markers.

---

_{Reviewed by deepseek-v4-pro-20260423 · 265,862 tokens}

_{Review guidance: REVIEW.md from base branch main}