Note that this package provides init-switcher and a tool that makes systemd wrapped commands (use systemd commands into an openrc system, in a compatible way, but not much tested)
Yeah i noticed that, but can be a fallback because the init system changed, nothing really important
yes I saw that too, i don't know what is the cause, didn't tried to google or search info yet 
we are talking only about the init-switcher or also the upgrade mode or the re-installation ? because the init-switcher should NOT do all these things:
- you can run init-switcher again to systemd and switch between them safely, but use it without the -y option so you can see (and confirm) what is going to install or remove, then verify that is not going to delete your enlightenment packages (of course you need to reinstall them again now first) - about the lightdm autologin same thing: the init-switcher has no reason to do that, but maybe the reinstall or upgrader did (we need to know which step did it) by replacing conf files, make a look to the /etc confs for lightdm to see if they has been modified, maybe you have backups or a backup of /etc.bak-somthing
- mmmh again thats not possible from init-switcher (unless uninstalled some packages), that should have been caused by the re-install ?
ok yes, that's because the E16 trigger of elive-pm doesn't wait for it to finish and straight logout the desktop
but more importantly: it should not ask you this prompt, your user should have the right (permissions) to reboot the computer without sudo password, so either:
- you created the user without permissions (which checkboxes you selected ? i always enable all of them in my tests)
- your system is not well configured to give him these permissions
so the gksu is doing its job for the users that has no permission (thats very good, expected, and well working), but the question is why your user cannot reboot (is this an expected/wanted behaviour?)
I don't think e16 is doing that wrongly, but is a small thing that should be brainstorm with the E16 dev I think
from init-switcher ? ok good... we need to know now "why" 
can you play again with init-switcher back and forth systemd/openrc as mentioned previously ?
are you running out of free space ? elive has an emergency cleanup of caches and some files if your disk is very low on space, could have been this the cause ? i don't know another reason of this can be - see below
shortly: we should not betatest much e27 yet, i have not finished to implement / integrate it at the moment, it only includes "a setup of hotkeys + a usable theme + startup scripts that are not fully migrated not for trixie nor for e27", the thing about the reboot/shutdown is that I don't even know which triggers uses (system reboots? elive-pm probably not ? systemd commands very likely? but then what when openrc?, etc..)
make a look to your files in /etc/enlightenment/ because its problably using these ones
eventually e27 must use elive-pm (try to set these files to use it), because elive-pm is the trigger that should agnostically accept and manage every environment
this message is from setvolume, run this:
export EL_DEBUG=3
setvolume defaults
if you don't see anything, add an "set -x" at the start of the script and try again, try to catch what is the thing that makes it -think- that audio is not working, so we can fix it (or just paste the set -x contents in a pastebin website so i can analize them and fix, that's more fast)
Also, something that needs to be brainstormed a bit for trixie... Alsa, Pulseaudio, Pipewire... which one to choose?
always forget the first shutdown on switch, you are shutting down a "broken" system to reboot it in the new init system
ok so this basically means that openrc requires you permissions to reboot the machine while in systemd it has these permissions (systemd has its own power commands, and user permissions management), we need to clearly state this issue as if this is what is happening or another thing, + knowing your settings of permissions in user creation time (the checkboxes)
ok wait, that can be because of "browsers on ram" feature, interesting... because it requires systemd, so probably is lefting your profile managed by systemd "orphaned", let me try to fix it...
ok so if you apug and run again init-switcher, it should disable your "browsers on ram" before to switch to openrc, retaining it to work correctly after to boot into openrc (rebuilding, wait 30 min after this post)
But then we still need to implement it correctly for openrc (and this is a requeriment for many other things too), but because of that very specific topic and need, I opened a new thread OpenRC: Daemons run by user
mmh, probably "setvolume" deleted your previous audio card configuration trying to reconfigure it (because it detected that your audio card was not working)
in fact e16 could have been due by the reboot, not sure... make sure to always have backups of e16 and other possible things that you customize, thats very simple by entering in the directory from a terminal and running "bkp save" (note that you cannot change e16 confs on the fly, e16 ignore your manual changes, except for the apps .list and bindings file)
about elive-pm (very explained previously), but I think that we should list well all the bugs in openrc to make it fully compatible working, so let's try to fix the things one to one slowly... read my previous comments and let's progress until theres no more bugs