{"version":"2.1.265","anchor":"turn-stream-user-message-uuid-stamping-extended-for-mid-turn","canonical_anchor":"turn-stream-user-message-uuid-stamping-extended-for-mid-turn","heading":"SDK stream-json schema gains historical and runner_exit fields, plus expanded meta-turn uuid stamping","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/turn-stream-user-message-uuid-stamping-extended-for-mid-turn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### SDK stream-json schema gains historical and runner_exit fields, plus expanded meta-turn uuid stamping\n\nThe SDK's streaming message schema adds historical\/runner_exit fields and documents how meta-turns stamp folded-in user messages\n\n**What**\n\n- Message schema gains an internal `historical` boolean field, stamped by the Remote Control bridge on messages it flushes to the session server, and by the server on deliveries it replays.\n\n- A new `runner_exit` field is set by the self-hosted runner when a session process fails to start or exits abnormally.\n\n- Documentation for `user_message_uuid`\/`user_message_uuids` (across turn, error-result, and thinking_tokens frames) was expanded: a turn started by a synthetic\/scheduled (meta) prompt can now stamp a later, non-ping stream event when a queued user message is folded into the turn mid-stream, in addition to the turn's first stream event. A turn started by a typed prompt still stamps only its first event.\n\n**Why** These are schema and documentation additions for SDK consumers: `historical` and `runner_exit` give more visibility into replayed messages and runner failures, and the clarified uuid-stamping rules help SDK clients correctly match stream events to the user message that triggered them, including when a message is folded into an already-running turn.\n\n- Area: SDK\n- Names: `user_message_uuid`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}