👷 Retitle release commits to 🚀

The release commit message is a machine-read convention (release-gate
in ci.yml skips the redundant main CI run on it), so the emoji carries
weight: change the mint in scripts/release.sh, the recognized pattern,
and both docs in one atomic commit. No tags or release commits exist
yet, so nothing historical parses differently. 🚀 matches the
gitmoji semantic (deploy/publish) better than 🔖 here.

.gitea/workflows/ci.yml

@@ -16,7 +16,7 @@ jobs:
     # pushes `main` and the tag seconds apart, and the tag points at exactly
     # the HEAD commit that push delivers — so the branch run would verify the
     # identical tree the tag run verifies anyway (plus `publish`). When a push
-    # to `main` is headed by a release commit (`:bookmark: Release x.y.z`, the
+    # to `main` is headed by a release commit (`:rocket: Release x.y.z`, the
     # single commit release.sh creates), the full CI is skipped here and the
     # tag run becomes the authoritative one for that SHA. All other pushes —
     # PRs, tags, ordinary `main` merges — see `skip=false` and run as before.
@@ -38,7 +38,7 @@ jobs:
                   # Keyed on the ref, not just the message: a tag run checks out
                   # the same release commit, and `publish` needs its `build`.
                   if [ "${REF}" = "refs/heads/main" ] &&
-                      git log -1 --format=%s | grep -qE '^:bookmark: Release [0-9]+\.[0-9]+\.[0-9]+$'; then
+                      git log -1 --format=%s | grep -qE '^:rocket: Release [0-9]+\.[0-9]+\.[0-9]+$'; then
                       echo 'Release commit on main — the tag run covers this SHA; skipping full CI.'
                       echo 'skip=true' >>"${GITHUB_OUTPUT}"
                   else