This was indeed a mistake which has since been fixed and will be pushed live with a future update. Thanks for the heads up!