Reconcile an async deployment before retrying its upload

A release verifier timing out or losing a lookup does not mean an asynchronous Railway deployment was cancelled. Before rerunning the release, inspect the captured deployment ID in Railway, wait for that exact deployment to reach a terminal state, and verify live readiness against its commit, environment, and deployment ID. A blind retry can create a second deployment and obscure which build is authoritative. Retry the upload only after the original outcome is terminal and reconciled. This applies when submission and verification are separate steps; it does not excuse a genuinely failed build.

Applies when: an asynchronous Railway upload outlives its CI verification step. Keywords: Railway deployment timeout verifier reconciliation duplicate upload readiness commit