## What happened

Updating 4.0.3-1 -> 4.0.4-1, `omarchy update` repeatedly failed to download large packages from `pkgs.omarchy.org`:

```
error: failed retrieving file 'spotify-1:1.2.96.518-3-x86_64.pkg.tar.zst' from pkgs.omarchy.org : Recv failure: Connection reset by peer
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
```

First run also failed on `omarchy-4.0.4-1-x86_64.pkg.tar.zst` the same way. Pacman left a stale `.part` file and retried from scratch each time (`Total (2/2) ... 100%` then fail at ~83-84%, ~85MB of 158MB). `omarchy update analyze logs` reported nothing (it only checks initramfs).

## What was expected

Large package downloads complete (or resume and recover) over IPv6.

## Reproduction / evidence

File: `https://pkgs.omarchy.org/stable/x86_64/spotify-1:1.2.96.518-3-x86_64.pkg.tar.zst` (166,220,614 bytes, `accept-ranges: bytes`, Cloudflare, `cf-cache-status: DYNAMIC`).

| Test | Result |
|---|---|
| `curl -4` full 158MB file | OK every time (~10 MB/s, 15s) |
| `curl -6` same file, attempt 1 | `curl: (56) Recv failure: Connection reset by peer` after ~21MB |
| `pacman` via `omarchy update` (2 runs) | Same reset at ~85MB, transaction aborted |
| `curl -6` same file, attempt 2 (20 min later) | Full 158MB OK (~8 MB/s, 20s) |

So: intermittent, IPv6-only, large-response-only. Small responses over IPv6 are fine (`curl -6 -I` returns 200s, archlinux.org over IPv6 returns 200). Host resolves to `2606:4700::6812:2cc` / `2606:4700::6812:3cc` (Cloudflare; cf-ray colo CMH). Local IPv6 is native (RA on ethernet, `/64`), general IPv6 works.

```
# failing case
timeout 120 curl -6 -o /tmp/spotify-test6.zst "https://pkgs.omarchy.org/stable/x86_64/spotify-1:1.2.96.518-3-x86_64.pkg.tar.zst"
# curl: (56) Recv failure: Connection reset by peer
```

## System details

- Omarchy 4.0.4-1 (update eventually completed via workaround below)
- Pacman server: `https://pkgs.omarchy.org/stable/$arch` (from `/etc/pacman.conf`)
- Note: there is no `omarchy debug` command in 4.0.4 (`Unknown Omarchy command: omarchy debug --no-sudo --print`), so diagnostics above were gathered manually.

## Workaround used

Fetched the file over IPv4 straight into the pacman cache, then re-ran the update, which verified the cached file and completed:

```bash
sudo rm -f "/var/cache/pacman/pkg/spotify-1:1.2.96.518-3-x86_64.pkg.tar.zst.part"
sudo curl -4 -o "/var/cache/pacman/pkg/spotify-1:1.2.96.518-3-x86_64.pkg.tar.zst" "https://pkgs.omarchy.org/stable/x86_64/spotify-1:1.2.96.518-3-x86_64.pkg.tar.zst"
omarchy update
```

Flagging in case the DYNAMIC (uncached origin fetch) path or edge config for large package files needs a look, or pacman downloads need retry/resume hardening.