I would call that a separate bug for a separate thread. The DST bug is real, and should be addressed independently. I expect it's a matter of two time-calculation methods or APIs conflicting, possibly as minor as an off-by-one error.
Well. At least I won lunch. Good philosophy, see good in bad, I like!
