bug: Pinned navigation on long sessions working on desc order, but not asc

[MCBoarder289]

Curious if anyone else is experiencing this. I have a session with roughly 8000 lines in the JSONL, and we recently implemented a fix that scrolls to the pinned message location when navigating from the pinned message pane (original issue)

After that merge, this works when I view the session first and set my message order to descending. But if I start at the pinned message screen and navigate (default is ascending message order), it overshoots and I have to scroll back up after the auto navigation.

I think there might be a small regression in the behavior from my original forked commit, but I can't seem to nail it down. For reference, here are the various iterations of the fix and what ultimately got merged in. It's also totally possible that some other FE change might have impacted this:

Original commit on my fork(works both ascending/descending)

Refactor commit on my fork (appears to not work on ascending)

Squashed/merged commit that's actually in main (combines the above, appears to not work on ascending)

I'll see if I can get a screen recording of the behavior and also try and look into a fix.