The launch.sh/launch.bat launchers were hardened (prefer the venv / $PYTHON, dep-check with a pip install -e . hint before starting the GUI, run a built bundle if present). launch.sh is verified on Linux; launch.bat has only been reviewed, never run on Windows (no Windows box during development).
Now that the prebuilt .exe from Releases is the primary Windows path this is low priority, but the source-run launcher should be smoke-tested on real Windows:
- fresh clone, no venv, deps missing -> should print the install hint and exit 1 (NOT a Python traceback)
- deps installed -> should launch the GUI
The
launch.sh/launch.batlaunchers were hardened (prefer the venv / $PYTHON, dep-check with apip install -e .hint before starting the GUI, run a built bundle if present).launch.shis verified on Linux;launch.bathas only been reviewed, never run on Windows (no Windows box during development).Now that the prebuilt
.exefrom Releases is the primary Windows path this is low priority, but the source-run launcher should be smoke-tested on real Windows: