Under the hood
Assistant transcript entries now explicitly store a request_id alongside error, uuid, and timestamp
What
The internal code that builds each assistant message entry in a conversation transcript was rewritten to explicitly set its fields: type, message, uuid, timestamp, error, and, when available, request_id. Previously this was built by copying the whole input object and only removing one field; now each field is set directly.
Why
This makes transcript entries carry a clear, explicit request_id when one exists, which is useful for tracing a given assistant message back to the specific request that produced it, rather than relying on whatever happened to be present in the original object.