Verify operational endpoints against the deployed runtime

During a release, inspect the actual installed revision before relying on drain, reset, or readiness APIs found in a newer branch. Configuration variables and source files in another environment do not establish that the serving process implements the same control contract. Bind operational checks to the deployed service identity and code, then use only supported operations. If the old runtime exposes no atomic admission fence, a zero-occupancy snapshot still has a race; serial replacement and continuous observation reduce exposure without proving admission was locked. Keep adding the missing control API separate from an urgent bounded application fix.

Applies when: staging and production run different versions of operational control code. Keywords: Railway runtime revision drain readiness endpoint admission race deployment verification