userofgos Yeah I took sometime to check now, while still not 100%, I'm fairly certain you understanding is incorrect.
Firstly, the g-docs on this:
Lock and unlock your private space
You can lock and unlock your private space with your device screen lock or with the private space lock that you set up.
When private space is locked:
The apps in the private space are:
Completely stopped. These apps can't perform foreground or background activities, like showing notifications.
When the device is locked, apps can't access sensor data or perform any functions [...]
Next, I'm not an Android dev - so could be making a mistake, but I can trace the source code to see that it actively kills apps:
See autoLockPrivateSpace -> calls setQuietModeEnabledAsync -> setQuietModeEnabled and that finally does killForegroundAppsForUser
LocalServices.getService(ActivityManagerInternal.class)
.killForegroundAppsForUser(userId);
This seems detached from any AFU/BFU thingy for private space. There are lot of variables - is this the correct code path, if so does GOS apply anything on top of this to change the behaviour for lock vs session-kill for private space, what about background apps/ipcs-wake-ups etc(though I'm fairly certain at this point that the OS won't just kill and stop things only to make them resumable via some shenanigan - I think they are all killed for good - but not sure), and so on.