Test plan and reproducibility

The UI tests explain presentation correctness; they do not replace a real no-target-install acceptance run.

State model

Materialization precedes delivery, delivery precedes activation, and the task begins last. Unknown critical booleans are treated as unsatisfied. Missing resources, incompatible architecture, failed verification, target-side install requirements and activation requirements must all block ready-for-task.

Browser behavior

The complete story must work without clicking, reverse scroll must be deterministic, film controls must pause and resume, hidden/offscreen states should not animate indefinitely, keyboard interactions must not be hijacked, and reduced-motion must preserve content.

Real boundary test

For a strict acceptance run, separately record preparation logs, target baseline, network/process traces, denied dependency-source access and actual application results. UI state alone cannot prove the boundary.