# LGUI Acceptance Baseline
The runtime contract requires component-local State invalidation, stale-handle rejection,
post-present Effects and cleanup, lazy Application-scoped Stores, selector equality, batched Store
updates, declarative Router history/outlets, shared multi-window Context, owner restoration, and a
single Application API for Skia rendering.
The acceptance suite is:
```powershell
cargo check -p lgui --no-default-features
cargo check -p lgui --no-default-features --features backend-winit
cargo check -p lgui --no-default-features --features notifications,tray
cargo check -p lgui --no-default-features --features backend-winit,notifications-win32,tray-win32
cargo test -p lgui --no-default-features --quiet
cargo test -p lgui --no-default-features --features images,persistent-cache --quiet
cargo test -p lgui --no-default-features --features renderer-skia --quiet
cargo test -p lgui --no-default-features --features backend-winit --quiet
cargo test -p lgui --quiet
cargo test -p lgui --all-features --quiet
cargo check -p liugc --bin liugc --features diagnostics-runtime
cargo test -p liugc --bin liugc frontend:: --quiet
cargo test -p liugc --bin liugc backend::settings::storage::tests:: --quiet
cargo check -p lgui-showcase --all-features
cargo fmt --all -- --check
git diff --check
```
Backend-wide tests are outside this GUI boundary and are not part of this baseline. Hardware FPS
is not a portable threshold; performance comparisons must use the same page, viewport, renderer,
DPI, build profile, and input sequence.
Memory acceptance uses fixed inputs on the Skia backend. Exercise cold login,
avatar loading, the Store list, route round trips, dialogs, theme/scale changes, simultaneous
windows, hide/restore, and device recovery. Capture `MemorySnapshot`, working set, private bytes,
and available GPU memory after warm-up, at the operation peak, after leaving the page, after all
windows are hidden, and after restore. Repeated churn must settle below the application's configured
policy after owner-thread Trim work drains; visible pinned bytes may exceed a cache share but must
be reported as pinned overflow rather than silently discarded.
Release acceptance also verifies that the embedded Windows `client.toml` requires a fixed memory
profile, persistent-cache choice, and disk quota; startup applies that configuration without adding
memory controls to user Settings. `memory.snapshot`/`memory.trim` must work with diagnostics enabled,
and no native resource may be dropped outside its owning UI thread. Architecture tests must reject
framework-owned profiles, implicit `MemoryOptions` defaults, domain weights, and any application path
that reaches `run` without explicit memory options. Focused tests must preserve exact application
domain budgets, including zero, and prove that lifecycle and default-image policy come from the
application.