# fix\(server\): reject replaying a command receipt across threads in v2 · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 187f1246d2d147641fa8db64d6fe095f83d39038

Requested commit: 187f1246d2d147641fa8db64d6fe095f83d39038

Commit: 187f1246d2d147641fa8db64d6fe095f83d39038

Tree: adb8ad3678f1ad58829688693ee72a2735f41525

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(server): reject replaying a command receipt across threads in v2

Ports v1's #5246 guard into the v2 dispatcher: a stored receipt only
proves that this exact command already ran for the thread it was recorded
against, so returning it for a command aimed at a different thread reports
success for work that never happened there. The check is extracted as
canReplayCommandReceipt so the rule is unit-testable, and reuse now fails
with OrchestratorCommandIdConflictError like the v1 path.

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

```

## Parents

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

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