### What happened

Running `omarchy install service sunshine` installs the package correctly, but then fails with:

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

Because the script uses `set -e`, it aborts at that point, so **everything after the enable step is silently skipped**: the UFW streaming ports are never opened, the "Sunshine Admin" web app is not installed, and the Hyprland autostart entry is not added. The user is left with Sunshine installed but unusable from Moonlight (connection blocked by the firewall).

### Cause

The `sunshine` package (`omarchy/sunshine 2026.516.143833-4`) now ships its user unit as:

```
/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
```

with `Alias=sunshine.service` in its `[Install]` section. A systemd alias only resolves after the unit is enabled, so line 74 of `bin/omarchy-install-service-sunshine`:

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

fails with "Unit sunshine.service does not exist".

### Fix

Enable the unit by its real name (the alias then gets created, so `sunshine.service` works afterwards):

```bash
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
```

Verified manually on the affected machine: enabling by the full name works, creates the `sunshine.service` alias symlink, and the service runs fine. `bin/omarchy-remove-service-sunshine` likely needs the same treatment for its disable step.

### Steps to reproduce

1. Fresh Omarchy install (v4.0.0) without Sunshine.
2. Run `omarchy install service sunshine`.
3. Package installs, then the enable step fails and the script aborts before opening firewall ports.

### System details

- Omarchy version: 4.0.0-1 (script also present unchanged on the `quattro` branch, `bin/omarchy-install-service-sunshine` line 74)
- sunshine package: `omarchy/sunshine 2026.516.143833-4`
- CPU: Intel Core i5-6600
- GPU: AMD Radeon R9 M395X