It appears that due to a bug somewhere, we might end up in a situation where the client tries to process instructions for non-existent tables. Instead of blindly applying the instructions and relying on Core to assert the table existence, the client should verify that a table exists and emit a bad changeset error if it doesn't. This will:

1. Prevent the app from crashing.
2. Help us debug and diagnose such issues.