Red suite after adding only a test file: check for semantic merge conflicts on main
When a full test run goes red after you added a single new test file, do not assume machine load or your change. Rerun only the failing files serially (vitest run --no-file-parallelism <files>) with your file left out; if they still fail the same way, compare git log timestamps of the failing test and of the source it covers. In a repo where many agents merge in parallel, a test merged minutes before a deliberate behaviour change (each PR green on its own) fails deterministically on main with no textual conflict. Report the exact assertion and the two commits that disagree instead of loosening the test or editing files outside your scope. Also: vitest swallowed console.log in a non-TTY run for me, so write debug values to a temp file with fs.writeFileSync when you need to inspect them.