### What happened

`omarchy install service sunshine` aborts partway through. The package installs, but the
service is never enabled and every step after it is skipped.

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

The installer runs:

```bash
omarchy-pkg-add sunshine
systemctl --user enable --now sunshine     # <-- fails here
```

But the `sunshine` package (2026.516.143833-4.1) ships its unit under a reverse-DNS name:

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

There is no `sunshine.service` on disk. That name only exists as an `Alias=` inside the
unit's `[Install]` section, so the symlink is not created until the unit is enabled *by its
real name*. The installer therefore enables a unit that does not yet exist.

Because `omarchy-install-service-sunshine` runs under `set -e`, the script exits at that
line and never reaches:

- `open_ufw_ports` — Moonlight's TCP/UDP ports stay closed, so clients cannot connect
- `install_admin_webapp` — no "Sunshine Admin" launcher for the `https://localhost:47990` UI
- `enable_hyprland_autostart` — no autostart entry

The user is left with Sunshine installed, not running, and unreachable, with no indication
that four of the five steps were skipped.

### A second-run trap

Enabling the real unit by hand fixes the service, but it also creates the alias symlink:

```
Created symlink ~/.config/systemd/user/sunshine.service
  -> /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
```

Re-running the installer then fails a *different* way, because systemd will not enable a
name that is now a linked unit:

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

So the script cannot complete on the first run or on any subsequent run.

### Expected

`omarchy install service sunshine` enables Sunshine and completes the firewall, web app,
and autostart steps.

### Steps to reproduce

1. On a clean Omarchy 4.0.3-1 install, run `omarchy install service sunshine`
2. Observe `Failed to enable unit: Unit sunshine.service does not exist`
3. `systemctl --user status sunshine` — not running
4. `sudo ufw status` — no `omarchy-sunshine` rules

### Workaround

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

Then perform the firewall, web app, and autostart steps manually.

### Suggested fix

Enable the unit by its real name, falling back for future package renames — e.g. resolve the
unit via `systemctl --user list-unit-files 'app-dev.lizardbyte.app.Sunshine.service' 'sunshine.service'`
and enable whichever exists. Treating the enable as non-fatal would also stop one failure
from silently skipping the firewall step, which is the part that actually leaves Sunshine
unreachable.

### System details

- Omarchy: 4.0.3-1
- Package: sunshine 2026.516.143833-4.1
- Kernel: 7.2.3-arch1-Watanare-T2-2-t2
- CPU: Intel Core i3-8100B (2018 Mac mini, T2)
- GPU: Intel UHD Graphics 630 (VAAPI; h264_vaapi + hevc_vaapi both work once running)