# fix\(orchestration\): promoted queued messages keep the queued_turn intent · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 25e0ed3d6fda88cd5fe3ce8cf1f9dd5a571c3e94

Requested commit: 25e0ed3d6fda88cd5fe3ce8cf1f9dd5a571c3e94

Commit: 25e0ed3d6fda88cd5fe3ce8cf1f9dd5a571c3e94

Tree: 01531ddc718cddd9c49e91fdd42a42080f13fb4a

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(orchestration): promoted queued messages keep the queued_turn intent

The turn item materialized when a queued run is promoted was emitted
with inputIntent "turn_start", but the deterministic replay driver (and
the recorded queued_turn fixtures) expect "queued_turn" — the mismatch
stalled replay before the queued run could start, leaving run 1 waiting
and run 2 queued forever in all five queued_turn fixtures.

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

```

## Parents

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

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