Installing systemd-boot using the architect menu doesn't work

v0.9.34 (manjaro-architect 0.9.34-5)

I'm installing into a VirtualBox VM using different ISOs (i3 and KDE), the issue is the same for both.

When I select the menu option to install systemd-boot as boot manager, I get a message, that it has been installed, but it actually hasn't, at least not completely. Of course, at this point, /boot is already mounted and the kernel images are present.

Later, when chrooting into the new installation, I can confirm this:

# ls -l /boot
total 47560
-rwxr-xr-x 1 root root    40960 Feb 11 16:27 amd-ucode.img
-rwxr-xr-x 1 root root 30314187 Mar 16 17:21 initramfs-5.4-x86_64-fallback.img
-rwxr-xr-x 1 root root  8203205 Mar 16 17:21 initramfs-5.4-x86_64.img
-rwxr-xr-x 1 root root  3624960 Feb 17 08:15 intel-ucode.img
-rwxr-xr-x 1 root root       22 Feb 26 11:18 linux54-x86_64.kver
drwxr-xr-x 2 root root     4096 Mar 16 17:21 memtest86+
-rwxr-xr-x 1 root root  6506816 Mar 16 17:21 vmlinuz-5.4-x86_64

# bootctl
systemd-boot not installed in ESP.
No default/fallback boot loader installed in ESP.
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: user
 Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: - Boot counting
               - Menu timeout control
               - One-shot menu timeout control
               - Default entry control
               - One-shot entry control
               - Support for XBOOTLDR partition
               - Support for passing random seed to OS
               - Boot loader sets ESP partition information
          ESP: n/a
         File: `-n/a

Random Seed:
 Passed to OS: no
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/8e0b3250-e787-429f-97c5-ad49bb2bf06e)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0004

I need to call bootctl install to actually install it:

# bootctl install
Created "/boot/EFI".
Created "/boot/EFI/systemd".
Created "/boot/EFI/BOOT".
Created "/boot/loader".
Created "/boot/loader/entries".
Created "/boot/EFI/Linux".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".
Random seed file /boot/loader/random-seed successfully written (512 bytes).
Not installing system token, since we are running in a virtualized environment.
Created EFI boot entry "Linux Boot Manager".
# sdboot-manage gen

# bootctl
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: user
 Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: - Boot counting
               - Menu timeout control
               - One-shot menu timeout control
               - Default entry control
               - One-shot entry control
               - Support for XBOOTLDR partition
               - Support for passing random seed to OS
               - Boot loader sets ESP partition information
          ESP: n/a
         File: `-n/a

Random Seed:
 Passed to OS: no
 System Token: not set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/8e0b3250-e787-429f-97c5-ad49bb2bf06e)
         File: `-/EFI/systemd/systemd-bootx64.efi (systemd-boot 247.3-1-manjaro)
         File: `-/EFI/BOOT/BOOTX64.EFI (systemd-boot 247.3-1-manjaro)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0005`

# ls -l /boot
total 47568
drwxr-xr-x 5 root root     4096 Mar 16 17:27 EFI
-rwxr-xr-x 1 root root    40960 Feb 11 16:27 amd-ucode.img
-rwxr-xr-x 1 root root 30314187 Mar 16 17:21 initramfs-5.4-x86_64-fallback.img
-rwxr-xr-x 1 root root  8203205 Mar 16 17:21 initramfs-5.4-x86_64.img
-rwxr-xr-x 1 root root  3624960 Feb 17 08:15 intel-ucode.img
-rwxr-xr-x 1 root root       22 Feb 26 11:18 linux54-x86_64.kver
drwxr-xr-x 3 root root     4096 Mar 16 17:27 loader
drwxr-xr-x 2 root root     4096 Mar 16 17:21 memtest86+
-rwxr-xr-x 1 root root  6506816 Mar 16 17:21 vmlinuz-5.4-x86_64

After that, it works fine (it's successfully booting into the new system).