refactor(workspace)!: move MCP crates under crates/mcp/ and update paths

crates/mcp/client/Cargo.toml

@@ -0,0 +1,12 @@
+[package]
+name = "owlen-mcp-client"
+version = "0.1.0"
+edition.workspace = true
+description = "Dedicated MCP client library for Owlen, exposing remote MCP server communication"
+license = "AGPL-3.0"
+
+[dependencies]
+owlen-core = { path = "../../owlen-core" }
+
+[features]
+default = []

crates/mcp/client/src/lib.rs

@@ -0,0 +1,17 @@
+//! Owlen MCP client library.
+//!
+//! This crate provides a thin façade over the remote MCP client implementation
+//! inside `owlen-core`. It re‑exports the most useful types so downstream
+//! crates can depend only on `owlen-mcp-client` without pulling in the entire
+//! core crate internals.
+
+pub use owlen_core::config::{McpConfigScope, ScopedMcpServer};
+pub use owlen_core::mcp::remote_client::RemoteMcpClient;
+pub use owlen_core::mcp::{McpClient, McpToolCall, McpToolDescriptor, McpToolResponse};
+
+// Re‑export the core Provider trait so that the MCP client can also be used as an LLM provider.
+pub use owlen_core::Provider as McpProvider;
+
+// Note: The `RemoteMcpClient` type provides its own `new` constructor in the core
+// crate. Users can call `RemoteMcpClient::new()` directly. No additional wrapper
+// is needed here.