Test reliability automations now measure your default branch

Reliability automations used to measure every run of a test, whichever branch it came from, so uploading pre-commit results meant letting work-in-progress failures move the number that decides whether a test gets quarantined.

They now measure runs on your project's default branch. There is nothing to configure: existing alerts pick it up, and send your pre-commit runs to Tuist to get the reports and failure detail while the reliability figure keeps describing your trunk. A test case needs at least ten default-branch runs in the window before an alert acts on it, so a single bad run cannot quarantine anything.

Flakiness automations are unchanged and still measure every branch.