Migrate host-list to Q

[Mookse]

Hosted List updated on create-account and should migrate to Q; in fact, to be a platform/system Avatar, you've got to prepare all the goods. Not yet ready to move session management in, but for now, identify any server functionality

• hostedMember
  • functions.mjs -> ctx.state.avatar.hostedMembers(key)
  • mylife-avatar.mjs add function async hostedMembers(key)'
  • add to this.#hostedMembers when account created
  • any MyLife instance must be able to host its own subset of members for distributed technology viability
  • note: ultimately there will be some donation scheme, but a member avatar is unlikely to ever "host" membership because by abstracting to that level it runs the risk of being indebted bondage for access (or the illusion of such could be presented)... Correct! humans can host systems that host humans, but humans (core) cannot host humans (core).
    • Open to all suggestions that would minimize exploitation of even that locally hosted member bondage (other than flatly abandoning distributed architectural notion); it may be too early to entertain, as frontend improvements and intelligence-derived obvious alternatives may well arise, and can certainly be infused into the central codebase a capacity to help individuals remediate such conditions and this knowledge would be available to their avatar which is always the central core. What? now you're asking about how to protect the fidelity and access of a crypto-level db-falsifiers?
• router/routes (already steals from Q or even System Avatar -> CORRECT frontend manipulation of menus was also through this mechanic - shouldn't have deviated too far, but stubs still operable!). Demonstrates minimal way to accomplish:
  • const serverRouter = await _Maht.router
    • note that this operates under the dependency injection reverse model, where attached intelligence
    • MyLife Avatar: the liberty, in eco - the privilege, and in exo the right to request consent
• session management - may be a ways off?
• Q-Hosting Key - corporate avatars should have internal key field that identifies them to system for handshake
  • currently process.env.MYLIFE_HOSTING_KEY compared against avatar field for org hosting_key