refactor: migrate monolithic crate to Cargo Workspace with Clean Architecture

Transform the single binary crate into a 9-crate workspace monorepo: - Root Cargo.toml as [workspace] manager with resolver = "2" - zesdex-entities: Domain entity types (session, settings, store, message, etc.) - zesdex-utils: Pure utility functions (error, logger, pagination, slug, clipboard) - zesdex-dto: Data Transfer Objects for LLM provider API communication - zesdex-ipc: Unix-socket IPC layer (client/server/framing/protocol) - zesdex-iam: Identity & Access Management (Clean Architecture: domain/application/infrastructure) - zesdex-cms: Content Management (Clean Architecture: domain/application/infrastructure) - zesdex-middleware: HTTP middleware (Auth, CORS, Rate Limiting) - zesdex-libs: Composition root (AppContext, DB init, JWT, Argon2) - zesdex-backend: Main binary entry point + seed/migrate binaries - DevOps: Dockerfile, docker-compose, Nix (flake/shell/default), CI/CD updates - Remove dead root src/ and src-misc/ directories All crate re-exports maintain backward compatibility with original crate::model::*, crate::dto::*, crate::ipc::* module paths. Feature crates enforce strict layer separation: domain -> application -> infrastructure with generic trait-based dependency injection.
2026-07-17 09:08:41 +07:00
parent 86cc412395
commit be0a9582bb
248 changed files with 7901 additions and 1505 deletions
@@ -0,0 +1,62 @@
+//! Conversation use-case implementations.
+//!
+//! `ConversationServiceImpl` is generic over `R: ConversationRepository`,
+//! delegating all persistence to that adapter.
+
+#![allow(
+    clippy::cast_possible_truncation,
+    clippy::cast_sign_loss,
+    clippy::cast_precision_loss,
+    clippy::cast_possible_wrap
+)]
+
+use anyhow::{Context, Result};
+
+use crate::domain::conversation::{ChatMessage, Conversation};
+use crate::domain::repository::ConversationRepository;
+use crate::domain::service::ConversationService;
+
+/// Generic conversation service backed by an injected repository.
+pub struct ConversationServiceImpl<R> {
+    pub repo: R,
+    pub sessions_dir: std::path::PathBuf,
+}
+
+impl<R: ConversationRepository> ConversationServiceImpl<R> {
+    /// Create a new service with the given repository and sessions directory.
+    pub fn new(repo: R, sessions_dir: impl Into<std::path::PathBuf>) -> Self {
+        Self {
+            repo,
+            sessions_dir: sessions_dir.into(),
+        }
+    }
+
+    /// Compute the session directory for a given session id.
+    fn session_dir(&self, session_id: &str) -> std::path::PathBuf {
+        self.sessions_dir.join(session_id)
+    }
+}
+
+impl<R: ConversationRepository> ConversationService for ConversationServiceImpl<R> {
+    fn load_conversation(&self, session_id: &str) -> Result<Conversation> {
+        let dir = self.session_dir(session_id);
+        self.repo
+            .load(&dir)
+            .with_context(|| format!("failed to load conversation for session '{session_id}'"))
+    }
+
+    fn save_conversation(&self, conv: &Conversation) -> Result<()> {
+        let dir = self.session_dir(&conv.session_id);
+        self.repo
+            .save(&dir, conv)
+            .with_context(|| format!("failed to save conversation for session '{}'", conv.session_id))
+    }
+
+    fn add_message(&self, conv: &mut Conversation, msg: ChatMessage) -> Result<()> {
+        conv.push(msg);
+        let dir = self.session_dir(&conv.session_id);
+        self.repo
+            .save(&dir, conv)
+            .with_context(|| format!("failed to persist conversation after adding message for session '{}'", conv.session_id))
+    }
+}