Wrong generated GRUB config, failing to boot

I just installed Fedora 44 Sway Atomic and the GRUB config is wrong, making it unable to boot by itself. It is trying to boot vmlinuz and initrd from /ostree but the correct path is /boot/ostree/. I edit it that way to boot. I had to manually partition on setup.

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 128M 0 part
├─sda2 8:2 0 1G 0 part
├─sda3 8:3 0 80.7G 0 part
├─sda4 8:4 0 39.9G 0 part
├─sda5 8:5 0 16M 0 part
├─sda6 8:6 0 57.3G 0 part
├─sda7 8:7 0 58.8G 0 part /var
│ /boot
│ /sysroot/ostree/deploy/fedora/var
│ /sysroot
│ /etc
└─sda8 8:8 0 613.2M 0 part /sysroot/boot/efi
/boot/efi
zram0 251:0 0 7.6G 0 disk [SWAP]

The important part is that I don’t have a separate boot partition. $root in GRUB points to (hd0,gpt7) which contains my whole Fedora installation. So /ostree relative to that doesn’t make any sense. It should be /boot/ostree which resolves properly. If I had a separate boot partition and $root pointed to it, then there I wouldn’t have a /boot directory layer and so /ostree resolves properly and that partition be mounted as /boot in sda7. So maybe the config is expecting a separate boot partition but it is obvious that it should generate the proper config without it.

I don’t think we support not having /boot as a distinct partition: https://docs.fedoraproject.org/en-US/atomic-desktops/installation/#manual-partition

GRUB configs are now static on Atomic Desktops and not dynamically generated.