👷 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.

scripts/release.sh

@@ -103,10 +103,10 @@ fi
 echo "Amending release commit..."
 git add package.json package-lock.json "${CHANGELOG}"
 # The exact message format is load-bearing: the `release-gate` job in
-# .gitea/workflows/ci.yml recognizes `:bookmark: Release x.y.z` on main and
+# .gitea/workflows/ci.yml recognizes `:rocket: Release x.y.z` on main and
 # skips the full CI run, since the tag push immediately after verifies the
 # identical SHA (and publishes). Keep the two in sync.
-git commit --amend -m ":bookmark: Release ${VERSION}"
+git commit --amend -m ":rocket: Release ${VERSION}"
 
 echo "Creating tag ${VERSION}..."
 git tag "${VERSION}"