chat-system

# Chat System ## Sources - `docs/chat.md` — Chat architecture (MVP, state machine, commands, services, event bus, auto-translation) - `docs/chat-emojis.md` — Emoji atlas creation with TextMesh Pro, noto-emoji font - `docs/chat-history-local-storage.md` — Local encrypted chat history persistence, feature flag control --- ## Architecture Overview The chat system uses **MVP + State Machine + EventBus + Commands**: - **View** (MonoBehaviour): draw-only; forwards UI events - **Presenter** (POCO): listens to View + EventBus, delegates to Commands/Services, updates View - **Model**: embodied by Services and data stores (`IChatHistory`) - **Commands**: single-purpose business logic (e.g., `SendMessageCommand`) - **Services**: long-lived shared state or I/O boundaries (history, member lists, input blocking) - **EventBus**: decoupled comms via `ChatEvents` (no tight coupling between Presenters) - **State Machine**: `ChatStateMachine` controls top-level UI mode; replaces boolean soup - **Composition root**: `ChatPlugin` wires Views, Presenters, Commands, Services, and State Machine ### Component Map | Layer | Key Classes | |-------|------------| | Composition | `ChatPlugin`, `ChatMainSharedAreaController` | | Presenters | `ChatPanelPresenter`, `ChatTitlebarPresenter`, `ChatInputPresenter`, `ChatMessageFeedPresenter`, `ChatChannelsPresenter`, `ChatMemberListPresenter` | | Commands | `SendMessageCommand`, `SelectChannelCommand`, `InitializeChatSystemCommand`, `GetMessageHistoryCom...