### System details

OS: 4.0.0.r1658.g0820484-1 CPU: Intel Core Ultra 9 185H GPU: NVIDIA GeForce RTX 4060 Laptop GPU

### What's wrong?

   ### System details

   - Omarchy: `4.0.0.r1658.g0820484-1` when the problem occurred
   - CPU: Intel Core Ultra 9 185H
   - GPUs:
     - Intel Meteor Lake-P Arc Graphics
     - NVIDIA GeForce RTX 4060 Laptop GPU
   - Root filesystem: encrypted Btrfs
   - Bootloader: Limine
   - Kernel after update: `7.1.8-arch1-3`
   - NVIDIA driver: `610.57.04-1`
   - systemd after update: `261.2-1`
   - mkinitcpio: `41-4`
   - cryptsetup: `2.8.7-1`

   ### What happened?

   After upgrading to the Quattro development release, the first normal reboot entered a boot loop. The newly
 generated normal UKI failed during early boot, before the encrypted root filesystem was mounted.

   Because the failure occurred before the real root filesystem and journal were available, the failed attempts
 did not produce persistent journal entries.

   Booting a pre-upgrade Snapper snapshot allowed me to recover the system.

   ### Steps leading to the problem

   1. Upgrade Omarchy to the Quattro development release.
   2. The upgrade updates the kernel, systemd, cryptsetup, Limine and NVIDIA packages.
   3. Allow the update to regenerate the normal UKI.
   4. Reboot and select the normal Omarchy Linux entry.
   5. The machine fails during early boot and loops instead of reaching the encrypted-root unlock/session.

   ### Relevant upgrade transaction

   The following packages were updated immediately before the failure:

   ```text
   systemd:                  261.1-1 -> 261.2-1
   cryptsetup:               2.8.6-1 -> 2.8.7-1
   limine:                   12.5.1-1 -> 12.5.2-1
   limine-mkinitcpio-hook:   1.36.0-1 -> 1.37.1-1
   linux:                    7.1.4.arch1-1 -> 7.1.8.arch1-3
   nvidia-utils:             610.43.03-3 -> 610.57.04-1
   nvidia-open-dkms:         610.43.03-3 -> 610.57.04-1
 ```

 ### Investigation and recovery

 The broken UKI was confirmed to use:

 ```text
   LoaderInfo: systemd-stub 261.2-1-arch
 ```

 It contained the expected components, including:

 ```text
   hooks/encrypt
   usr/bin/cryptsetup
   usr/lib/modules/7.1.8-arch1-3/updates/dkms/nvidia.ko.zst
 ```

 I then built a compatibility UKI using:

 - Current kernel 7.1.8-arch1-3
 - Current NVIDIA modules 610.57.04
 - Pre-upgrade initramfs userspace and systemd-stub from Snapper snapshot 1712
 - systemd-stub 261.1-1-arch

 That UKI booted successfully into the current root filesystem.

 The system is currently running successfully with:

 ```text
   Kernel: 7.1.8-arch1-3
   LoaderInfo: systemd-stub 261.1-1-arch
 ```

 This suggests that the root filesystem, current kernel and current NVIDIA modules are healthy. The failure
 appears to be somewhere in the early-boot UKI generated after the upgrade—potentially the updated initramfs
 userspace, systemd-stub, cryptsetup integration, or Limine/mkinitcpio generation path.

 I cannot conclusively attribute it to systemd-stub alone because the successful recovery UKI uses both the older
 stub and older initramfs userspace.

 ### Expected behavior

 The UKI generated by the upgrade should unlock and mount the encrypted Btrfs root filesystem and boot normally.

 ### Actual behavior

 The regenerated UKI fails before mounting root and causes a boot loop. A compatibility UKI using the previous
 initramfs userspace/systemd-stub boots successfully with the current kernel and NVIDIA modules.