11 lines
764 B
Markdown
11 lines
764 B
Markdown
# Atomic update and rollback
|
|
|
|
1. Read and validate manifest.
|
|
2. Copy/download into a new staging directory with cancellation and bounded parallelism.
|
|
3. Validate file length, SHA-256, required files, entry metadata and forbidden DLLs.
|
|
4. Write local manifest, close streams and rename staging to `versions/<version>`.
|
|
5. Atomically replace `current.json`; preserve prior pointer.
|
|
6. On bootstrap failure, offer rollback by atomically restoring the prior pointer.
|
|
|
|
Never update an active directory in place. Locked files leave the current version intact and yield a diagnostic status. Network failure uses the last valid local version; when none exists, policy is to launch Plant without the corporate plugin or offer Legacy fallback, never a partial Next package.
|