OK... while the ASCOM docs state 360 is not a valid position, I have added code to normalize that position just in case it is returned by a device anyhow (The driver @Andy wrote does not appear to be doing this... just a general comment). Furthermore, I believe I corrected the issue that was blocking your sequence and not allowing that position to be "in tolerance".
It will be in the next 2.5.2 beta.