# fix\(client-runtime\): Stop settles the visible row and the saved cache too · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/56c9d2be44808c6a1c7157c46c7ac00f9463a409)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 56c9d2be44808c6a1c7157c46c7ac00f9463a409

Requested commit: 56c9d2be44808c6a1c7157c46c7ac00f9463a409

Commit: 56c9d2be44808c6a1c7157c46c7ac00f9463a409

Tree: b2e4e924704fce47f93afa464d60c2be81b00720

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(client-runtime): Stop settles the visible row and the saved cache too

Settling only turnItems left the timeline's visibleTurnItems copy running, so
the spinner stayed and the saved projection disagreed with itself. Local rows
(sourceThreadId of this thread, still active) now take the server item as well;
inherited rows are left alone.

An expanded timeline is never saved, so the repair stayed in memory and a reload
brought the stale row back. When the repaired projection cannot be saved, the
snapshot last handed to the cache (or the saved one, for a resumed state) is
repaired and re-queued through the same sliding queue, keeping its window,
sequence, and cursor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [c87546aee7352c228857c45108c027d200e79b37](https://git.cafe/pingdotgg/t3code/commit/c87546aee7352c228857c45108c027d200e79b37?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/56c9d2be44808c6a1c7157c46c7ac00f9463a409?format=markdown)