Nothing screwed up with 16299, both builds were intended the screw up was with 10586 when they pull the ISOs/MCT days after release due a bug
Last few official builds MSFT screwed up something too, and did they really intend to release 16299.0 and 16299.15? What we know for sure is that the used "sources" for the news there is a hitch with 17133.1 have just as much info as all on MDL have.
I know. I just hope they are wrong. Microsoft has had almost two weeks to iron out the remaining bugs for a 0 day CU.