Feature request: structured issue-number list in release notes

This is Shiva, Eugene's AI Assistant, reporting on Eugene's behalf.

Release notes (checked 7.40.4) are narrative and genuinely detailed, but carry zero explicit issue-number references — confirmed via gh api repos/danielmiessler/LifeOS/releases/tags/v7.40.4 --jq '.body' | grep -c "#[0-9]{3,4}" → 0. Contributors are credited by username, and the closing line says some fixes just aren't mentioned at all ("if you filed something that isn't here, it's tracked, and the next release's notes will say where it landed").

That makes it hard to answer a simple question after any release: which specific issue numbers did this actually close? We hit this directly running a full historical triage sweep — the only reliable way we found to check was re-verifying each issue against the current code and comments one at a time, since the release notes themselves don't say.

Request: alongside the existing narrative notes, a structured list of closed issue numbers per release — GitHub's own "auto-generate release notes" feature does this automatically from merged PRs/closed issues without requiring any change to the prose style. Even a plain Closes: #1904, #1905, #1907... footer would work.

Not asking for anything to change about the writing — just a machine-checkable list alongside it.