Reported as 'this app dosent generate me the last few sentences': the audio comes back clean and simply short, so nothing in the product ever said a sentence had gone missing. #1360 added a log line, which records the bug for us and tells the user nothing.
The join now collects the text of every chunk the engine rendered to nothing, and both delivery paths carry it back — response headers on the classic path, a warning frame before done on the streaming one — announced through one shared helper so the two cannot drift, quoting the lost text, plural-aware, in all 21 locales. Deliberately a warning rather than a failure: the take is real and playable.
Both carriers are exercised rather than grepped: a real NDJSON body through the streaming client, and POST /generate with an engine that renders one chunk to nothing.
This does not fix the underlying cause (the engine returning empty audio for certain chunks, still unreproduced); it stops that cause from being invisible, and the quoted text is the reproduction input we have been asking reporters for.
Palash Debnath
d2eaee9fde