This has been fixed. Thanks for bringing it to our attention and your patience while we addressed it. The announcement is here…