## What happened

`omarchy install service sunshine` installs the package, then aborts:

```
(3/3) installing sunshine                                      [----] 100%
...
Failed to enable unit: Unit sunshine.service does not exist
```

Because the installer runs with `set -e`, everything after the enable never happens: no firewall ports opened, no "Sunshine Admin" webapp, no autostart. The user is left with Sunshine installed but unreachable and not running.

## Cause

The current sunshine package (omarchy repo, `2026.516.143833-4`) ships its unit under the upstream's new name:

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

`omarchy-install-service-sunshine` still runs:

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

`sunshine.service` only exists as an `Alias=` of the new unit, and systemd cannot *enable* by alias — only address an already-enabled unit through it. Hence "does not exist".

## Fix

Enable the real unit name:

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

(Verified working here — after enabling the real name and re-applying the installer's remaining steps manually, Sunshine works perfectly, including the `Alias=sunshine.service` resolving from then on.)

## Steps to reproduce

1. Omarchy 4.0.1, sunshine not installed
2. `omarchy install service sunshine`
3. Installer errors after package install; `systemctl --user status sunshine` shows nothing running, `ufw status` shows no sunshine rules

## System details

Omarchy 4.0.1-1, sunshine 2026.516.143833-4 (omarchy repo)