{"version":"2.1.251","anchor":"background-task-output-files-copied-more-safely-and-failures","canonical_anchor":"background-task-output-files-copied-more-safely-and-failures","heading":"Background task output files copied more safely, and failures now surface","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/background-task-output-files-copied-more-safely-and-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Background task output files copied more safely, and failures now surface\n\nBackground task output files move more safely and now report failures instead of hiding them.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Applies to background and bash task output-path handling, with no gate.\n\n**Evidence**\n\n`reroot failed after the gate`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}