#Deploy and Live Update

A miniapp deployment has two layers:

1. an immutable package release produced by your build; and
2. a logical tag or environment that selects one verified release.

The AI Platform follows the logical selection while retaining the immutable identity it verified. A new selection activates in a fresh realm; a failed candidate does not replace the last known good release.

#Publish Once to Create the Application

Configure the supported Zephyr Cloud integration for the build that produces the assembled dist directory, then run one authenticated build. That first publication creates or discovers the application record and makes it available in the Zephyr Cloud UI. Use identifiers assigned to your organization rather than copying another publisher's values.

Follow the current Zephyr Cloud documentation for authenticating the build and enabling its supported Rspack or Rslib integration. Confirm the organization, project, application, immutable version, and source revision after the build finishes.

Authentication is owned by the developer or CI environment. Do not put credentials, sign-in links, or local session data in the repository.

#Establish Development and Production Environments

Keep development publication and production selection in the same Zephyr Cloud application and control plane. After the first publication appears:

1. Create an unlocked dev tag that authorized main-branch builds may advance.
2. Create an unlocked development environment that follows dev.
3. Create a locked production environment and pin it to an exact immutable version.

Production has no authoritative prod tag. Main builds may advance dev and therefore development; they cannot move the manually pinned production environment.

#Follow Development from TAP

1. Open Settings → Miniapps in The AI Platform.
2. Choose the Zephyr Cloud installation source.
3. Select your organization, project, application, and development environment.
4. Enable Follow updates, then choose Next launch or OTA activation.
5. Review the requested permissions and install or enable the miniapp.
6. Open its surface and confirm the displayed package and release identity.

The selector is logical, but the installation record also retains the exact resolved version, snapshot, descriptor, and integrity identity.

#Publish a Visible Change

Change a visible string or behavior, then run the application-local build configured for development publication:

pnpm build

Confirm in Zephyr Cloud that:

• a new immutable release exists;
• the authorized dev tag resolves to that release;
• the development environment resolves through the dev tag; and
• the production environment still resolves to the previous tested release.

The AI Platform verifies the updated descriptor and asset graph before it activates anything. Next launch keeps the current release active until you restart the app. OTA prepares a fresh realm and swaps the visible contribution after activation succeeds, without restarting the app. Host-managed Code and Browser use next-launch activation.

Compatible state is restored through the declared lifecycle contract. Browser storage tied to an outgoing realm is not a portable state mechanism.

#Pin Production

Pin the exact immutable development release that passed validation. Do not rebuild or copy it through another control plane.

1. Open the application in the Zephyr Cloud UI.
2. Open its production environment.
3. Select the intended immutable version and save the exact version pin.
4. Confirm production resolves to the recorded version ID, snapshot ID, and content digest.
5. Verify production from a separate installation or test profile.

#Roll Back

Pin the production environment back to a previously verified immutable release. A followed The AI Platform installation resolves the earlier release and performs the same fresh-realm activation path. For development rollback, move the dev tag instead.

If a candidate fails descriptor, integrity, compatibility, import, mount, or state restoration checks, The AI Platform retains the last known good release and reports an activation error. Correct the release or select a previous one; do not ask users to clear unrelated application data.

#Publication Evidence

For your own release process, retain a sanitized record of the package ID, immutable release and snapshot, content digest, source revision, selected environment, development tag when applicable, readiness result, and timestamp. Never include credentials or private authentication URLs.