[FEATURE] Include GitHub issue numbers in release notes / changelog

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When a bug is fixed or a feature request is implemented, reporters have no way to know:

• Which release includes their fix
• Whether their reported issue was actually addressed

The only current signals are:

• Issue being closed (sometimes with "fixed" label, sometimes not)
• General release notes that describe changes but don't link back to issues

This creates a disconnect between the issue tracker and the changelog. Reporters must either:

• Manually check each release note looking for their issue
• Keep their issue open indefinitely to ask "was this fixed?"

Related: #15692 discusses this feedback loop gap.

Proposed Solution

Include GitHub issue numbers in release notes when a fix or feature addresses a reported issue.

Example changelog entry:

### Bug Fixes
- Fixed race condition in file watcher (#XXXXX)
- Resolved terminal rendering issue on Windows (#YYYYY, #ZZZZZ)

This provides:

1. Automatic notification to reporters (GitHub notifies on issue mention)
2. Traceability between releases and issues
3. Credit to reporters who took time to file issues

Alternative Solutions

• Close issues with "fixed in vX.Y.Z" comment: Requires manual effort per issue
• Public roadmap with issue links: Helpful but separate from release flow
• Do nothing: Reporters remain in the dark

Priority

Medium - Would be very helpful

Feature Category

Documentation

Use Case Example

1. User reports bug with detailed reproduction steps
2. Anthropic fixes the bug internally
3. New version is released with changelog entry: "Fixed file watcher race condition"
4. User sees changelog but can't tell if their specific issue was addressed
5. User comments on their issue: "Was this fixed? Which version?"

With issue numbers in changelog:

• Step 3 becomes: Changelog entry includes issue number
• User gets GitHub notification automatically
• User knows exactly which version to update to
• No follow-up comment needed

Additional Context

Prior art:

• Most OSS projects include issue numbers in changelogs (React, Vue, TypeScript, etc.)
• GitHub automatically linkifies issue references
• Conventional Commits spec recommends issue references

Cost:

• Minimal: just include issue number in changelog entries
• Can be added to existing release workflow

Benefit:

• Closes feedback loop automatically via GitHub notifications
• Builds trust: "my issue was heard and fixed"
• Reduces "is this fixed?" comments on issues

---

✍️ Author: Claude Code (Dev Container) with @carrotRakko

Note: This issue was written and submitted by an AI agent (Claude Code), with human review and approval.