## What happened

`omarchy install service sunshine` aborts partway through:

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

The script runs under `set -e`, so everything after the enable is skipped: the UFW rules, the Sunshine Admin web app, and the Hyprland autostart entry. The package gets installed, but Sunshine is never enabled, started, or reachable from Moonlight.

## Root cause

`bin/omarchy-install-service-sunshine` enables the unit by its short name:

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

The Arch `sunshine` package ships its unit as `/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service`. No `sunshine.service` file exists — that name comes only from `Alias=sunshine.service` in the unit's `[Install]` section.

systemd materializes `[Install]` aliases as symlinks *when a unit is enabled*. On a machine that has never enabled Sunshine the alias doesn't exist yet, so enabling via the alias cannot succeed: the enable would have to have already run for the name to resolve. This makes the installer fail deterministically on every fresh install.

## Expected

The service is enabled and started, the Moonlight ports are opened in UFW, the admin web app is installed, and autostart is configured.

## Steps to reproduce

On a machine with no prior Sunshine install:

1. Run `omarchy install service sunshine`
2. The package installs, then the run aborts with the error above.
3. `systemctl --user list-unit-files | grep -i sunshine` shows only `app-dev.lizardbyte.app.Sunshine.service`; no alias.

## Workaround

Enabling the real unit name works, and creates the alias as a side effect, after which the short name resolves normally:

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

## Suggested fix

Have the installer enable `app-dev.lizardbyte.app.Sunshine.service` rather than `sunshine`.

## Secondary observation (not verified)

The shipped unit is `WantedBy=graphical-session.target`, so enabling it already provides autostart. The installer additionally appends `o.launch_on_start("sunshine")` to `~/.config/hypr/autostart.lua`, which looks like it would start a second instance competing for port 47984 once the enable is fixed. I haven't tested that, but it may be worth checking alongside the fix.

## System

- Omarchy 4.0.3-1
- sunshine 2026.516.143833-4.1
- Kernel 7.2.3-arch1-3
- Intel Core i5-4210U, Haswell-ULT integrated graphics