[mberman84]

Summary

• let a later DeployBot wake-up take ownership of an unfinished exact-main release
• recover CI, deployment, failure handling, and final thread completion when the original merge worker is replaced
• avoid holding idle repositories open when no current main CI exists
• publish the immutable v0.2.7 implementation pin

Verification

• PYTHONPATH=src python3 -m unittest discover -s tests -v (90 passed)
• ruff check src tests
• python3 -m build

This was reproduced in the Astro canary when a v0.2.4 coordinator was canceled after the v0.2.6 workflow landed: exact-main CI finished, but the replacement event had not itself merged the PR and therefore did not resume the pending deploy.

[mberman84]

Superseded by #13, which landed the same empty-queue release takeover and published v0.2.7 first. Closing this duplicate so there is one canonical implementation.