# fix\(client-runtime\): Stop settles cached work the server already finished · pingdotgg/t3code

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

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

Visibility: public

Requested revision: a19e624e7d2cc55951bb29ac56b5adbe30468830

Requested commit: a19e624e7d2cc55951bb29ac56b5adbe30468830

Commit: a19e624e7d2cc55951bb29ac56b5adbe30468830

Tree: 40b5ca7095749f2a8fbffca5c4870c4eac8e408e

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(client-runtime): Stop settles cached work the server already finished

A cached thread can resume with a command still marked running after the
server finished it. No later event names that item, so Stop left the
Running banner up. When Stop lands while the local projection still lists
pending background items, re-read the server's snapshot and install it.

Replaces the provisional commands.test.ts reproduction with state-level
tests for stale and truly running work.

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

```

## Parents

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

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