Repository navigation
Release testing
The development line is v10.5.4-NEXUS. A release must not be described as stable solely because CI is green.
Before publishing a test package:
- build the .muxapp with only one top-level Void-Desk/ folder;
- run
python3 tools/validate_muxapp.py path/to/VoidDesk.muxappand fix every reported error; - install it through Archive Manager on MustardOS 2606.0 Andromeda;
- confirm startup, controller navigation and shutdown;
- verify the Bluetooth panel and NEXUS animation together;
- test optional XFCE hand-off only if there is enough storage and network;
- test Pygame on target hardware; LÖVE remains experimental.
Include QWASAR Desk version or commit, exact device model, MustardOS/muOS build, frontend (py or love), screen and selected action, reproduction steps, expected and actual behaviour, and relevant log lines or screenshot. Redact credentials, Wi-Fi names, private IPs, hostnames, tokens and personal filenames.
Do not close hardware issues until the reporter has verified the behaviour on the affected handheld.
The public product identity is QWASAR Desk. The current release and installable package still use the legacy Void Desk identifiers. Do not infer a new package/release name until the migration is published and tested.