Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/integrations/api.md
Original file line number Diff line number Diff line change
Expand Up @@ -344,7 +344,12 @@ code.

Failed lifecycle operations restore their own tracked changes while preserving
unrelated files, workflow progress, and conflicting external edits. Recovery
failures report retained snapshots for manual recovery. Upgrade and uninstall
failures report retained snapshots for manual recovery. Individual files the
operation rewrote in place are restored in place; replaced or removed files,
and directories, are recreated from their snapshots. A file whose bytes are
restored without all of its metadata (mode, times, extended attributes, or BSD
file flags) is reported with its snapshots retained; see the
[shared CLI reference](cli.md#upgrade-an-integration). Upgrade and uninstall
preserve modified generated files unless forced; forced recovery still needs
local ownership proof to delete old files and does not bypass catalog policy
or replacement-package trust.
Expand Down
10 changes: 9 additions & 1 deletion docs/integrations/cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -295,7 +295,15 @@ Recovery does not bypass catalog policy or replacement-package trust.

Failed operations roll back their own changes, not unrelated user files or
workflow progress. Conflicting concurrent edits are reported with recovery
snapshots retained. Adapter authors should follow the
snapshots retained. A file the operation rewrote in place gets its original
bytes back in that same file, so it keeps its owner, hard links and Windows
access-control list, and its mode, times, user extended attributes and POSIX
access ACL are set back where the platform allows it safely. If some of that
metadata does not come back, or the file is replaced while its bytes are being
restored, the file is reported as not fully restored, with recovery snapshots
retained. A file the operation replaced or removed, one rollback
cannot safely identify as the original, and a directory are recreated from
their snapshots instead. Adapter authors should follow the
[setup and file ownership contract](api.md#setup-and-file-ownership)
and [lifecycle guarantees](api.md#external-adapter-lifecycle-guarantees) for safe writes and recovery.

Expand Down
Loading