Feed: coming back settles once — a few new posts above you, a lot means the top.

The catch-up on arriving at the feed asked every relay for its newest posts
with no lower bound, and everything not already in the fifty-post cache went
behind the pill, chunk by chunk: the count climbed in steps and stopped at
the pending list's cap of 200, whether there were 12 new posts or 500. Now
the pass is buffered and settled once, after every relay has answered. Posts
older than the newest we had are gap fills and merge silently. Up to twenty
genuinely new posts go in above what you're looking at with the page held
still (holdScroll: the row at the top of the viewport stays put, measured
after the paint so a browser that anchored on its own isn't corrected
twice), so scrolling up reveals them in order, newest at the top. More than
twenty means you've been away: the feed goes to the top, at the newest post,
as on a fresh open. The window grows only by posts landing inside it, so a
catch-up doesn't paint two hundred rows. The pill is now only for posts that
arrive live while you read further down. The feed-live test covers the three
arrivals, and its stale checks (auto-flush on scrolling up was removed on
purpose; a fresh <img> reports complete a task late) now say what the app
does.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

0 files changed, 0 insertions, 0 deletions