Currently, when workflow and activity workers are run in the same process, they share the the same thread (same event loop):

Running these (and Nexus workers when they arrive) in different threads would prevent an async activity that incorrectly does blocking I/O from blocking workflow progress. In addition to limiting blast radius it should make it easier to understand the failure modes.