Errors and stream events now echo the prompt id that started the turn.
What's wrong with this entry?
The error result message and the first non-ping stream event of a turn can both carry user_message_uuid, the client uuid of the prompt that started the turn, so a stream or a failure can be matched to its send immediately.
- The schema field is optional, so older producers simply omit it.
- Absent on meta and scheduled turns and on any turn submitted without a client uuid.
Client uuid of the user message that triggered this turn (submitMessage options.uuid), stamped on the turn's FIRST non-ping stream event only
Strings lifted out of the shipped bundle, so the claim above can be checked against them.