System Updates

The manager TCP API exposes a two-step manual update flow:

1. Call MngGetSystemUpdates to display published versions newer than the server currently running and the cumulative release notes between them.
2. A SuperAdmin may call MngInstallSystemUpdate with one of the returned versions.

Update information is platform-wide and is not scoped by brand. Viewing it does not grant permission to install an update.

Only releases explicitly published in the release registry with release: true are returned or accepted for installation. Draft releases and debug-symbol packages are not exposed through these API methods.

The installation request starts the updater asynchronously. A successful TCP response confirms that the updater process was accepted and launched; it does not confirm that service replacement, restart, health verification or rollback has already completed.

When status reporting is enabled, the accepted response contains a temporary TCP port and per-update credentials. BackOffice switches to that port while the main process is unavailable, polls GetUpdateStatus, and returns to the normal platform port after a terminal state.