Release workflow fails if dispatched before exact-SHA CI / Packed install finish #332

What happened
The 0.2.45 Release run 40591839135 was dispatched at 2026-10-27T22:03:50Z, ~14s after the #331 merge push to main. CI on a7ff3b6 took 1h49m and Packed install lifecycle 44m, so the "Exact-head CI conclusions" step read CI=none packed-install=none and release verify failed closed:

release verify: NOT READY — 2 blocker(s):
  - packed-install-lifecycle is missing
  - platform-ci is missing

v0.2.45 stayed unpublished for ~2 days. Re-dispatching the same version/sha on 2026-10-29 (run 40884307777) passed (release verify: READY) and published v0.2.45.

Suggestion
Either have the exact-head step wait/poll (with a timeout) while CI / Packed install are in_progress, or have the release docs/train say to dispatch only after both are green on the main SHA. Fail-closed behavior itself is correct; the failure mode is just silent until someone checks.