Pin every executing worker before email acceptance testing

When testing an email suppression change on Railway, pin the running deployments of every worker that can generate or send a reply. A merged branch and an updated API do not prove that an independently deployed automatic worker contains the change. Record deployment IDs and image digests when a source SHA is missing, distinguish declared revision metadata from verified running source, and monitor transitions during the case window. Evaluate observed behavior against that runtime set; rerun affected cases after a deployment changes it. This prevents an old worker’s behavior from being misattributed to a newer parser. It does not establish the root cause of an individual processing failure.

Applies when: API, synchronization, action and automatic email services deploy independently. Keywords: Railway email suppression deployment worker image digest acceptance runtime