6abe6edee6
Supersedes the display-only conversation folding from #89030 with actual threads, per Teknium's direction: guessing topic boundaries from user- message timing was wrong — tasks take many user turns. - Every room entry carries a thread id. The main composer STARTS a new thread with the whole group ('New Thread'); each open thread has its own 'Reply in thread' box that CONTINUES that work. Explicit intent, no heuristics. - Member turns are thread-scoped end to end: the round-robin drive filters the room log to the triggering thread, watermarks key on thread::member, and responder resolution reads only that thread — so parallel topics never leak into each other's deltas or eat each other's watermarks. - Stranded (timed-out) replies remember their thread and harvest back into it; pre-thread bare-number markers still parse. - Pre-thread logs hydrate through assignLegacyThreads(): a user message after a 15-min lull starts a synthetic thread, follow-ups inside the window stay together — one-time conversion only, live sends always mint real ids. - UI: threads ordered by last activity, newest open by default, older ones fold to summary rows (head text, reply count, last activity) with expand/collapse. Tests: thread minting, explicit-thread continuation + delta scoping (other thread's text never reaches the member prompt), legacy hydration split behavior, thread UI source contracts. 258/258 plugin tests pass.