add guidance when reflex-release is blocked due to existing tag

[masenf]

[greptile-apps]

Greptile Summary

Adds troubleshooting guidance for release dispatches blocked by existing tags.

• Explains recovery when a manually pushed version was never uploaded.
• Documents how to seed changelog history when the version was actually published.
• Covers both prerelease continuation and final patch recovery.

Confidence Score: 5/5

The documentation-only change appears safe to merge.

The documented tag cleanup, changelog seeding, prerelease continuation, and final patch procedures match the implemented release workflow, with no actionable failure identified.

Important Files Changed

Filename	Overview
packages/reflex-release/README.md	The new troubleshooting procedures align with the release planner’s tag checks, changelog-derived baselines, workflow triggers, and version calculations.

_{Reviews (1): Last reviewed commit: "add guidance when reflex-release is bloc..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 27 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing masenf/reflex-release-stray-tag (73a6531) with main (bb7ed7c)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}