## What happened

`omarchy-settings 4.0.0-1` installs
`/usr/lib/systemd/zram-generator.conf.d/90-omarchy.conf`:

```ini
[zram0]
zram-size = ram
compression-algorithm = zstd
swap-priority = 100
```

But nothing installs the `zram-generator` package that reads it:

- `omarchy-settings` does not depend on `zram-generator`
- `omarchy` does not depend on it either
- no script under `/usr/share/omarchy/install/` installs it — `zram-generator`
  appears only in `install/omarchy-other.packages`, which is the offline
  package-cache manifest rather than a to-install list

Result: on a system where `zram-generator` isn't pulled in by some other route,
the shipped zram tuning is silently inert. No zram device is created, and the
machine runs with no swap at all if the hibernation swapfile has been removed —
while `systemd-oomd` is enabled and benefits from swap being present.

## Expected

Either `omarchy-settings` should `depends=('zram-generator')`, or an install
step should `omarchy-pkg-add zram-generator`, so the config it ships actually
takes effect.

## Steps to reproduce

On a system where `zram-generator` is not installed:

```bash
pacman -Q zram-generator                 # error: package not found
cat /usr/lib/systemd/zram-generator.conf.d/90-omarchy.conf   # config is present
zramctl                                   # empty — no zram device
swapon --show                             # no zram entry
```

Then `pacman -S zram-generator && systemctl daemon-reload` and the shipped
config immediately takes effect (`zramctl` shows zram0 at RAM size, zstd,
priority 100), confirming the config is correct and only the package was missing.

## System

- Omarchy: 4.0.0-1
- CPU: Intel(R) Core(TM) i7-6770HQ CPU @ 2.60GHz
- GPU: Intel Corporation Skylake-H GT4 [Iris Pro Graphics 580] (rev 09)
- Kernel: 7.1.8-arch1-3
- Install path: manual/online install (`curl -fsSL https://omarchy.org/install | bash`)
  onto a hand-built Arch base, later upgraded to Quattro via `omarchy update`

(Deliberately not attaching `omarchy debug` output: this is a packaging
inconsistency reproducible from the package contents alone, and the debug log
carries VPN peer addresses and hostnames I'd rather not publish.)