Background task output files move more safely and now report failures instead of hiding them.
What's wrong with this entry?
When a background task's output file resolves outside the expected directory and has to be moved back into it, the copy now refuses to follow symlinks, refuses to overwrite an existing file, verifies the file identity before and after, and copies in bounded chunks. If anything goes wrong after the initial safety check the operation now fails with a clear reroot error instead of silently swallowing it.
- Applies to background and bash task output-path handling, with no gate.
reroot failed after the gate
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.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task