Inspector Timeline: make loaded history reversible

[Phoenix500526]

While working on #3986, I found that reversing the Timeline order is only part of the interaction problem. Showing the newest turn first makes recent activity easier to find. However, after a user loads earlier records, those records remain expanded and there is no way to return to the initial view that contains only the recent page. In a long session, a user may load several earlier pages to inspect one older turn. Once their focus is deep in the history, returning to the newest turn requires scrolling through all of the loaded records again.

One possible direction is to make the Timeline header sticky within the Inspector scroll container. The Timeline heading would remain visible while the user scrolls through history. After earlier records have been loaded, the header could expose an action to collapse the loaded history and return to the initial recent-only view. Load earlier records would remain at the end of the Timeline, so users could still load multiple pages when needed. I would like feedback on this interaction model. Is a sticky Timeline header a good way to keep the collapse action reachable? Is there a better way to return from deep history to recent activity?

Here is another related issue #1625. It seems that @ARE404 is working on some relevant topic. Any thouhgt of this?

[Astro-Han]

Glad to see this land — #4120 covers the core need, and I like that it reuses the existing end-of-timeline button instead of adding sticky chrome. That seems like the simpler answer to "how do we keep the collapse action reachable": no new floating UI, and the action lives where the user's attention already is after loading history.

One residual gap I noticed while reading the merged code: canHideEarlier requires !nextCursor (use-session-trace.ts), so the collapse action only appears after the user has loaded all the way to the oldest page. The scenario in your OP — load a few pages to inspect one older turn, then jump back — isn't covered if the session has more pages than the user loaded; they'd have to keep loading to the end before "Hide all earlier records" appears. Was that condition deliberate (e.g. to keep the pagination cursor bookkeeping simple), or just the first cut? If mid-pagination collapse turns out to matter, an always-visible "hide earlier" next to "load earlier" whenever more than one page is loaded would cover it — two explicit buttons instead of one dual-purpose one, which may also read more clearly.

Either way, I'd lean against the sticky header now: the merged interaction is smaller, and the remaining question is just when the collapse action is offered, not where it lives.

(Drafted with AI assistance; behavior verified against main after #4120.)

中文版本

很高兴看到这个需求已经落地——#4120 覆盖了核心问题，而且我很喜欢它复用时间线末尾现有按钮的做法，而不是新增 sticky chrome。对于"如何让折叠动作够得着"这个问题，这似乎是更简单的答案：不加任何悬浮 UI，动作就待在用户加载历史后注意力所在的位置。

读合并后的代码时发现一个残留缺口：canHideEarlier 要求 !nextCursor（use-session-trace.ts），所以折叠动作只在用户一路加载到最旧一页之后才出现。你在正文里描述的场景——加载几页去查看某个旧 turn，然后想跳回最近——在会话页数多于用户已加载页数时还覆盖不到：必须先一直加载到底，"Hide all earlier records" 才会出现。这个条件是有意为之（比如为了让翻页游标的 bookkeeping 简单），还是第一版先这样？如果分页中途折叠确实重要，在加载超过一页时让 "hide earlier" 和 "load earlier" 同时常驻也能覆盖——两个明确分工的按钮，替代一个双用途按钮，可读性可能也更好。

无论如何，我现在倾向于不要 sticky header：已合并的交互更小，剩下的问题只是折叠动作何时出现，而不是它放在哪。

（本评论由 AI 辅助起草；行为已在 #4120 合并后对照 main 核实。）

[Phoenix500526]

That condition was deliberate. While more pages remain, showing “Load earlier records” and “Hide all earlier records” at the same time felt awkward because the two actions point in opposite directions. The current design keeps a single action in that position: it continues to load earlier records, then changes to “Hide all earlier records” once the oldest page has been reached. The tradeoff is the gap you described: users cannot collapse the loaded pages midway through pagination. I am not sure there is a clear and natural way to expose both choices without making the controls feel busy or confusing.I would be interested in alternatives that preserve the simple single-action flow while still allowing users to collapse the loaded history before reaching the oldest page.