That happens for any operator which triggers asynchronous behavior within itself (as opposed to simply forwarding or transforming signal events). Subscription has similar behavior too.

That said, we only ever do stuff like this if there's no `+currentScheduler`. Maybe that's what this heading should be about. "Signals may switch threads to deliver on a valid scheduler" or something?