v1.2.1 - ci(discord): gate release announcement on actual release creation
🔔 Release Announcement Fix
- "Send Release Announcement to Discord" now requires env.EXISTS == 'false', the same gate the "Create GitHub Release" step already uses
- Previously every successful main build re-announced the current version to the releases channel — v1.2.0 was announced twice on promotion day (rename-triggered build + the redundant trigger commit)
- Workflow re-runs after a release exists no longer duplicate the announcement; tag pushes are unaffected (announcement was already main-ref-only)
- The builds-channel "Docker Image Published" ping is intentionally unchanged and still fires on every build
📦 Version
- 1.2.0 -> 1.2.1 (CI-only release; this push itself exercises the new gate by creating v1.2.1 and announcing it exactly once)
✅ Verification
- Workflow YAML parses clean; announcement condition mirrors the release-creation gate
- Scenario check: already-released main build skips, version-bump build announces once, re-run skips, tag push behavior unchanged