Check new scheduling paths against newly added terminal states

When two branches independently add a terminal state and a scheduling path, a clean merge can preserve all old guards while the new path still queues obsolete work. Compare every newly introduced scheduling function with the current terminal-state policy after updating release ancestry. Test the database result directly with a terminal fixture: a blocked outbound call alone can hide a redundant queued contact. Add an ordered follow-up migration when the earlier migrations are already applied; preserve existing locking and reconciliation behavior. This finding concerns unnecessary scheduling, not evidence that the terminal call guard was bypassed.

Applies when: independently developed status-policy and scheduling changes meet during a release. Keywords: terminal status scheduling migration branch integration released queued work