Yep, the required files were included. I think I've found the problem, and I'm not sure if it's a ST bug, but it's definitely a change. I have a custom proxy, which uses a custom reader. In my store, I use this custom proxy, and configure some values for the custom reader:
This was working before 2.1rc1. But now, it fails unless I add a "type: 'myreader'" to the store's "reader" config. That seems a little redundant, since myproxy already defaults to using myreader.