fix: replace Venice custom provider with declarative config

crates/goose/src/providers/declarative/venice.json

@@ -0,0 +1,25 @@
+{
+  "name": "venice",
+  "engine": "openai",
+  "display_name": "Venice.ai",
+  "description": "Venice.ai models (Llama, DeepSeek, Mistral) with function calling",
+  "api_key_env": "VENICE_API_KEY",
+  "base_url": "https://api.venice.ai/api/v1/chat/completions",
+  "models": [
+    {
+      "name": "llama-3.3-70b",
+      "context_limit": 131072
+    },
+    {
+      "name": "llama-3.2-3b",
+      "context_limit": 131072
+    },
+    {
+      "name": "mistral-31-24b",
+      "context_limit": 131072
+    }
+  ],
+  "dynamic_models": true,
+  "supports_streaming": true,
+  "model_doc_link": "https://docs.venice.ai/"
+}

crates/goose/src/providers/init.rs

@@ -35,7 +35,6 @@ use super::{
     provider_registry::ProviderRegistry,
     snowflake::SnowflakeProvider,
     tetrate::TetrateProvider,
-    venice::VeniceProvider,
     xai::XaiProvider,
 };
 use crate::config::ExtensionConfig;
@@ -84,7 +83,6 @@ async fn init_registry() -> RwLock<ProviderRegistry> {
         registry.register::<SageMakerTgiProvider>(false);
         registry.register::<SnowflakeProvider>(false);
         registry.register::<TetrateProvider>(true);
-        registry.register::<VeniceProvider>(false);
         registry.register::<XaiProvider>(false);
     });
     // Register cleanup functions for providers with cached state

crates/goose/src/providers/mod.rs

@@ -54,7 +54,7 @@ pub mod tetrate;
 pub mod toolshim;
 pub mod usage_estimator;
 pub mod utils;
-pub mod venice;
+
 pub mod xai;
 
 pub use init::{