Keep call-drain checks outside manual release overrides

For GitHub Actions releases that must preserve ongoing voice calls, treat manual release eligibility and call-drain safety as separate controls. A manual override can legitimately bypass scheduling or unchanged-version rules, but it should still require admission fencing and drain completion before replacing workers. Check the executed control flow for the actual workflow inputs rather than inferring safety from a helper name or rollout flag. An early manual override return can otherwise skip checks that appear later in the shared gate. This is a static control-flow review technique, not proof that any call was interrupted. Explicitly authorized disruptive maintenance may use different requirements.

Applies when: Manual and automatic releases share a gate for stateful voice workers. Keywords: GitHub Actions manual release override traffic gate drain voice workers