### System details

- Omarchy 4.0.4-1
- Hyprland 0.56.2, hyprsunset 0.4.0-3
- CPU: Intel Core i5-10300H
- GPU: Intel UHD (CometLake-H) + NVIDIA GTX 1650 Mobile

### What's wrong

`omarchy toggle nightlight` (Super + Ctrl + N) does nothing when another user on the same machine has a Hyprland session with `hyprsunset` running.

`bin/omarchy-toggle-nightlight` checks whether hyprsunset is running with:

```bash
if ! pgrep -x hyprsunset >/dev/null; then
  setsid uwsm-app -- hyprsunset &
fi
```

`pgrep` matches processes of every user, so it finds the other user's hyprsunset and never starts one for the current session. Then `hyprctl hyprsunset temperature ...` fails because there's no socket in the current Hyprland instance:

```
Couldn't connect to /run/user/1001/hypr/<signature>/.hyprsunset.sock. (3)
```

The toggle exits silently and the screen temperature never changes.

### Steps to reproduce

1. Log in as user A in Hyprland and run `omarchy toggle nightlight` (hyprsunset starts for user A).
2. Without logging out user A, switch to user B and log in to Hyprland.
3. As user B, press Super + Ctrl + N (or run `omarchy toggle nightlight`).
4. Nothing happens. `hyprctl hyprsunset temperature` returns the "Couldn't connect" error, and `pgrep -u "$USER" hyprsunset` returns nothing.

### Expected

The toggle starts hyprsunset for the current user's session and changes the temperature.

### Suggested fix

Limit the check to the current user:

```bash
if ! pgrep -u "$USER" -x hyprsunset >/dev/null; then
```

Other `pgrep -x` checks in `bin/` might need the same change.