### What happened

On a clean Omarchy install, `omarchy install service sunshine` installs the
package and then aborts. Sunshine ends up installed but **not enabled, not
started, with no firewall rules, no admin web app, and no autostart entry**.
The only visible output is:

```
Installing Sunshine...
```

followed by the failure of the `systemctl` call.

### Root cause

`omarchy-install-service-sunshine` runs:

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

But the `sunshine` package ships its user unit as
`/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service`, whose
`[Install]` section declares:

```ini
[Install]
WantedBy=graphical-session.target
Alias=sunshine.service
```

A systemd `Alias=` is only materialised as a symlink **when the unit is
enabled**. On a fresh install the unit has never been enabled, so
`sunshine.service` does not resolve yet and the enable call fails:

```
$ systemctl --user status sunshine
Unit sunshine.service could not be found.

$ systemctl --user list-unit-files | grep -i sunshine
app-dev.lizardbyte.app.Sunshine.service    disabled  enabled
```

Because the script is `set -e`, it exits at that point, so
`open_ufw_ports`, `install_admin_webapp` and `enable_hyprland_autostart`
never run.

### Why this is easy to miss when reproducing

Enabling the unit by its real name creates the alias symlink:

```
/home/<user>/.config/systemd/user/sunshine.service
  -> /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
```

After that, `systemctl --user enable --now sunshine` resolves fine and a
re-run of the installer succeeds. **The bug only reproduces on a machine
where the unit has never been enabled.**

### Steps to reproduce

1. Fresh Omarchy install with no prior Sunshine
2. `omarchy install service sunshine`
3. Observe the script stops after "Installing Sunshine..."
4. `systemctl --user is-enabled sunshine` -> `not-found`
5. `sudo ufw status | grep omarchy-sunshine` -> no rules

### Expected

Sunshine enabled and running, Moonlight ports opened for private LANs and
`tailscale0`, admin web app installed, autostart configured.

### Suggested fix

Enable the unit by the name the package actually ships:

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

Worth noting for the autostart step: that unit is already
`WantedBy=graphical-session.target`, so it starts with the session on its
own. Adding `o.launch_on_start("sunshine")` to `autostart.lua` on top of the
enabled unit launches a second instance that contends for the same ports —
so `enable_hyprland_autostart` may be redundant once the unit is enabled
correctly.

### System details

- Omarchy 4.0.2-1
- `sunshine` 2026.516.143833-4
- CPU: Intel Core i7-6700
- GPU: Intel HD Graphics 530 + NVIDIA Quadro K1200
- Hyprland 0.56.2, session via uwsm, SDDM autologin