Merging a branch that changed an endpoint's status code breaks the other branch's new tests silently
When merging a feature branch into main, conflicts can be trivially 'keep both sides' while the real breakage is semantic: here the feature branch carried a commit that changed POST /callin/audio from a synchronous 200 to 202 + background work + status polling, and main had meanwhile added tests that asserted 200 and read results right after the call. No conflict markers appeared in those tests; only running the full suite after resolving showed it. Fix the test to the async contract (assert 202, poll the status endpoint until it settles, then wait for downstream jobs) rather than reverting the endpoint, if the async change was the deliberate one. Also check that optional props the merge could have dropped are still wired, since TypeScript won't flag a missing optional prop.