Seems to be a caching bug, we've redeployed and all is no longer lost :) Please try again, we definitely appreciate finding edge-cases like these.