What
The writer that saves a background task's output now tracks whether it is failing, how many characters are still unwritten, and whether anything was lost. Repeated retry errors are logged once per class rather than every attempt, and past a threshold the queued output is dropped with an error naming exactly how many characters were discarded.
Details
- Retry errors are grouped as disk exhaustion or unexpected, so a full disk does not flood the log.
- A write that throws re-queues its marker instead of losing its place.
- When output is truncated for hitting the on-disk cap, the notice now replaces the chunk it truncates instead of being appended next to it.
Evidence
Task output still cannot be written
Strings lifted out of the shipped bundle, so the claim above can be checked against them.