Updates & recovery
Preserve your installation and prove the updated runtime is healthy.
Update a current installation
Use the supported updater in the owning checkout. Existing owner configuration and private state are preserved. A successful fetch alone does not prove the runtime was deployed.
mso update status
mso update
mso doctorUpgrade an older installation
If your installed version predates mso update, rerun the current canonical installer. It detects an owned active service checkout and upgrades in place. Without a service, use the known checkout via the installer’s documented --dir flag.
Do not create another clone beside an owned installation. The installer refuses dirty/diverged source rather than discard local work.
Return to the canonical installer →If the update fails
Inspect status and the updater transcript. Re-running mso update retries supported recovery work. Keep private update-state receipts and existing source changes intact.
mso update status
mso update logRollback needs the full procedure
Use the current install reference for rollback, backup and service activation. Version changes can affect runtime/state compatibility; do not replace the live .next directory or reset Git from a generic snippet.
Read the full update and rollback reference →These guides orient you; use the runtime reference for complete flags and operational procedures.
Read docs/INSTALL.md on GitHub ↗Reviewed against source 5c4f136a.