Use this page when an Installer run leaves temporary package files, staging folders, or failure artifacts behind. Cleanup protects the workspace without rewriting lifecycle truth.
Installer owns temporary package workspace cleanup. It does not own permanent lifecycle cleanup truth.
After successful deployment and result handoff, Installer should remove temporary upload copies, extracted staging folders, and transient execution artifacts that are not intentionally retained.
After failure, Installer may retain minimal diagnostics according to configured retention. It must remove unsafe or executable staging debris when retention is not required.
Installer execution history is non-authoritative. Retention options may include forever, 90 days, 30 days, 7 days, and manual purge.
system governance lifecycle history remains the permanent authority.
After first-run install succeeds, `/install` and `addons/*/bootstrap/` may be removed. If retained, they are inert and must not become runtime fallback paths.
See Addon Update vs Clean Install and Package Install and Update Flow.
Updated: 2026-05-07 02:18:09