launchd under Sonoma

Having some problems with launchd since I upgraded to Sonoma.

First some background. I run a secondary userid which is logged in whenever the Mac is turned on. At startup it logs in. It contains a launchd file to run at load & lock the user, in case my Mac falls into the wrong hands. It also contains two launchd files which run an app at load & daily at 2PM.
All the above worked reliably under Ventura.
Focusing on the launch process now. I noticed the app was not starting up at login. Suspected that two launchd run at launch files may be a problem. So, as a test, I renamed (plist > xml) so that only the app would run at launch.
When I tested it. my app did not launch, but the renamed file which locks the id still ran. Strange. Any insights as to what's happening? Thanks.

I have observed a more onerous behavior from the ManagedClient, which I suspect is related. There seem to be processes that launchctl no longer has any control over. To date I have found no clear documentation, though I am experiencing these hangups as Orwellian.

launchd under Sonoma
 
 
Q