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

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

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

Visibility: public

Requested revision: adf137f59be50dc824ee80ad414da9d16f79c090

Requested commit: adf137f59be50dc824ee80ad414da9d16f79c090

Commit: adf137f59be50dc824ee80ad414da9d16f79c090

Tree: 1269c1e311c1fbb4d8ce8289a0188f887dffa513

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

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

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