### System details

Intel i7-10875H, NVIDIA RTX 3080 Mobile (hybrid graphics, compositor on the Intel iGPU), Omarchy 4.0.4-1, `omarchy/sunshine 2026.516.143833-4.1`

### What's wrong?

`omarchy install service sunshine` aborts right after the package installs, so none of the follow-up steps run: no UFW rules, no "Sunshine Admin" web app, no autostart entry.

```
$ omarchy install service sunshine
Installing Sunshine...
[sudo] password for win:
...
(3/3) installing sunshine                          [------------------] 100%
...
Failed to enable unit: Unit sunshine.service does not exist
```

**Cause.** `bin/omarchy-install-service-sunshine` runs

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

but the `sunshine` package currently in the omarchy repo ships its user unit as
`/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service`. That unit only
carries `sunshine.service` as an `Alias=` in its `[Install]` section:

```
$ pacman -Ql sunshine | grep systemd/user/
sunshine /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
$ grep -E 'Alias|WantedBy' /usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service
WantedBy=graphical-session.target
Alias=sunshine.service
```

Per `systemd.unit(5)`, `Alias=` names are symlinks that `systemctl enable`
creates when the unit is enabled. On a fresh install that symlink does not
exist yet, so enabling by the alias name fails, and `set -e` stops the script
there. `bin/omarchy-remove-service-sunshine` uses the same alias name in its
`systemctl --user disable --now sunshine`, which is harmless because of the
`|| true`, but leaves the unit enabled if the alias was never created.

**Workaround that confirms it.** Enabling by the real unit name works and
creates the alias as a side effect:

```
$ systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
Created symlink '~/.config/systemd/user/sunshine.service' → '/usr/lib/systemd/user/app-dev.lizardbyte.app.Sunshine.service'.
Created symlink '~/.config/systemd/user/graphical-session.target.wants/app-dev.lizardbyte.app.Sunshine.service' → ...
```

After that, `systemctl --user enable --now sunshine` succeeds too.

**Suggested fix.** Use the real unit name in both scripts, e.g.

```
systemctl --user enable --now app-dev.lizardbyte.app.Sunshine.service
...
systemctl --user disable --now app-dev.lizardbyte.app.Sunshine.service 2>/dev/null || true
```

Steps to reproduce: on a machine without Sunshine installed, run
`omarchy install service sunshine` and watch it stop at "Failed to enable unit".

Separately, since the installer also appends `o.launch_on_start("sunshine")`
to `autostart.lua` while the systemd unit is `WantedBy=graphical-session.target`,
a successful run starts Sunshine twice per login. The second copy fails to bind
its ports and exits, so it is only noise, but it may be worth dropping one of
the two.