Interrupted Export Recovery

Deputy Shell builds and verifies a workspace export in its own private storage first, then copies that finished archive to the destination you picked — because not every Android storage provider (cloud drives especially) guarantees that a copy either fully completes or leaves no trace.

If the copy step is interrupted

If Deputy Shell is closed, crashes, or the destination copy otherwise fails to finish, the next time you open the app you'll see a "Finish workspace export" dialog with three choices:

• Choose another destination — retries the copy from the still-valid private archive to a new location.
• Discard export — deletes the private archive and attempts to clean up the incomplete file at the original destination, if it's still reachable.
• Later — keeps the private archive and hides the dialog for your current session only; it reappears the next time you open the app.

If the private archive itself turns out to be missing, incomplete, or fails its own integrity check, "Choose another destination" and "Later" aren't offered — only Discard is available, since there's nothing valid left to retry from.

Current limitation

This recovery flow has been validated through automated crash-simulation testing, but full manual testing across every real storage provider (different cloud-drive apps, forced app termination at different exact moments, device reboots mid-copy) is still in progress. If you hit unexpected behavior during an export, exporting to local device storage first (rather than directly to a cloud-drive provider) is the more thoroughly-tested path.