# docs\(server\): pin interleaved-collapse divergence as intentional with test · screen/t3code-personal

[View on GitCafe](https://git.cafe/screen/t3code-personal/commit/e4abc31f1e3f930e521a5bb62b38a9c5b28d8fb1)

Repository: [screen/t3code-personal](https://git.cafe/screen/t3code-personal)

Visibility: public

Requested revision: e4abc31f1e3f930e521a5bb62b38a9c5b28d8fb1

Requested commit: e4abc31f1e3f930e521a5bb62b38a9c5b28d8fb1

Commit: e4abc31f1e3f930e521a5bb62b38a9c5b28d8fb1

Tree: eb0578ff975b6149dcf0b19ee92e2574665152c5

Author: Theo Browne

Committer: Theo Browne

## Message

```
docs(server): pin interleaved-collapse divergence as intentional with test

Bugbot flagged that clients collapse only adjacent lifecycle rows, so
dropping a superseded update separated by an interleaved parallel call
diverges from full-history rendering. Measured on a real database: 1.5%
of dropped rows (553/36,581), all pure in-flight state whose final result
the retained completion still shows, and zero dropped rows carry a
client-merged payload field their completion lacks (verified across all
49,515 update rows). Documents the tradeoff and adds a test pinning it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [b7d1981b57f1c30908808d1939fd4edbc781de12](https://git.cafe/screen/t3code-personal/commit/b7d1981b57f1c30908808d1939fd4edbc781de12?format=markdown)

[Source at this commit](https://git.cafe/screen/t3code-personal/tree/e4abc31f1e3f930e521a5bb62b38a9c5b28d8fb1?format=markdown)