## Summary

Migration `1785543725.sh` (added in d47b4b0 "Collapse WhatsApp Web to a Signal-style avatar rail in slim windows") appends the `whatsapp-slim` extension to browser flags files, but the browser list contains `brave-origin-beta` instead of `brave-origin`. As a result the extension is **never loaded in Brave Origin** while it works in Chromium.

## Root cause

`migrations/1785543725.sh:18`:

```bash
for conf in chromium chrome google-chrome brave brave-beta brave-nightly brave-origin-beta microsoft-edge-stable; do
  add_whatsapp_slim_extension "$HOME/.config/$conf-flags.conf"
done
```

This targets `$HOME/.config/brave-origin-beta-flags.conf`. However, the AUR `brave-origin-bin` package's launcher (`/usr/bin/brave-origin`) reads a different file:

```bash
CONF_FILE="${XDG_CONFIG_HOME}/brave-origin-flags.conf"
```

So `~/.config/brave-origin-flags.conf` never gets the `whatsapp-slim` entry added, and Brave Origin keeps only the pre-existing `copy-url` and `yt-dlp` extensions. There is no `brave-origin-beta` package or flags file in common use, so that loop entry is effectively dead.

## Impact

- `whatsapp-slim` loads correctly in Chromium but not in Brave Origin.
- Users who already ran the migration must manually append `,/usr/share/omarchy/default/chromium/extensions/whatsapp-slim` to the `--load-extension=` line in `~/.config/brave-origin-flags.conf` and restart the browser.

## Suggested fix

Replace `brave-origin-beta` with `brave-origin` in the loop (or keep both for safety):

```bash
for conf in chromium chrome google-chrome brave brave-beta brave-nightly brave-origin microsoft-edge-stable; do
```

Note: this migration already shipped, so a follow-up migration may also be needed to append the extension for existing Brave Origin users.