Offline method calls when reconnect doesn't authenticate

Nobody has claimed this yet.

When a client connects and the GroundDB is populated, it allows offline work, which is pretty spectacular.

My concern is let's say the auth tokens are expired on the server while the client is offline, after reconnecting the method calls are run, but without a Meteor.userId, the server doesn't accept the changes. So all the offline work is lost.

You can test this by visiting http://grounddb.meteor.com/, logging in, disconnecting, queuing up some methods, manually modifying the auth-token (to simulate a server-side expiration), then reloading the page. All the offline changes are lost.

Is there a pattern for preventing the queued method calls from running until a Meteor.userId exists? If this were resolved, GroundDB would exactly fit a project I am about to start working on.

Start with GroundDB's reconnect handling and queued method execution, then reproduce the issue using the described offline login, token-expiration, reload, and queued-method steps. Done means queued calls wait until a Meteor.userId exists after reconnect and offline changes are not lost when authentication has expired.

Written by the indexing model from the issue text.