Setting inst.ksstrict is your enemy - that sets all warnings to errors and just bails out. You can switch to a console or various logs by hitting alt-f2 (etc) if you undo that.
if its sitting their its probably not finding a storage device or something.
in case it is your custom iso, maybe try just installing @^minimal-environment from the regular dvd/minimal iso instead of all those other package groups, won’t need internet access for that.
why use a custom iso when you’re injecting the kickstart into the initrd anyway - in fact that could be your problem, you’ve got two kickstart sources.
it could be that its not finding the packages, i’ve done this a few times when i’m serving up the kickstart over http and need to tell it on which disk to find the packages:
harddrive --partition=LABEL=AlmaLinux-9-2-aarch64-dvd --dir=/
harddrive --partition=LABEL=AlmaLinux-9-5-aarch64-dvd --dir=/
harddrive --partition=LABEL=AlmaLinux-10-0-beta1-aarch64-dvd --dir=/
i’m not sure if i’ve ever done a custom boot cd that’s also got the packages on, i’d use an internal mirror for that otherwise the iso ends up massive.