Installation updates and client preparation

Core owns one shared installation-update operation. API access to updates is separate from project/settings access and from plugin execution trust.

Review and stage

Use updates.read to inspect the installation and operation. With updates.manage, check approved sources, inspect supported legacy packages, and plan the complete compatible component set.

Display required components, publisher evidence, unsigned-package acknowledgements and new permissions. Approval binds the exact plan and current operation/registry revision; changing the plan invalidates old consent.

Poll package progress and operation state. An accepted command is not the same as a completed installation. After an uncertain update response, recover the original command through the update lookup rather than repeating a new POST.

Prepare a native client

updates.prepare permits registration and readiness responses; it does not grant update-management authority. Use ApiUpdateParticipant with callbacks that durably preserve supported drafts, freeze edits and handle release/close requests.

Respond only to the exact Host/operation/preparation/plan/client round. A readiness receipt is not a request to upload draft contents or local checkpoint paths. Refusal, expiry, unsupported drafts or Save failure can postpone installation.

Approved installation can continue after prepared clients close. Reconnect to the new Host and read the recorded outcome; do not reuse old sessions or command cursors.

See User update recovery.