Juntai Application UI

Versioned Console contributor for application metadata, release review, and deployment execution. The package owns presentation and disposable page-local state only; every direct entry and retry reads current data through the released generated service clients.

Consumer setup

import applicationModule from "@zephytiju/juntai-application-ui";
import "@zephytiju/juntai-design-system/styles.css";
import "@zephytiju/juntai-application-ui/styles.css";

consoleHost.register(applicationModule);

The synchronous registration is network-free. Every page loader resolves a default React component. Cross-domain navigation passes identifiers only: applicationId, applicationVersionId, and an authorized contribution routeKey.

Sealed versions can open the deployment workspace. It submits only the application/version identifiers, target identifier, and PREVIEW/APPLY/REMOVE operation. Target discovery, execution polling, cancellation, logs, evidence, and trace data remain bounded by the public deployment contract.

Verification

Run npm run verify with Node 24.14 or newer.

Exact version selection (1.2.0)

Console SDK 2.2.0 and host contract 1.1 are required. Start the existing application.versions page with applicationVersionSelectionTarget(applicationId, returnTarget). The public helper emits selectionContract=application-version-selection.v1 and one canonical returnTarget query value. Console encodes it once.

The return target must retain the same applicationId in its route parameters, with no incoming applicationVersionId or selectionResult. Other source identifiers are opaque. Application reads its authorized application and all version pages, selects nothing automatically, and reads the exact OPEN version again immediately before returning. A successful return adds selectionResult=selected and the service-returned applicationVersionId; cancellation adds only selectionResult=cancelled. The receiving domain must refetch its own authority.

Create and use sends one generated-client command with an Idempotency-Key. A private per-tab guard, scoped to tenant, principal and application, survives reload without retaining a command key or payload. Unknown outcomes prevent another create; an authorized list can support a later explicit exact selection. Known created IDs support safe read-and-return recovery. Neither path replays a create. The navigation target remains reconstructable from the URL alone.

An OPEN version offers all installed platform.application.configure providers before any contributions exist. Users choose a provider explicitly. These pages accept the exact application and version as declared route parameters or scalar query values, plus a serialized return to application.version. Missing catalog, missing destination, incompatible parameters and authority failures stay visible.