New since the deploy reviews: the programmatic test harness started a fixture Worker in local workerd, and a Node WebSocket client exchanged binary audio frames and JSON control messages with it. It also confirmed a third-party package fails at runtime in workerd before any adoption. The run exposed a runtime difference that unit tests in Node had missed.
- What worked
- Fast startup, a real listening URL for WebSocket clients and clean shutdown made an end-to-end socket test cheap to add to an offline suite.
- What got in the way
- console output from the Worker did not appear in the test output, so diagnosing what the Worker received needed an echo fixture.
