I was kind of surprised at the behaviour, mostly because of the superlatives ... fast app switching doesn't imply opening and closing to me since some apps are VERY slow to start up (excel, numbers, xcode, eclipse, )
You should make sure you are very clear about it CLOSING apps.
Also, the first time you should not close apps but instead ask the user if closing all the non-listed apps is ok. So the first time they run it the are not surprised by everything going away. Especially losing all my Chrome tabs :-(
You need a "stop list" so that apps in the list are not shutdown.
Other suggestions include - hotkeys - spotlight / alfred integration - Adding macros to launch when click a new set of apps
In other words, if I don't put terminal into an app group, it doesn't get closed, etc.
It sounds like you're forcefully killing processes - can you at least kill them more gracefully? Basically "kill" vs "kill -9".
From the docs, "attempts to quit the receiver normally." I'm not sure why ensorcled's terminal was closed while a process was running, but I get prompted to confirm closing terminal when a process is running.
The way it's supposed to work is, if you click on a horizontal row then it opens all the apps in that row (if they're not already open) and closes any apps that aren't in that row. So, for example, Terminal was closed because it sounds like it wasn't in your app group.
About "unsafely" - it should behave just as if you had hit command+q in the app. So if you have unsaved documents, the application should prompt you to save them.
Sorry again for the frustration it caused you!