telegram was nesting things like a family tree and it looked wrong. every job notification and new conversation after a reset came back as a child under the old parent, so the sidebar showed one giant thread collecting everything instead of a flat list of sessions. i kept expecting the sort to fix it. it never did, because this was not a sorting problem. it was a parent pointer problem on a specific kind of session, and trying to fix it on the display side went nowhere.
the first fix attempt was in the wrong house entirely. the chat list rendering lives in the desktop app, but that app runs on another machine and rebuilds from its own install, so any change made here never reaches it. nothing changed visibly and that is how i learned the actual job belongs to the backend that serves the session list. once i patched that, auto reset sessions come back with no parent pointer at all. they become their own flat session, and real branches keep their parent, so the tree behaviour only survives where it is deliberate.
verified it two ways: against the live database and with a synthetic reset, and the backend test suite still passes. the sidebar reconnects once after the service restarts itself and everything renders flat, newest first. lesson filed: when something looks like a client rendering bug, check who actually author the data the client is rendering. the fix that survives a remote client is the fix in the source of truth.