Thanks Ben, we are unable to reproduce this in a simple repo but we are continuing to investigate.
We did notice something odd in the mergeinfo of the affected branch though. It lists a set of revisions for *itself*, which we don’t see elsewhere. Is this valid? This repo has had a lot of activity, but we think this may have happened when it was deleted and recreated at one point (and possibly had revisions cherry-picked into it).
