I suspect that a possible explanation could be similar to what I've attempted to describe here: Ensuring _any_ isolation of a non-Sendable type - #2 by nkbelov
Calling notOk from actor A and then again from actor B captures op (and, in turn, the non-sendable self.value) into tasks isolated to two different actors.