Enable required checks

Require status checks before merging on the backend repo: enable the CI pipeline named unit-and-lint, require it to pass, and block merging if the check is missing. Apply the requirement to the develop branch, add the devops lead Priya and engineering manager Carlos to the required reviewers list, and verify one successful run before marking the enforcement complete.

Before I make the unit-and-lint check required, make the PR experience obvious: put the pass/fail badge and the failing tests summary at the top of the pull request description, identify flaky tests that cause false negatives, and list quick fixes that reviewers can accept without rerunning the entire pipeline. Highlight any checks that run on forks so external contributors can get clear guidance.

I flipped on the required unit-and-lint check for develop, and external contributors report their pull requests show a missing status and are blocked from merging. I fear we'll lose open-source contributions and get bug reports. I don't know whether the problem is checks not running on forks, missing permissions, or a naming mismatch. What is the most likely culprit and the step-by-step fix that restores contributor builds while keeping the check enforced?

Over time we tack on more required status checks until PRs take hours before merge. That kills sprint velocity and makes engineers bypass rules. I need a new habit to avoid runaway check bloat. Recommend criteria for when a check warrants 'required' status, a retirement cadence for low-value tests, and a governance step to approve new requirements.