refactor(cache): remove dead Cache._native_cache runtime path

litellm-rust/crates/python-bridge/Cargo.toml

@@ -29,17 +29,9 @@ litellm-host.workspace = true
 bytes.workspace = true
 futures-util.workspace = true
 litellm-cache.workspace = true
-litellm-cache-azure-blob.workspace = true
 litellm-cache-memory.workspace = true
 litellm-cache-redis.workspace = true
-litellm-cache-s3.workspace = true
-litellm-cache-gcs.workspace = true
-litellm-cache-disk.workspace = true
-litellm-cache-redis-semantic.workspace = true
 litellm-cache-response.workspace = true
-litellm-cache-qdrant-semantic.workspace = true
-qdrant-client.workspace = true
-litellm-cache-valkey-semantic = { path = "../cache-valkey-semantic" }
 serde.workspace = true
 litellm-auth.workspace = true
 litellm-auth-aws.workspace = true
@@ -63,7 +55,6 @@ strum.workspace = true
 veil.workspace = true
 thiserror.workspace = true
 tokio = { workspace = true, features = ["rt", "sync"] }
-url.workspace = true
 
 [dev-dependencies]
 tracing.workspace = true
@@ -75,7 +66,6 @@ criterion.workspace = true
 futures-util.workspace = true
 rstest.workspace = true
 sqlx = { workspace = true, features = ["migrate"] }
-sha2.workspace = true
 tokio-tungstenite.workspace = true
 wiremock.workspace = true
 aws-sdk-secretsmanager = "1.117.0"

litellm-rust/crates/python-bridge/src/cache/AGENTS.md

@@ -1,13 +1,7 @@
 # Cache boundary
 
-This folder owns Python cache API compatibility: argument projection, facade identity, public result construction, Python embedding calls and per-operation composition of native backends. Cache algorithms, storage protocols and response-cache semantics belong to their cache crates
+This folder owns how Rust inference reaches the selected cache: global cache selection, route admission, delegation to a Python cache and the experimental V2 native handles. Cache algorithms, storage protocols and response-cache semantics belong to their cache crates
 
-`mod.rs` exposes the cache boundary to routes and module registration; adapter directories remain private. `selection.rs` owns global cache selection, route admission and inference protocol composition for both adapters. `runtime.rs` exposes the Python-facing runtime that can wrap either native storage or a Python callback. `future.rs` converts cache results into ready Futures
+`mod.rs` exposes the cache boundary to routes and module registration; adapter directories remain private. `selection.rs` owns global cache selection, route admission and inference protocol composition for both adapters
 
-`python/` delegates operations to the selected Python cache without discovering configuration. `native/` owns native backend construction, configuration projection, facade validation, embedding and storage bindings, including experimental V2 handles. Neither adapter depends on shared selection or the other adapter. Shared composition depends on the adapters, and routes use only the parent module's exports
-
-`SemanticExecution` belongs here because its steps select cache operations and invoke the Python embedder. Use the shared `Execution` handle and inline lifecycle driver; do not duplicate coroutine state validation, runtime waiting or GIL machinery. Python embedding awaits stay in the caller's task, and cancellation must prevent later backend or batch operations from starting
-
-Resolved asyncio Future construction is generic host machinery. Use `litellm-host-python::ready_future` with an already constructed Python value. Keep cache-specific conversion and disabled-cache return values here. Preserve the Future-returning API and running-loop requirement
-
-Tests for Future mechanics belong in `host-python`; tests for disabled-cache values, embedding failure policy, batch sequencing and cancellation belong with this cache adapter. Assert public behavior rather than the location or name of a helper
+`python/` delegates operations to the selected Python cache without discovering configuration. `native/` owns the experimental V2 native cache handles. Neither adapter depends on shared selection or the other adapter. Shared composition depends on the adapters, and routes use only the parent module's exports

litellm-rust/crates/python-bridge/src/cache/mod.rs

@@ -1,12 +1,9 @@
-mod future;
 mod native;
 mod python;
-mod runtime;
 mod selection;
 
 pub(crate) use native::NativeCacheHandle;
 pub(crate) use python::{CacheCall, PythonCache};
-pub(crate) use runtime::ResolvedCache;
 pub(crate) use selection::{Cached, Selection, admit_native, configure, configured_native};
 
 use litellm_cache::Error;

litellm-rust/crates/python-bridge/src/cache/native/AGENTS.md

@@ -1,9 +1,9 @@
 # Native cache bindings
 
-This directory constructs and exposes Rust cache backends to Python. It owns backend configuration projection, facade validation, native request conversion, semantic embedding integration and experimental V2 handles. Cache algorithms and storage protocols remain in their cache crates
+This directory exposes the experimental V2 native cache handles (`NativeCacheHandle`) to Python. Cache algorithms and storage protocols remain in their cache crates
 
-Accept the cache object or projected configuration selected by the parent module. Do not read global `litellm.cache`, decide route admission, or select the Python cache adapter here
+Accept the cache object selected by the parent module. Do not read global `litellm.cache`, decide route admission, or select the Python cache adapter here
 
-Keep Python-facing cache classes and method signatures stable when reorganizing modules. Native internals stay private to this directory unless the shared cache boundary or Python module registration needs them. Python embedding awaits use the existing inline lifecycle driver, preserving caller task identity and cancellation
+Keep Python-facing cache classes and method signatures stable when reorganizing modules. Native internals stay private to this directory unless the shared cache boundary or Python module registration needs them
 
-Verify changes with the existing backend and facade tests using a freshly built extension. Test cache behavior, not module paths or file structure
+Verify changes with the V2 cache tests using a freshly built extension. Test cache behavior, not module paths or file structure