Appliances Validation

Validation · OCR Extract v2.5.0

A Passed run against the current fingerprint is required to publish.

Fingerprint

a91f…c4d2

current draft

Run status

Running

leased by worker-3

Checks

14 / 16

2 pending

Validation runs

Run #3 — in progress

a91f…c4d2 · now

Image scan, manifest checks, endpoint probes.

Run #2 — Passed

77b0…19ac · Jun 30

Superseded by fingerprint change.

Run #1 — Failed

2e5c…88f1 · Jun 28

SBOM reference unreachable.

About this page

The automated checks a version must clear before release: structure, declared contacts, resource claims, contract consistency. Like the AI test gate, the block is enforced by the system — a failing version cannot be published.

Behind this page/appliances/versions/:packageVersionId/validation · CanManageAppliances

Retrieve

Runs read from the validation-run records keyed by fingerprint; status polled to completion.

Save

Queue → sp_ApplianceValidation_Queue; the pipeline lives in the Template Library, keyed by PackageVersionId + the exact ReleaseFingerprint; workers use sp_ApplianceValidation_Lease / _Complete / _Abort.

Success

Publishing needs a Passed run for the exact fingerprint.
Fingerprint change invalidates prior runs.
Lease/complete belong to the worker, not the browser.

CLI handoff

Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.

Page IDappliance-validation

Route/appliances/versions/:packageVersionId/validation

AccessCanManageAppliances

Statusworker-integration-required

Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.