### System details

- Omarchy 4.0.0-1 (Quattro stable), upgraded from a pre-Quattro installation
- Linux 7.1.8-arch1-3
- Intel Core Ultra 5 228V
- Intel Arc Graphics 130V/140V
- Brave Origin Beta before upgrade: `brave-origin-beta-bin 1.94.109-1`
- Brave Origin stable after upgrade: `brave-origin-bin 1:1.93.136-1`

### What's wrong?

The Quattro migration `1784510887.sh` automatically installs Brave Origin stable, removes Brave Origin Beta, and changes the default browser:

```bash
omarchy-pkg-aur-add brave-origin-bin
omarchy-pkg-drop brave-origin-beta-bin
```

However, Beta and stable use different user-data directories:

- Beta: `~/.config/BraveSoftware/Brave-Origin-Beta`
- Stable: `~/.config/BraveSoftware/Brave-Origin`

The migration does not transfer or otherwise reconnect the existing profile. On first launch, stable creates a fresh profile, making the user's extensions, cookies/login sessions, history, and other browser state appear to have been deleted.

The data was not actually erased on this machine; it was stranded in the old Beta profile after the Beta package and launcher were removed.

#### Evidence from this installation

Pacman recorded the automatic switch at 20:31:

```text
installed brave-origin-bin (1:1.93.136-1)
removed brave-origin-beta-bin (1.94.109-1)
```

The old Beta profile was last modified immediately before the upgrade, while the new stable profile was created on the first post-upgrade launch:

```text
Brave-Origin-Beta: created 2026-07-08 23:25, last modified 2026-08-14 20:28
Brave-Origin:      created 2026-08-14 20:42
```

Without reading any browsing data, file metadata shows the profile discontinuity:

| Profile | Total size | History database | Cookies database | User extension directories |
|---|---:|---:|---:|---:|
| `Brave-Origin-Beta` | 5.2 GB | 7,274,496 bytes | 589,824 bytes | 4 |
| `Brave-Origin` | 82 MB | 163,840 bytes | 20,480 bytes | 0 |

This matches the observed behavior: Brave opens as a new browser with extensions gone, sites logged out, and history missing.

There is an additional downgrade risk: the migration replaced Beta 1.94.109 with stable 1.93.136, so blindly copying or reusing the newer Beta profile in the older stable build may be unsafe.

#### Steps to reproduce

1. On a pre-Quattro installation, use `brave-origin-beta-bin` as the default browser.
2. Accumulate history, cookies/login sessions, and install user extensions.
3. Upgrade to Quattro so migration `1784510887.sh` runs.
4. Launch the new default `brave-origin.desktop`.
5. Observe a fresh browser profile with the previous extensions, sessions, and history missing.
6. Compare `~/.config/BraveSoftware/Brave-Origin-Beta` and `~/.config/BraveSoftware/Brave-Origin`; the original data remains only in the Beta directory.

#### Expected behavior

A distribution upgrade should not make an existing browser profile disappear from the user's browser. The migration should preserve access to the existing profile or require an explicit, well-explained opt-in before switching release channels.

#### Actual behavior

The Beta package is removed and the default browser is changed to stable, which starts with a separate empty profile.

#### Suggested fix

Avoid automatically removing Brave Origin Beta during the Quattro upgrade. Keep it installed and selected until the user explicitly chooses to migrate to stable.

If an automatic migration is retained:

1. Back up the existing profile.
2. Ensure the target stable browser version is not older than the source Beta version.
3. Perform a supported profile migration from `Brave-Origin-Beta` to `Brave-Origin`.
4. Verify that extensions, cookies/session state, history, bookmarks, and saved credentials remain accessible before removing Beta.
5. Show a clear warning and recovery instructions if a safe migration cannot be guaranteed.

A regression test should create a populated Beta profile marker, run the migration, and verify that the replacement browser still uses or safely migrates that profile.