[ryanbr]

Follow-up to #790, and the part of #736 that fixes what was actually reported.

#790 landed the convention, the corrected v9.1.0 credit line, and a collector for the handles. All of that
governs the curated section at the top of a release body. This governs the auto-generated PR list
below it, which is where the handles were being destroyed.

The mechanism

fork-release.yml post-processes GitHub's generated notes and did two destructive things:

| sed -E 's/ by @[A-Za-z0-9_-]+//g' \                       # every handle, gone
| awk '/^#+ *New Contributors/{skip=1; next} ...'           # the whole block, deleted

Measured against v9.1.0's real generated notes, that removed 66 by @handle credits covering 7 distinct
third-party contributors, plus the New Contributors block. The issue reads as drift in hand-written prose
because this is invisible from the release page — so implementing its four suggestions literally would still
have left every contributor's handle off the next release.

The comment justified it with "this is a solo fork". That premise has expired: 16 people have landed merged
PRs here, 7 of them in v9.1.0 alone.

The fix

Targeted rather than a revert. Un-stripping everything would stamp by @ryanbr on nearly every line — the
self-credit noise the convention exists to avoid, and a self-mention notifies nobody. So the maintainer's own
handles keep being stripped and everyone else's is kept:

| sed -E 's/ by @([Rr]yanbr|[Ff]anboynz)([^A-Za-z0-9_-]|$)/\2/g'

Nothing deletes the New Contributors block any more, so it returns.

Verification

Run against v9.1.0's real generated notes, not a mock:

• third-party credits kept: 35 (was 0)
• maintainer credits surviving: 0 of 31
• New Contributors block: restored
• shortened lines stay well-formed — … (#613) in https://…; the trailing capture group is what preserves
  the following separator
• YAML re-validated

One workflow file, 7 insertions / 4 deletions. No app or package code, no parity surface.

Closes #736.