A missing timing field in a stream event can no longer crash a headless turn.
What's wrong with this entry?
The headless turn loop now checks that timing fields exist on a stream event before reading them for time-to-request metrics, so a missing field cannot throw mid-turn. Structured-output telemetry and the max-retries error path are otherwise unchanged.
tengu_structured_output_retraction_exhausted
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Headless text output recovers the last full assistant message on an incomplete run
Both mention headless mode
-
v2.1.246
Non-interactive runs retry a response that was cut off mid-stream
Both mention headless mode
-
v2.1.246
Headless idle detection now waits for background tasks and undelivered notifications
Both mention headless mode