### System details

- Omarchy repo checkout: `basecamp/omarchy` at `8e031516`
- Hyprland: `0.55.2-2`
- Elephant: `2.21.0-1`
- Walker: `2.16.2-1`
- uwsm: `0.26.4-1`
- Signal Desktop: `8.12.0-1`
- Chromium: `148.0.7778.215-1`

### What's wrong?

Apps launched directly from a terminal worked normally, for example:

```sh
chromium
signal-desktop
```

But launching the same apps through the configured app launcher did nothing or appeared to lock up. Signal repeatedly segfaulted when started through the launcher, and Chromium/Signal left stale `SingletonLock` files behind after failed launches.

The launcher path was the important difference. Elephant auto-detected this launch prefix:

```text
systemd-run --user --scope
```

Relevant journal evidence before the workaround:

```text
INFO config "runprefix autodetect"="systemd-run --user --scope"
INFO desktopapplications activated=signal.desktop
Started [systemd-run] /usr/bin/signal-desktop --.
Process 6339 (signal-desktop) of user 1000 dumped core.
Process 6876 (signal-desktop) of user 1000 dumped core.
Process 10797 (signal-desktop) of user 1000 dumped core.
Process 11235 (signal-desktop) of user 1000 dumped core.
Process 14486 (signal-desktop) of user 1000 dumped core.
```

This also caused stale singleton locks such as:

```text
~/.config/Signal/SingletonLock -> phalanx-6876
~/.config/chromium/SingletonLock -> phalanx-7757
```

Those PIDs were dead and the referenced socket directories under `/tmp` no longer existed.

### Workaround

Pinning Elephant to use `uwsm-app --` fixed the launcher path:

```toml
# ~/.config/elephant/elephant.toml
auto_detect_launch_prefix = false
launch_prefix = "uwsm-app --"
```

I also enabled window integration to avoid spawning extra instances for already-open apps:

```toml
# ~/.config/elephant/desktopapplications.toml
window_integration = true
```

After restarting `elephant.service`, the launcher path changed to UWSM and Signal no longer hit the same failure path:

```text
INFO desktopapplications activated=signal.desktop
uwsm_app-daemon received: app -- signal-desktop --
uwsm_app-daemon sent: exec systemd-run --user --scope --slice=app-graphical.slice ... -- signal-desktop --
Started app-signal-21162.scope.
```

### Expected behavior

On Omarchy, Elephant should prefer `uwsm-app --` for desktop application launches when UWSM is available, or Omarchy should ship a default Elephant config that pins:

```toml
auto_detect_launch_prefix = false
launch_prefix = "uwsm-app --"
```

### Actual behavior

Elephant auto-detected raw `systemd-run --user --scope`, which created a subtly different launch environment than the working terminal/UWSM path and caused Electron/Chromium-family apps launched from the app launcher to fail or crash.