[Bug]: Linux/Hyprland desktop exits silently with no crash diagnostics

Before submitting

• I searched existing issues and did not find a duplicate of this specific failure.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Launch T3 Code from the desktop under Hyprland/Wayland.
2. Use the app normally. The exact interaction immediately preceding the failure is unknown.
3. The desktop window/process disappears; launching T3 Code again restores access.

This was observed once so far and is not yet deterministic.

Expected behavior

The desktop app should remain open. If it has to exit, it should leave a visible error and a useful crash/exit diagnostic.

Actual behavior

The T3 Code desktop process disappeared unexpectedly. The prior app scope started at 2026-09-09 10:55:34 CEST, and the next launch occurred at 11:02:38 CEST. The replacement process is running normally now.

Impact

Major degradation or frequent failure

Version or commit

t3code-bin 0.0.38-1 (installed 2026-09-09 10:34 CEST)

Environment

Arch Linux x86_64, kernel 7.1.9-arch1-2
Hyprland 0.56.2, Wayland
Electron desktop launched with --ozone-platform=wayland
Intel UHD 630 + NVIDIA GeForce GTX 1050 Ti Mobile
Mesa 26.2.1

Logs or stack traces

# journalctl --user
2026-09-09 10:55:34.535443 CEST systemd[953]: Started app-t3code-87926.scope.
2026-09-09 11:02:38.906517 CEST uwsm_app-daemon[1445]: received: app -- gtk-launch t3code.desktop
2026-09-09 11:02:38.906517 CEST uwsm_app-daemon[1445]: sent: exec systemd-run --user --scope --slice=app-graphical.slice '--unit=app-Hyprland-gtk\\x2dlaunch-cf8add58.scope' --description=gtk-launch --quiet --collect --same-dir -- gtk-launch t3code.desktop
2026-09-09 11:02:39.902160 CEST systemd[953]: Started app-t3code-105259.scope.

# systemd scope state for the exited app
Id=app-t3code-87926.scope
ActiveState=inactive
SubState=dead
Result=success

# checks performed
- coredumpctl list: no entry for /usr/lib/t3code/t3code
- no OOM-killer event in the kernel/user journal
- no T3 Code Crashpad dump was present; only Crashpad/client_id existed
- free -h at investigation time: 31 GiB total, 22 GiB available

The available evidence confirms an unexpected process exit/relaunch, but does not identify whether the cause was an application-level exit, Electron/Wayland failure, or another external termination.

Workaround

Relaunching T3 Code restored the app.

Start in apps/desktop and reproduce the unexpected exit under Hyprland/Wayland using the reported t3code-bin 0.0.38-1 environment. Review the user journal, systemd scope state, coredumpctl output, and Crashpad evidence described in the issue. Done means an unexpected exit leaves a visible error and useful crash or exit diagnostics, with the behavior verified after relaunching the desktop app.