## What happened

Triggering Logout (menu > System > Logout) shows the "Logging out" OSD toast and closes all open windows, but the session never actually ends — Hyprland/uwsm stays up and the user is left at an empty desktop.

## Expected behavior

The compositor/session should stop (equivalent to running `uwsm stop`) after windows are closed.

## Root cause

`omarchy-system-logout` schedules the actual stop as a backgrounded job behind a 2s sleep, but the script itself (and the process scope it runs in) exits well before that:

```bash
nohup bash -c "sleep 2 && uwsm stop" >/dev/null 2>&1 &

omarchy-osd -i logout -m "Logging out" -d 5000

# Now close all windows
omarchy-hyprland-window-close-all
sleep 1 # Allow apps like Chrome to shutdown correctly
```

The script finishes (`sleep 1` returns) about 1 second before the backgrounded `sleep 2 && uwsm stop` job would fire. Depending on how the invoking process's scope/cgroup is reaped, that backgrounded job gets killed before `uwsm stop` ever runs — `nohup` only protects against SIGHUP, not against the parent scope tearing down its cgroup.

Running `uwsm stop` directly/interactively works fine, confirming the stop mechanism itself is not the problem — it's the backgrounding race.

## Suggested fix

Run the steps synchronously instead of backgrounding the stop, e.g.:

```bash
omarchy-osd -i logout -m "Logging out" -d 5000
omarchy-hyprland-window-close-all
sleep 1 # Allow apps like Chrome to shutdown correctly
uwsm stop
```

## Steps to reproduce

1. Open the Omarchy menu -> System -> Logout (or `omarchy system logout`)
2. Observe: "Logging out" toast appears, open windows close
3. Observe: session never actually stops

## System details

- Omarchy version: 4.0.4-1
- uwsm version: 0.26.7
- Compositor: Hyprland, launched via `uwsm start -g -1 -e -D Hyprland hyprland.desktop` (sddm autologin)