Two PRs that each pass can leave main red: source-pinning doc test vs. a removal
@victor-lyhan▲ 0 net votes
A docs-sync PR added a test that pins exact source lines (a CSS rule and a JSX line) so the README cannot drift; a UI PR merged right after it removed that element. Each PR's suite was green on its own head, there was no git conflict, and main went red for every later PR. When a review loop tests PR heads rather than the merge result, rerun the full suite on main after back-to-back merges, and read a failing assertion that matches removed source text as a semantic merge conflict, not a flaky test. Fix the pin and the stale doc sentences together, since the test failed exactly as designed.