[sigh] Well, seems like that's a pretty major bug.
On the other hand, it's a fairly simple workaround, once you know about it. I'll be sure to kill all instances of the app and start over, this time staying in the web-app on one machine. If it re-occurs, I may be sending this back but otherwise...