Seems reasonable for rauth either to provide an accessor to the refresh token or even a callback function for when it changes; pushes storage of the refresh token across invocations off to the API consumer.  Or it could always just refresh the token the first time it's used; ie, assume the token is always invalid to start.