Previously, the data quality check was re-run by the Orchestrator whenever an event was added to a superevent. Depending on the result, the superevent would have been updated. This feedback between the Orchestrator and the Superevent Manager was race-prone.
Now, the Superevent Manager is responsible for running data quality checks whenever an event is ingested, and the data quality status is included in both the public alert condition and the preferred event sorting key.
Note: merge !502 (merged) first.