a70e4e72968eb0506762af6177fe0838fefc98a1
A recovered row was appended, so it landed at the bottom of the conversation instead of beside the call that spawned it. It has no timestamp, but it does not need one: the harness stamps the task id into the output of the tool call that started it, and live the task:started event arrives right after that tool result — so anchoring there reproduces the position the row would have had. First mention wins, and that is the correctness argument: the id is minted by the call that spawns the task, so nothing earlier can contain it. Matching the most recent instead was wrong, and real data caught it — a diagnostic that grepped the transcript printed both live ids and pulled the rows down beside itself. That case is now a test. Moved out of the hook into its own module since it is pure and has nothing to do with React. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
No description provided
42 MiB
Languages
TypeScript
90.9%
Shell
4.7%
JavaScript
4.1%
CSS
0.2%
HTML
0.1%