[Feature]Add Matrix as a Channel Entry Point

[mwnu]

Is your feature request related to a problem? Please describe.
Dotcraft supports interacting with the agent via various messaging channels. Currently, users who rely on open, self-hosted, or decentralized communication protocols don't have a native channel to interact with their workspace agent.

Describe the solution you'd like
I propose adding Matrix as a supported Channel Entry Point. This would allow users to communicate with their dotcraft agent directly through Matrix clients (like Element).

Why Matrix?

1. Open Source & Developer Friendly: Matrix is a highly popular protocol among developers, perfectly matching dotcraft's target audience.
2. Privacy & Self-Hosting: Users who care about data ownership often host their own Matrix homeservers. Allowing them to route their AI interactions through Matrix keeps their data within their control.
3. Seamless Integration: It fits perfectly into the existing architecture of interacting with the agent via external IMs, similar to the existing Telegram or WeChat implementations.

Describe alternatives you've considered
Users currently have to rely on bridging solutions (e.g., Matrix-to-Telegram bridges) to interact with the agent, which adds unnecessary latency, complexity, and potential points of failure. Native integration would be much more reliable.

[AkiKurisu]

Could you provide the GitHub repository url for Matrix?

[mwnu]

Could you provide the GitHub repository url for Matrix?

Matrix is actually an open standard and protocol for decentralized communication (similar to how Email works), rather than a single software repository. To help you understand the ecosystem:

1. Official Matrix Specification & Documentation:

• URL: https://github.com/matrix-org/matrix-spec
• Description: The core specification repository for the Matrix protocol if you need to look into underlying room events and API structures.

2. The Ecosystem (For context & understanding):

• [matrix-org/synapse](https://github.com/matrix-org/synapse): The most popular backend homeserver implementation. Users host this to own their data.
• [element-hq/element-web](https://github.com/element-hq/element-web): The most popular flagship client (UI) that users use to chat, analogous to how people use Outlook or Gmail for emails.

3. The Integration (For dotcraft development):
To build a Matrix Channel Entry Point for dotcraft, you don't need to touch the server or client repositories above. You only need a Node.js/TypeScript SDK to connect dotcraft to a Matrix room. I highly recommend looking at these two:

• [turt2live/matrix-bot-sdk](https://github.com/turt2live/matrix-bot-sdk): A high-level TypeScript SDK specifically designed for building bots and appservices. This is likely the fastest way to implement the channel routing.
• [matrix-org/matrix-js-sdk](https://github.com/matrix-org/matrix-js-sdk): The official, more low-level JavaScript/TypeScript SDK.

For testing during development, you can simply create a free account on matrix.org using the Element client, and use the Bot SDK to write a script that connects dotcraft to your test room.

Given dotcraft's architecture, using matrix-bot-sdk or the official matrix-js-sdk would be the quickest path to wire Matrix up as a new Channel Entry Point.