764 B
764 B
Atomic update and rollback
- Read and validate manifest.
- Copy/download into a new staging directory with cancellation and bounded parallelism.
- Validate file length, SHA-256, required files, entry metadata and forbidden DLLs.
- Write local manifest, close streams and rename staging to
versions/<version>. - Atomically replace
current.json; preserve prior pointer. - 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.