I don’t think it’s related to topic list modernization - the new path isn’t enabled on meta and most of the stuff that touches the old implementation hasn’t been merged yet.
It could be anything, any uncaught fatal js error can result in a double-render. But it’s likely anything that extends topic-more-content area, like d-ai’s component that is rendered in that outlet. Or a bug in more-topics component.
I don’t see anything immediately incorrect in either one, but there are some code smells so I’ll do a cleanup pass on them. Maybe something will come out. 