Nix has two responsibilities in the cua-driver test stack: reproducible Linux builds and desktop-session dependencies for the canonical Rust harnesses.
| Attribute | Purpose | CI |
|---|---|---|
cua-driver-build |
Build the shipped Linux package from the locked Rust source | ci-nix-linux.yml |
cua-driver-linux-rust-unit |
Compile and run the source-owned headless Rust tests | ci-nix-linux.yml |
cua-driver-policy-yaml |
Run YAML permission-policy MCP checks in a NixOS VM | Flake check |
cua-driver-policy-rego |
Run embedded Rego permission-policy MCP checks in a NixOS VM | Flake check |
cua-driver-wayland-e2e |
Provide the Sway, GTK, WebKit, Chromium, Electron, capture, and Rust toolchain used by native Wayland E2E | e2e-rust-linux-wayland.yml |
cua-driver-inject-e2e |
Provide the same typed harness toolchain plus the nested cua-compositor package |
Experimental nested-injection workflow |
cua-compositor-build |
Build the optional compositor-owned injection backend against pinned wlroots | Flake check |
The Rust tests own all protocol and desktop behavior. The old NixOS Python clients, GIF scenarios, real-app smoke rows, and compositor matrix were removed because they maintained a second scenario catalog with different assertions. The canonical Rust matrix is the coverage source of truth; retired rows are not treated as equivalent unless a current typed case proves the same contract.
Run the native Wayland matrix from the repository root:
nix develop .#cua-driver-wayland-e2e -c \
scripts/ci/linux/run-rust-e2e-wayland.shThe wrapper starts a pure Wayland Sway session with Xwayland disabled, then
calls the same canonical Rust runner used by X11. Results use the common typed
JSONL schema and retain MP4 trajectories under artifacts/cua-driver/linux/.