Wow. I can't believe I let such a large bug slip by -- must have happened during a deploy this morning. I've just pushed out a fix.