fix: CI release tag_name must include v prefix to match git tag

Release was created with tag_name "0.8.1" but the git tag is "v0.8.1".
This caused an orphan release that /releases/latest couldn't find via
the real tag. Now uses "v${VERSION}" so the Release references the
actual pushed tag.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.gitea/workflows/build-release.yml

@@ -435,11 +435,11 @@ jobs:
           VERSION="${{ steps.version.outputs.version }}"
           GITEA_URL="https://git.command.vigilcyber.com"
 
-          echo "=== Creating Gitea Release for ${VERSION} ==="
+          echo "=== Creating Gitea Release for v${VERSION} ==="
           curl -s -X POST \
             -H "Authorization: token ${{ secrets.GIT_TOKEN }}" \
             -H "Content-Type: application/json" \
-            -d "{\"tag_name\": \"${VERSION}\", \"name\": \"Wraith ${VERSION}\", \"body\": \"Auto-release from CI build.\"}" \
+            -d "{\"tag_name\": \"v${VERSION}\", \"name\": \"Wraith v${VERSION}\", \"body\": \"Auto-release from CI build.\"}" \
             "${GITEA_URL}/api/v1/repos/vstockwell/wraith/releases"
           echo ""
           echo "Release created."