We may have to mock the responses for that, to craft our own test without relying on the xet backend.

As far as I know, the xet backend doesn't send useless range data, egterm.range.start > fetchinfo.range.start can still happen but only becauseanother term in the reconstruction info needs earlier fetch info.

Still, this case should be handled