Refactor/rewrite Mom

[badlogic]

The project is a pig, and not very well structured. But it allowed contributors and myself to get a feel for how it should be structured. Just some general observations and thoughts from my end.

The packages/mom/docs folder has a bunch of explorations, specifically wrt the sandbox mom can execute bash in. I would love to be able to package mom as a self-contained thing, so end users don't need to install Docker or any other virtualization machinery.

Qemu seems to be the path of least resistent.

@nicobailon has also done some excellent Discord exploration (https://github.com/badlogic/pi-mono/pull/188), which has a much richer API to work with, specifically wrt custom TUI. For Slack, we could look into BlockIt. The agentic code shouldn't care about the UI at all, the chat app adapters need to turn whatever the agentic core returns into the best possible chat app specific UI.

Related and now closed issues and PRs: https://github.com/badlogic/pi-mono/issues/63 https://github.com/badlogic/pi-mono/pull/132 https://github.com/badlogic/pi-mono/issues/184 https://github.com/badlogic/pi-mono/pull/187 https://github.com/badlogic/pi-mono/pull/188 https://github.com/badlogic/pi-mono/pull/189 https://github.com/badlogic/pi-mono/pull/237

We might also steal some ideas from @steipete 's Clawdis project, specifically wrt concurrent direct message and context handling. The difference between Clawdis and mom is that mom is more focused on "business-y" things in teams, rather than personal assistant tasks (with a personality). And it should be super simple to setup, as simple as the silly bot settings each chat app lets you set let us make it. Including the exeuction container.