The code that withdraws a half-printed reply and shows a refusal banner was reorganized; nothing looks different.
What's wrong with this entry?
The logic that withdraws a partially printed response, handles a stale stream restart and swaps in a refusal banner was pulled out of the print loop into a reusable unit whose handlers swallow and log their own errors. The events emitted and the telemetry reported are unchanged.
- Telemetry still reports
tengu_partial_stream_retraction_closedwith sources including a stale stream start and a refusal banner. - When streaming events are not requested, the whole thing is a do-nothing object.
tengu_partial_stream_retraction_closed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.