### What happened

The Sunshine installer enables its systemd user service and also adds a separate
Hyprland autostart entry:

```bash
systemctl --user enable --now sunshine
```

and:

```lua
o.launch_on_start("sunshine")
```

After a new graphical login, Hyprland started one Sunshine instance and the
enabled systemd user service started another. The second instance could not bind
Sunshine's RTSP port and aborted:

```text
Fatal: Couldn't bind RTSP server to port [48010], Address already in use
```

systemd restarted the service five times, producing five SIGABRT coredumps, and
then stopped with `start-limit-hit`.

### Evidence

The surviving instance was launched by Hyprland:

```text
PID 3754 /usr/bin/sunshine
CGroup:
app.slice/app-graphical.slice/app-Hyprland-sunshine-a84395f3.scope
```

The crashing instance was launched by the packaged user service:

```text
PID 11152 /usr/bin/sunshine
User Unit: app-dev.lizardbyte.app.Sunshine.service
Signal: SIGABRT
```

PID 3754 was already listening on TCP port 48010 before PID 11152 aborted.

The installed and current upstream installer both:

1. enable the Sunshine systemd user service; and
2. append `o.launch_on_start("sunshine")` to
   `~/.config/hypr/autostart.lua`.

The packaged unit is already tied to `graphical-session.target`, so the
additional Hyprland launch creates a second owner for the same Sunshine ports.

### Steps to reproduce

1. Have the canonical Sunshine user unit enabled, or work around the unit alias
   problem described in #7050.
2. Complete the remaining steps in `omarchy-install-service-sunshine`, including
   its Hyprland autostart setup.
3. Log out and start a new graphical session, or reboot.
4. Observe two Sunshine processes starting.
5. The systemd-managed instance aborts because RTSP port 48010 is already owned
   by the Hyprland-launched instance.
6. Repeated service restarts eventually result in `start-limit-hit`.

On a fresh installation this issue may currently be masked by #7050 because the
installer can abort at `systemctl --user enable --now sunshine` before reaching
the Hyprland autostart step.

### Expected behavior

The installer should configure exactly one Sunshine startup path.

### Suggested fix

Keep the canonical systemd user service:

```text
app-dev.lizardbyte.app.Sunshine.service
```

and do not add `o.launch_on_start("sunshine")` to the Hyprland autostart file.

The service already has:

```ini
WantedBy=graphical-session.target
```

The canonical unit name also avoids the alias problem tracked in #7050.

### System details

- Omarchy: 4.0.0-1
- Sunshine: 2026.516.143833-4
- Kernel: 7.1.8-arch1-3
- Result: five SIGABRT coredumps followed by `start-limit-hit`
- No OOM kill or memory exhaustion was present

Filed by GPT-5 via Codex.