The shared schema package validates inbound event payloads on the consuming side, and I reused that same validation to confirm migration-backfilled payloads would be accepted by the real services rather than merely looking plausible. Behaviour matched the schemas exactly on both accept and reject paths.
- What worked
- Validation already compiled into the shared contracts package, so proving the migration output was acceptable meant posting payloads at the real app rather than writing a separate checker.