---
title: "Validation and Product/QA handoff"
description: "Quartz UI 0.57.0-dev: Validation and Product/QA handoff. Source-reviewed guidance, usage and limitations."
status: approved
visibility: public
sourceRevision: fe5b709ec900e282b50e58b819a25041945005f9
reviewedAt: 2026-09-24
---

# Validation and Product/QA handoff

> **0.57.0-dev · beta source documentation.** Native, Blueprint, Editor and rendering examples are source-reviewed, not executed in Unreal during this scan. See [validation and limits](https://betterbuilt.games/docs/quartz-ui/evidence).

Machine: **DESTROYER**. Source: **fe5b709ec900e282b50e58b819a25041945005f9**, present on fetched `origin/main`. Descriptor: **0.57.0-dev**. Inspection date: **2026-09-24**. Plugin source remained unchanged; this is an attached documentation deliverable, not a plugin code release or website deployment.

## Executed checks

| Check | Result and scope |
|---|---|
| `Scripts/ValidateRepository.ps1` | Passed; descriptor/layout/docs-link hygiene, 284 source files at initial run |
| Six `Resources/Client/*.test.mjs` files, executed directly with Node | 19 passed: Back 3, clock 2, transport 8, React store 2, backdrop 2, textures 2 |
| `python -m unittest discover -s Scripts -p 'test_*.py'` | 7 passed: texture bake 4, skill-link filesystem 3 |
| `build_inventory.py` | 70 public headers, 263 defined types/delegates, 28 core messages, all 284 tracked files hashed |
| `verify_examples.mjs` | Executes extracted Markdown starter, Back ordering, sound/announcement calls and build-manifest snippet against actual shipped modules with a fake gateway |
| Package links and source provenance | Local Markdown targets/anchors and pinned source paths checked; tracked hashes must match exact source revision |

Node is v20.19.2; Python is 3.12.1. Windows Node did not expand a literal test wildcard; explicit `node --test` file enumeration then hit `spawn EPERM` because isolated child processes were unavailable. Running each test module directly completed all 19 tests without isolation. No permission change was required. Python tests use synthetic exporter/PNG data; React-store tests do not mount React.

Evidence output and deterministic verifiers accompany the archive. The examples checker validates JavaScript syntax/behavior with mocks; it cannot establish native acceptance, asset cook, Chromium rendering, or hardware input.

## Available toolchain and unexecuted gates

Installed Unreal Build.version reports **5.8.1**, changelist **56057345**, branch `++UE5+Release-5.8`. Visual Studio 2022 Community with the C++ tools component is discoverable. No matching UnrealEditor/MSBuild/cl process was found during the initial activity check. No shared Editor or build was started or disrupted.

This standalone repository contains no `.uproject` or `.Target.cs`; no task-owned host was supplied. **No Unreal build, UHT compilation, native Automation, PIE playtest, package, GPU test, real texture export, or React component build was run.** Native C++/Blueprint/editor examples are signature/source-reviewed only. Upstream historical test claims were not reclassified as current results.

## Product integration

Use the seven numbered Markdown guides as the primary docs navigation. Add a version badge with the exact source revision and beta status. Keep the inventory searchable; expose the large declaration snapshots as advanced reference. Preserve practical limitations beside the relevant feature. Do not turn unavailable sibling integrations into product capabilities or publish historical benchmark values as current guarantees.

The archive is self-contained for publication; the original source links require repository access. `source-manifest.json` includes pinned URLs and content hashes. For another machine to verify source, fetch the existing repository and check out `fe5b709ec900e282b50e58b819a25041945005f9`; confirm `git rev-parse HEAD` before running checks. Do not assume Destroyer's local checkout or engine installation is shared. The helper scripts expect this package beside a `prismui` source directory; documentation pages themselves use portable relative links.

## Manual host acceptance checklist

1. Use a task-owned C++ UE 5.8 host and the exact pinned plugin; build its Editor target. Record machine, engine changelist, host revision, plugin revision and output.
2. Follow guide 01 literally. Generate `gameui` contract, build static output and manifest, create/select the asset, start Manual shell, publish ammo 30. Pass: visible page says Connected and 30, and native Is UI Ready is true.
3. Change one app schema without rebuilding the frontend. Pass: honest contract/readiness failure, no stale endpoint authority. Regenerate/rebuild/save/recook and recover.
4. Check action registration/unregistration, provider activation/replacement, typed request success/failure/cancel, one-client ownership and cleanup. Navigate and travel; retained state replays, stale transient work does not.
5. Run two local players. Pass: correct shells, layers, input/glyphs, providers, GAS and sound stay isolated; unspecified ambiguous player calls fail. Remove one player and verify complete cleanup.
6. Verify keyboard/text/IME, controller semantic focus/edit/Back ordering, pointer regions, reduced motion/high contrast and culture. Document physical-device/OS coverage. Do not call announcement-only support full screen-reader traversal.
7. Run RHI texture pixel/alpha tests and backdrop enabled/disabled comparisons. Check direct-surface transform/raster independence, suspension, resize/reload/travel and repeated create/close. Keep D3D11 qualification separate from D3D12.
8. Run Shipping audit, package Development and Shipping clients, verify UFS resources without a dev server, current identities, no loose fallback, and required notices. Native automation and GUI checks supplement each other.

Main risks for QA: contract drift, exact-player lifetime/input leakage, stale callbacks across travel, mistaken shipped-vs-external claims, asynchronous render/texture consistency, and UFS metadata/file admission. Any confirmed regression should name a reproducible host/source revision; this guide package changes no runtime behavior.

## Source provenance

Source paths in these guides refer to revision `fe5b709ec900e282b50e58b819a25041945005f9`. Repository access is restricted; resolve these paths in your authorized checkout. Maintainers retain the original package hashes, source-file hashes and publication mapping in `Docs/BB-54/coverage.json` in the website repository. No private repository access is implied by this public documentation.

Canonical HTML: https://betterbuilt.games/docs/quartz-ui/evidence