It does work for me, so something must be off. I did work up to it in stages, to make sure I’d done everything right. As Chris suggests, run from the Terminal first. I also started out with a 1 minute sleep, so I made sure I was seeing the ‘notify’.
When you think it actually should be running, check that it is with ‘ps’, or the ProcessController.
One other thing to know is that the launching is done via UserBootScript, so check that is correct. A while back I too was puzzled that nothing was launching… until I looked at UserBootScript and found it was still referencing ~/config/boot/launch! It should look like:
# DO NOT EDIT!
# Start programs and open files in the boot launch folder
for file in $HOME/config/settings/boot/launch/*
/bin/open "$file" &
ADDENDUM: I meant to add that I think that last is an Ooh-nasty misstep! A file labelled “UserBootScript” should be exclusively for user customization. If something is put in the 'launch" folder, I’d expect the system to take care of it. And of course there’s a /boot/system/data/user_launch/user script that invokes UserBootScript itself, so that’s where the launch folder launching should be done too.