ci(release): create the GitHub Release the workflow never made

This repository has four tags — v0.2.2, v0.3.0, v0.4.1, v0.4.2 — and, until now,
zero GitHub Releases. Nothing failed and nothing warned: the release workflow
simply had no step that creates one, so the release-notes page never existed for
this repository at all. Every sibling plugin repository has that step.

It is not only a missing page. The notes are an indexed surface, and a directory
that grades MCP servers reads a `releaseSeries` to judge maintenance — this
repository's is empty, so a project that has cut four tagged versions looks, from
the outside, like one that has never released anything.

Two changes:

- The three versions that are actually on npm get their Releases, with notes taken
  verbatim from this repository's own CHANGELOG: v0.2.2, v0.3.0 and v0.4.1.
- The step is added to `release.yml` so it cannot recur. It is gated on
  `github.event_name == 'push'`, exactly like the publish above it, which gets both
  behaviours right for free: a manual run still rehearses everything and stops
  before creating anything public, and a release that fails never reaches the step
  — run #7, the v0.4.2 tag, failed at the publish and correctly produced no
  Release.

**v0.4.2 deliberately keeps no Release.** It is tagged, but its npm publish never
succeeded: npm's registry cannot match this repository's immutable OIDC subject
claim (npm/cli#9969), and the documented manual fallback only stages a version and
occupies the number permanently. A Release for it would assert that something
shipped when nothing did. It gets one the day the publish succeeds.

Author: PerryLink

.github/workflows/release.yml

@@ -336,3 +336,20 @@ jobs:
             echo "::warning::the MCP Registry publish of $name@$version failed. npm is published; the registry entry is not. Re-run the failed jobs of this workflow to retry it -- every step here is idempotent, and an already-published version is skipped rather than re-published."
             exit 1
           fi
+
+      - name: Create GitHub Release
+        # This step was missing until 2026-10-09, and its absence was invisible:
+        # the four tags had no Releases at all, so the release-notes page - an
+        # indexed surface, and the `releaseSeries` a directory such as Glama reads
+        # to judge maintenance - simply did not exist for this repository. Every
+        # sibling plugin repository creates one; this one never had the step.
+        #
+        # Gated on the same event as the publish above, for the same reason:
+        # a manual run rehearses everything and stops before creating anything
+        # public, and a release that FAILS does not reach here at all (run #7, the
+        # v0.4.2 tag, failed at the publish step and correctly produced no
+        # Release). So a Release appears exactly when a version actually shipped.
+        if: github.event_name == 'push'
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true