[P1][Tier 4] AI-assisted release/status-notes generation

Tier 4 — FC-specific leverage · Priority: P1

Gap

The FC has no AI-assisted release/status-notes generation. Our epic score table already names "missing … release-notes … automation" as a Tier 4 gap, but there is no tracked child issue for it. dotnet/sdk's AI Engineering epic (#55185) has systematized this as a supported generate-release-notes workflow.

Investment

• Build an AI workflow/skill that drafts release notes or status summaries from merged PRs / closed issues over a range (milestone, date window, or build), in the team's expected format.

Acceptance criteria

• A skill (or agent workflow) that produces a draft release/status-notes document from a defined change set.
• Output format matches how the team currently authors release/status notes.
• Documented invocation (inputs: range/milestone; output location) discoverable by agents.
• Piloted on at least one real release/status cycle.

Reference

• Adopted from dotnet/sdk epic #55185 (Tier 4 "systematize existing bets" → generate-release-notes).

Part of epic #3273

Start by reading epic #3273 and the referenced dotnet/sdk issue #55185 to understand the proposed generate-release-notes workflow and the team's current release/status-note format. Define the workflow's change-set inputs and output location, then validate it through one real release/status cycle; done means all four acceptance criteria are met.