Background job state read failures now report themselves once per job instead of silently falling back to a cache.
What's wrong with this entry?
A failed read of a background job's state now reports itself once per job before falling back to the cached copy, so intermittent storage problems are visible.
- fires on backend errors and on parse/read exceptions, and only if that job has not already reported
- the event carries the errno and whether a cached state existed
- oversized state files are skipped with a warning instead of being parsed
tengu_bg_state_read_transient
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.227
Deleting a background job keeps a directory a live session is sitting in
Both mention background
-
v2.1.248
claude logsno longer lets replayed output corrupt your terminalBoth mention background
-
v2.1.248
Job list offers "open" rather than "resume" for a job already attached to a terminal
Both mention background