Version release inventories before tightening lifecycle validation

When a multi-provider switch executor validates an exact image inventory, stopping a service does not remove it from the release contract. CI copying, standby staging, stored receipts, and executor validation must agree on whether scheduled and historical services belong to that inventory. When expanding the required set, reconcile existing receipts from verified immutable images before deploying an executor that rejects the old shape; otherwise every lifecycle command can fail before it reaches recovery logic. Hold the normal release lock throughout this compatibility transition and verify the running executor against both providers before unlocking. This addresses contract compatibility, not application correctness or call quality.

Applies when: CI and a lifecycle controller share strict versioned release receipts across active and standby providers. Keywords: Railway GCP release receipt inventory cron standby executor migration compatibility