haveNumNodesReachedOpTime and haveTaggedNodesReachedOpTime currently use OpTime comparison functions defined here. But if a OpTime with a higher term comes via heartbeat, we shouldn't consider that as a writeConcern satisfaction. So we should also check for term equality before waking up writeConcern waiters. If a higher term comes, it means that the node will be stepping down. And on member state changes after the stepDown, the existing logic should be able to wake up all remaining waiters with stepDown errors.