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,68 @@
+//! `cd` tool: verify and resolve a workspace-relative directory path.
+use super::super::Tool;
+use super::super::ToolCtx;
+use anyhow::{anyhow, Result};
+use serde_json::{json, Value};
+
+/// Tool that resolves a workspace-relative path and reports whether it exists and is a dir.
+pub struct Cd;
+
+impl Tool for Cd {
+    fn name(&self) -> &'static str {
+        "cd"
+    }
+
+    fn description(&self) -> &'static str {
+        "Check if a directory exists within the workspace and print its resolved path. Use this to verify a directory path before running other commands there."
+    }
+
+    fn parameters(&self) -> Value {
+        json!({
+            "type": "object",
+            "properties": {
+                "path": {
+                    "type": "string",
+                    "description": "Directory path (relative to workspace root)"
+                }
+            },
+            "required": ["path"]
+        })
+    }
+
+    /// Resolve `path` against the workspace roots and report its status.
+    ///
+    /// Flow: extract `path` → `resolve_path` (sandboxed to `ctx.workspaces`) →
+    ///       check `exists()` and `is_dir()` → canonicalize → return canonical path.
+    ///
+    /// Why: the agent has no persistent cwd between tool calls; "cd" here is purely a
+    /// verification + canonicalization helper rather than a state change.
+    ///
+    /// Return: canonical path on success; explicit "does not exist" / "not a directory"
+    /// message (still `Ok`) so the model can react without treating it as an error.
+    fn run(&self, ctx: &ToolCtx, args: &Value) -> Result<String> {
+        let rel = args
+            .get("path")
+            .and_then(|v| v.as_str())
+            .ok_or_else(|| anyhow!("missing required argument: path"))?;
+
+        let path = super::super::resolve_path(&ctx.workspaces, rel)?;
+
+        if !path.exists() {
+            return Ok(format!(
+                "path '{}' does not exist (resolved to {})",
+                rel,
+                path.display()
+            ));
+        }
+        if !path.is_dir() {
+            return Ok(format!(
+                "path '{}' is not a directory (resolved to {})",
+                rel,
+                path.display()
+            ));
+        }
+
+        let canon = path.canonicalize().unwrap_or(path);
+        Ok(format!("{}", canon.display()))
+    }
+}