## What happened

`omarchy install service sunshine` aborts immediately after the package
install, leaving Sunshine installed but completely unconfigured.

The `sunshine` package ships its unit as
`app-dev.lizardbyte.app.Sunshine.service`, which declares
`Alias=sunshine.service`. systemd only materialises an `Alias=` symlink when
the unit is enabled, so on a fresh install there is no `sunshine.service` in
the search path yet:

```
Failed to enable unit: Unit sunshine.service does not exist
```

`omarchy-install-service-sunshine` runs under `set -e`, so everything after
that line is skipped: the UFW port rules, the admin web app, and the Hyprland
autostart entry. The result is the package installed, no service, and a
firewall still blocking Moonlight, with no indication that three
configuration steps were missed.

Retrying does not help. Once the unit is enabled by its real name, systemd
creates `~/.config/systemd/user/sunshine.service` as a symlink, and enabling
through it is then refused:

```
Failed to enable unit: Refusing to operate on linked unit file sunshine.service
```

So there is no state in which line 74 succeeds: the alias is missing before
the unit is enabled, and is a linked unit file afterwards.

## Expected

The service is enabled, the Moonlight ports are opened, and the admin web app
is installed.

## Steps to reproduce

1. Omarchy 4.0.1 with the `sunshine` package not yet installed
2. Run `omarchy install service sunshine`
3. The package installs, then the script exits at the `systemctl --user
   enable --now sunshine` call

## Confirmation

```
$ ls /usr/lib/systemd/user/ | grep -i sunshine
app-dev.lizardbyte.app.Sunshine.service

$ grep -E '^(Alias|WantedBy)' /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
WantedBy=graphical-session.target
Alias=sunshine.service
```

## Suggested fix

Enable the real unit name in `omarchy-install-service-sunshine`:

```diff
-systemctl --user enable --now sunshine
+systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
```

`omarchy-remove-service-sunshine` is fine as-is: by removal time the alias
exists, so `disable sunshine` resolves, and the call is guarded with
`|| true` regardless.

## Secondary observation

The unit already declares `WantedBy=graphical-session.target`, so enabling it
places it in `graphical-session.target.wants`. `enable_hyprland_autostart`
then also adds `o.launch_on_start("sunshine")`, which starts Sunshine a
second time on login. The duplicate instance fails to bind the already-taken
ports and exits. One of the two mechanisms looks redundant.

## System

- Omarchy 4.0.1-1
- sunshine 2026.516.143833-4 (omarchy repo)
- systemd 261 (261.2-1-arch)
- Hyprland 0.56.2
- Kernel 7.1.9-arch1-2
- CPU: 12th Gen Intel Core i7-12700
- GPU: Intel UHD Graphics 770 (Alder Lake-S GT1)

Enabling the unit by its real name works correctly and Sunshine finds
hardware encoders (`h264_vaapi`, `hevc_vaapi`), so this is purely the
installer's enable call. A full `omarchy debug` log can be provided if
useful; it is omitted here since it contains host-specific detail.