Versions, compatibility and validation limits
Record a commit pair, not just the descriptor's 0.57.0-dev. Both the published baseline and later repair candidate use that same version label.
| Revision | Meaning and evidence |
|---|---|
Host 91fd772c282098157c4e7cded0263844f076e9fb | Private reference-host baseline used for installation. |
Plugin 933db5171161ac5966e3b9bca3fd3a965f5399cc | Reference-host gitlink; earlier independent testing passed rendering/readiness and reproduced native inspector Origin failure. |
Plugin acfea46445f8400e19181d580df9c9844ec6cd84 | Earlier repair candidate with independent attachment, preview and multi-page evidence; direct viewport clicks activated app controls. |
Plugin e7ab5dcc0069ade3393cc0e033e4541a78eaae3b | Later repair candidate with two viewport defects independently resolved. Physical captured-mouse Shift+F1 remains unverified. Not presented as a release or reference-host pin. |
The documentation review found no source changes in the runtime subtree, web client or contract commandlet between the baseline and later candidate. This establishes source equivalence in those paths, not universal behavioral equivalence.
Tested environment versus support
The demonstrated configuration is Windows Win64 Development Editor, UE 5.8.0 AS, D3D11. The standalone host descriptor declares Windows, while the plugin descriptor does not define a comprehensive platform allowlist. Neither that absence nor an available source module establishes Linux, macOS, mobile, console, stock Epic UE, other engine versions or other rendering backends as supported.
QuartzUIRuntime and QuartzUIGAS are ClientOnly; QuartzUIEditor is Editor; QuartzUITests is an Editor-allowed DeveloperTool. GAS is optional and its module has LoadingPhase=None. Do not add runtime browser/UI code to a dedicated-server dependency as if the browser were available there. The minimal reference host contains no AngelScript gameplay even though its tested engine is the AS fork.
Naming and migration
Use Quartz UI as the product name. Technical names are QuartzUI.uplugin, Plugins/QuartzUI, QuartzUIRuntime, UQuartzUIAppAsset, FQuartzUI and the quartzui web gateway/origin namespace.
The rename from legacy PrismUI/WebUIUnreal identities added serialized redirects; historical developer evidence includes migration through Unreal asset tools. This is not permission to rename binary assets in a text editor or assume every old installation upgrades automatically. Consult the exact plugin Documentation/QuartzUIMigration.md and test a project's assets and contracts against its selected revision. Keep generated app identities aligned with native code.
Evidence ledger
| Gate | What the evidence establishes |
|---|---|
| Earlier independent baseline testing | Exact-commit retrieval, LFS integrity, real gitlink, incremental Editor build with zero compile actions, audit of one app / seven files / zero issues, eight focused tests, rendered reference and readiness. Native inspector failed. |
| Earlier developer testing | Full reference-host compilation and a fresh recursive clone; not repeated by the independent documentation review. |
| Earlier independent candidate testing | Scoped viewport/preview/lifecycle checks, incremental build, six adapter tests and two DevTools automation tests at e7ab5dcc. Physical keyboard release and prior-revision multi-page qualifications remain. |
| Independent documentation review | Reused exact checkout, helper flags, asset hash/resources and unchanged integration source verified; existing client/React-store tests passed 10/10. Fresh clone and new remote LFS hydration were not repeated. |
| Reader build and first render | Not repeated by the documentation review: its exact-baseline checkout lacked host/plugin build artifacts. Earlier rendering evidence remains separate. |
| Custom integration example | Source-defined API names/payloads checked. App registration, frontend build/import/manifest recipe and observable native-action/lifecycle fixture are incomplete. No compiled C++, Blueprint graph, Score: 42 or native action outcome is claimed. |
Packaging and compatibility gaps
No cooked Development/Shipping executable was built or run in the cited baseline or documentation review. Source-level app auditing and cook integration do not establish a working package. No verified packaging sequence is offered here.
Packaging, offline packaged operation, clean-machine provisioning, stock Epic UE, other engine versions, other platforms and broader browser coverage remain unverified. A passing Shipping-policy resource audit is not a packaged-runtime pass. Version-specific tooling details are in debugging; the existing reference-app workflow is in installation.