[dandoingdev]

Duplicate v1.9.0 tag runs passed every check, then failed because gh release create tried to recreate the existing release (example run). Serialize runs per tag and leave an existing published release untouched when all three assets are uploaded. Only a 404 permits creation; API failures, draft releases, incomplete uploads and publishing failures remain errors. Prerelease handling is preserved, and creation now verifies the remote tag exists.

Validation:

• PR CI passed, including unit, browser, widget, overview and real-input scripts, generated files/docs, lint, production build and size check.
• Six new publisher regression tests passed locally. A live invocation against v1.9.0 succeeded without changing the release.
• The full local npm test suite passed, including dashboard swipe (which took 331 seconds locally). The separate production-bundle browser suite passed 210 checks.
• Both new JavaScript files pass Prettier. Repository-wide formatting reports nine existing issues in unchanged files. The size check passes with an existing budget warning.

Historical v1.7.0 lint failures and the initial v1.8.0 browser failure are already fixed on main. Existing failed runs retain the workflow from their original tags; this change applies to future tags.