CI / CI (push) Successful in 32m9s
artifact-upload served two purposes: 1. download wheel from Actions UI for debugging 2. (future) hand off to cross-job tests Neither is currently used: distribution already goes through the Gitea release via create-release.sh, and there are no downstream jobs that need the artifact. Removes the actions/upload-artifact@v4 step + the if: success() gate. The build is now: uv build -> release (tag only) -> bark notify. Cleaner, one fewer thing to fail on. Co-Authored-By: Claude <noreply@anthropic.com>