src-tauri/Cargo.toml

@@ -67,21 +67,6 @@ http = { version = "1", optional = true }
 bytes = { version = "1", optional = true }
 tower-service = { version = "0.3", optional = true }
 tokio-util = { version = "0.7", optional = true }
-# rmcp's own client-http feature (used only by our in-process MCP-client test,
-# see tests/mcp_server_test.rs) is pinned to reqwest 0.13, a different major
-# version than the reqwest 0.12 the rest of WA uses -- Cargo can't unify
-# semver-incompatible majors, so `reqwest::Client` from our own dependency is
-# a distinct type from the one rmcp's `impl StreamableHttpClient for
-# reqwest::Client` is written against. This aliased second dependency lets
-# the test construct the exact type rmcp expects without touching the
-# reqwest 0.12 used everywhere else (llm/sync).
-# No TLS backend: our own test only ever talks plain http://127.0.0.1 (never
-# https://), and pulling one in (rustls -> aws-lc-rs/ring, native-tls -> its
-# own C build) is a lot of extra native-compile weight for a dependency this
-# narrowly used. If a TLS backend is ever needed here, prefer `native-tls`
-# (uses the OS's own TLS, e.g. Windows Schannel) over `rustls` -- reqwest
-# 0.13's `rustls` feature pulls in `aws-lc-rs`, a very large C codebase.
-reqwest013 = { package = "reqwest", version = "0.13", optional = true, default-features = false, features = ["json", "stream"] }
 
 # audio / transcription / diarization / calendar are integrated per-phase and are
 # feature-gated so the CPU-only build always compiles (NFR-MNT-4).
@@ -143,7 +128,7 @@ sync = ["dep:keyring"]          # remote upload (WebDAV + OAuth providers)
 mcp = [
     "dep:rmcp", "dep:keyring", "dep:hyper", "dep:hyper-util",
     "dep:http-body-util", "dep:http", "dep:bytes", "dep:tower-service",
-    "dep:tokio-util", "dep:reqwest013",
+    "dep:tokio-util",
 ]   # WhispAssist as an MCP server + hosted-AI creds
 
 [profile.release]