I may be a bit late into this conversation however I noticed the issue as soon as I looked at the End date of the first record and the start date of the second record. The dimension records in SCD II scenario always need to be contiguous with respect to time. No gaps and no overlaps.
Clearly we have an overlap here. So the end date of the first records can't be the same as the start date of the second. The second record could start on 28/11 or if that does not accurately reflect the data the timestamp data type could achieve this objective where the timestamp portion of Date column can be apart by 1 second. Although I have never seen anyone bother with data type of timestamp for start and end date for SCD II.
More often than not column type is DATE and if an attribute of a person changes such as Marital status there would be no need to account for the minutes and seconds as when he/she got married and Date would be sufficient.
He was single yesterday (Jan 1) and got married the next day (Jan 2).
Am I missing something? I have been implementing this approach for years which also happen to be the same as Kimball's.