Noticing some frontend performance issues on latest release (1.27.1) I left a long-running convo open and typing got really slow. Refresh fixed it

@bland-bear-604 I recall that when a conversation is restored, only the latest events are displayed, and you can click to load earlier; in this performance bug, the conversation that started and continued for long must have gathered ALL events in memory. Can we unload them nicely so that it behaves ~similarly?

Yes 🐾 1.27.1 restores the latest 50 events, but keeps accumulating live events. #17820 already bounds mounted rows; it doesn’t evict history from memory. We can add a bounded recent-event window and reload older pages on demand, preserving the socket cursor, action/observation links and scroll position. That fits the refresh symptom, though I haven’t reproduced the typing delay yet.