## Summary

Migration `1789325478` (Omarchy 4.0.4, "Install our bespoke kernel and set `linux-omarchy` as the default boot option") exempts Macs from the kernel swap, but the test only recognises **T2** Macs. Every other Apple machine, T1 and pre-T2 alike, is switched to `linux-omarchy` and has its `BOOT_ORDER` rewritten.

The comment says Mac. The code says T2.

```sh
# linux-omarchy is an x86_64 kernel. T2 Macs must keep their specialized kernel,
# including when other kernels are installed or the running T2 package is gone.
[[ $(uname -m) == "x86_64" ]] || exit 0
running_kernel=$(uname -r)
if omarchy-pkg-present linux-t2 || [[ ${running_kernel,,} == *-t2* ]]; then
  exit 0
fi
```

Both limbs are T2-specific: the `linux-t2` package, and a `-t2` substring in the running kernel release. A Mac on stock `linux` matches neither.

## Measured

MacBookPro14,2 (A1706, Intel i7-7567U, Apple **T1**), Omarchy 4.0.3 to 4.0.4, running stock `linux` 7.2.3-arch1-3. The migration applied in full: it installed `linux-omarchy` and `linux-omarchy-headers` 7.2.5-3, rewrote `BOOT_ORDER` in `/etc/default/limine`, and ran `limine-mkinitcpio linux-omarchy`. Read from `/usr/share/omarchy/migrations/1789325478.sh` on the machine, and confirmed against this repository.

For what it is worth, the swap was clean here: both out-of-tree T1 modules (`appleibridge`, `snd_hda_macbookpro`) rebuilt for 7.2.5-3, the new UKI's kernel cmdline came out byte-identical to the old one (LUKS mapping, `rootflags=subvol=@`, `modprobe.blacklist`, swapfile resume offset all preserved), and the machine boots and runs normally on the new kernel. **I am not reporting a breakage on my own hardware.** This is about the guard's scope.

## Why the scope matters

Two open issues are non-T2 Macs that took this same swap and could not live with it:

- #12097, `linux-omarchy` 7.2.5-3 boots to emergency shell on a MacBookAir6,1, while stock `linux` boots the same encrypted root immediately.
- #12131, constant HDMI audio underruns on a Haswell Mac since 4.0.4 installed the new kernel, with stock `linux` 7.2.3 working.

Neither machine is a T2, so neither was exempted. I am not claiming their root cause is the guard; their root cause is whatever `linux-omarchy` does differently on that hardware. The guard is what put them on it.

## Suggested fix

Widen the exemption from "is this a T2" to "is this an Apple Mac", for example a DMI vendor test alongside the existing checks:

```sh
[[ $(cat /sys/class/dmi/id/sys_vendor 2>/dev/null) == "Apple Inc." ]] && exit 0
```

That keeps the stated intent (Macs keep the kernel they were installed with) without needing a model list. Anyone who wants the Omarchy kernel on a Mac can still install it by hand.

Worth noting for future migrations: this guard reads like the canonical "skip Macs" idiom, so anything copying it inherits the same gap.