Move Macs onto Omarchy's official packages with a standalone omarchy-mac-migrate

[maralcbr]

Moving existing Macs onto Omarchy's official packages is now a standalone script, not part of any package (agreed with Ryan on 2026-10-04: the Mac packages move to omacom/omarchy-mac-pkgs without the migration engine; omacom#13362 uses them).

What it adds

• omarchy-mac-migrate: a single self-contained script built from migrate/src by migrate/build and committed as bin/omarchy-mac-migrate. It is the quattro-upstream engine (Migration engine with the quattro-upstream tester transition #559, Convert legacy omarchy-mac installs to official packages and trust #564, Migrate mx-mac Macs in place (ticket 43) #571, Switch legacy Macs' boot chain to Limine, keeping their encryption #582, Migrate Macs from a verified download of omarchy-mac-boot, handing files over inside the transaction #602, Keep an administrator's migration target as it is in the Mac bootstrap #607) taken out of omarchy-mac-boot and reworked:
  • It moves a quattro Mac, an omarchy-mx-mac Mac or a pinned test image onto its channel's official packages. On edge that is the omarchy-dev pair, omarchy-mac and omarchy-mac-boot (from omarchy-mac-pkgs), the Aurora chain, and Converge omarchy-mac and omarchy-mx-mac into upstream Omarchy omarchy#13362's Apple Silicon pacman.conf. No fork package, repository, key or pin is left.
  • A channel whose signed archives don't carry the Mac yet defers (exit 75, nothing changed): stable and rc today, and edge until omarchy-mac-pkgs is published and the dev pair has the dispatcher.
  • Kept from the old engine: the journal and resume, backups, one pacman transaction rehearsed on a database copy, the shared-files guard, and refusals that leave the Mac byte-identical. New:
    • frozen sync databases;
    • an IgnorePkg guard from the switch until the setup is verified;
    • a pre-switch failure sets the attempt aside and defers; after the switch, a failure exits 1 and its own boot unit (a kept copy of the tool) resumes it;
    • setup through the new runtime's omarchy-lifecycle-dispatch (setup-boot, setup-system, setup-user, update-verify);
    • the fork leftovers that omarchy-mac-pkgs da8279b stopped retiring are now retired here.
• Delivery to quattro Macs (approach A, ticket 53): migrations/1791080196.sh marks the Mac. The next omarchy update runs the tool before any fork step and stops for the reboot, or updates as before while the move defers.
• Testers: a one-line command in the README, with the release asset's checksum (migrate/build --check keeps it current).

Supersedes #603. The code of #601, #602 and #607 is the tool's source.

Tests

• New fixture suites mac-migrate-test.sh (tester cohort, engine), mac-migrate-legacy-test.sh, mac-migrate-mx-test.sh and mac-move-migration-test.sh: 104 checks. They cover kill -9 after, during and in the middle of every step, deferral before the switch and failure after it, the guard, channel detection and qualification, and leftovers.
• VM runs on the M1 (aarch64 KVM with the Mac image harness, on the encrypted test image apple-test-f22c43fb7903). The target was a test-lane-signed set: the Converge omarchy-mac and omarchy-mx-mac into upstream Omarchy omarchy#13362 (69d80cc) dev pair, plus omarchy-mac and omarchy-mac-boot from proposal/main without the engine. Everything else came from the real edge.
  • Stable: deferred (75) with the Mac byte-identical.
  • Today's edge: deferred. The dev pair has no dispatcher, and the boot package carries the old engine.
  • Test image → edge: passed.
  • mx-mac → edge: the guest ran the fork's omarchy-dev 4.0.4.r7099 bundle. The rc lane deferred unchanged. On the edge lane, the fork's pair went down to the official build in one transaction, with kills during prefetch and the boot-chain rebuild resumed.
  • Encrypted legacy → edge: the guest was set up as quattro's layout (GRUB, busybox encrypt from cryptdevice=, ESP at /boot, [omarchy-aarch64] lane). The ESP moved to /boot/efi, the unlock to sd-encrypt and the loader to Limine.
  • After each move, pacman.conf was the core configuration and the migrated disk unlocked with the same password through its own boot files and reached a login. The boot unit's verification correctly refused the guest's generic kernel; completion needs a Mac.
• Two design debate rounds and two code review rounds; every verified finding is fixed (boundary event, lock contention, retired keys in preflight, NoExtract/NoUpgrade, guard scope, update-hook exit, payload tool trust, resume unit kept through user-setup retries, HOOKS preview). The VM runs used an earlier build (879faa65); the fixes after it are covered by the fixture suites.
• Not done: real Mac hardware (the post-reboot verification needs the Aurora kernel). A power loss inside the pacman transaction itself is not recoverable by the tool, as for any pacman upgrade.

Release (owner): merge, publish bin/omarchy-mac-migrate as release mac-migrate-v1, and publish a quattro omarchy build to the [omarchy-aarch64] lanes so packaged quattro installs get it (checkout installs get it from git pull). Nothing moves until omarchy-mac-pkgs' packages and a dev pair with omacom#13362 are on edge.