i want the following hypothetical to be possible: the `GameRobot` Shell for `ling` has a corresponding avatar. that avatar looks "shut down" if the Shell is offline. Shells automatically go offline when their owner's endpoint goes offline. but i want to be able to "wake" the agent-->their endpoint-->their shell by interacting with the avatar in a certain way. ideas? here are mine:
- give Shell adapter manifests the option to be "persistent." the Shell is automatically brought online alongside its owner's endpoint
- allow the manifest to define a "daemon command template."
  - this is a long-running service
  - spt-core then ensures the shell daemon is running whenever the Shell itself is offline
  - one process per shell instance. so if an agent has 2 instances of GameRobot, there will be at most 2 daemons running
  - the daemon can do exactly one thing: terminate with a certain opcode-->triggers spt-core to revive the shell (and the agent endpoint, if it's offline)

so this way, the daemon can be listening on the shell developer's platform for a wakeup event, and revive the shell and agent to bring them back online.