zuplo 7.8.24 → 7.9.2

package/docs/policies/{ai-gateway-configuration-executor-v2-inbound → ai-gateway-configuration-executor-inbound}/doc.md

@@ -1,10 +1,10 @@
 The AI Gateway Configuration Executor loads each application's configuration
-(when auth or `ai-gateway-configuration-loader-v2-inbound` has not already) and
+(when auth or `ai-gateway-configuration-loader-inbound` has not already) and
 runs its ordered inbound policy chain. Configuration comes from route-level
-`ai-gateway-auth-v2-inbound` or the configuration loader when either already
-ran, otherwise from the route's `app_id` path parameter via Gateway Service.
+`ai-gateway-auth-inbound` or the configuration loader when either already ran,
+otherwise from the route's `app_id` path parameter via Gateway Service.
 Applications can still require API keys later by including
-`ai-gateway-auth-v2-inbound` in their own `inboundPolicyChain`.
+`ai-gateway-auth-inbound` in their own `inboundPolicyChain`.
 
 Prefer placing the dedicated configuration loader before this executor on the
 route. When the loader is omitted, this executor still loads configuration
@@ -74,10 +74,10 @@ chooses the policies it needs in its `inboundPolicyChain`:
 {
   "policies": [
     {
-      "name": "ai-gateway-auth-v2-inbound",
-      "policyType": "ai-gateway-auth-v2",
+      "name": "ai-gateway-auth-inbound",
+      "policyType": "ai-gateway-auth",
       "handler": {
-        "export": "AIGatewayAuthV2InboundPolicy",
+        "export": "AIGatewayAuthInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -85,10 +85,10 @@ chooses the policies it needs in its `inboundPolicyChain`:
       }
     },
     {
-      "name": "ai-gateway-configuration-loader-v2-inbound",
-      "policyType": "ai-gateway-configuration-loader-v2",
+      "name": "ai-gateway-configuration-loader-inbound",
+      "policyType": "ai-gateway-configuration-loader",
       "handler": {
-        "export": "AIGatewayConfigurationLoaderV2InboundPolicy",
+        "export": "AIGatewayConfigurationLoaderInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -96,10 +96,10 @@ chooses the policies it needs in its `inboundPolicyChain`:
       }
     },
     {
-      "name": "ai-gateway-configuration-executor-v2-inbound",
-      "policyType": "ai-gateway-configuration-executor-v2",
+      "name": "ai-gateway-configuration-executor-inbound",
+      "policyType": "ai-gateway-configuration-executor",
       "handler": {
-        "export": "AIGatewayConfigurationExecutorV2InboundPolicy",
+        "export": "AIGatewayConfigurationExecutorInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -107,19 +107,19 @@ chooses the policies it needs in its `inboundPolicyChain`:
       }
     },
     {
-      "name": "ai-gateway-metering-v2-inbound",
-      "policyType": "ai-gateway-metering-v2",
+      "name": "ai-gateway-metering-inbound",
+      "policyType": "ai-gateway-metering",
       "handler": {
-        "export": "AIGatewayMeteringV2InboundPolicy",
+        "export": "AIGatewayMeteringInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {}
       }
     },
     {
-      "name": "ai-gateway-model-filtering-v2-inbound",
-      "policyType": "ai-gateway-model-filtering-v2",
+      "name": "ai-gateway-model-filtering-inbound",
+      "policyType": "ai-gateway-model-filtering",
       "handler": {
-        "export": "AIGatewayModelFilteringV2InboundPolicy",
+        "export": "AIGatewayModelFilteringInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "models": {
@@ -131,10 +131,10 @@ chooses the policies it needs in its `inboundPolicyChain`:
       }
     },
     {
-      "name": "ai-gateway-fallback-model-v2-inbound",
-      "policyType": "ai-gateway-fallback-model-v2",
+      "name": "ai-gateway-fallback-model-inbound",
+      "policyType": "ai-gateway-fallback-model",
       "handler": {
-        "export": "AIGatewayFallbackModelV2InboundPolicy",
+        "export": "AIGatewayFallbackModelInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "models": {
@@ -147,10 +147,10 @@ chooses the policies it needs in its `inboundPolicyChain`:
       }
     },
     {
-      "name": "ai-gateway-semantic-cache-v2-inbound",
-      "policyType": "ai-gateway-semantic-cache-v2",
+      "name": "ai-gateway-semantic-cache-inbound",
+      "policyType": "ai-gateway-semantic-cache",
       "handler": {
-        "export": "AIGatewaySemanticCacheV2InboundPolicy",
+        "export": "AIGatewaySemanticCacheInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "semanticTolerance": 0.4,
@@ -186,8 +186,8 @@ chain:
     },
     "policies": {
       "inbound": [
-        "ai-gateway-configuration-loader-v2-inbound",
-        "ai-gateway-configuration-executor-v2-inbound"
+        "ai-gateway-configuration-loader-inbound",
+        "ai-gateway-configuration-executor-inbound"
       ]
     }
   }
@@ -198,9 +198,9 @@ If you omit the loader, the executor loads the application configuration.
 
 Authentication is optional and placement controls its scope:
 
-- **App-level** — add `ai-gateway-auth-v2-inbound` to an application's
+- **App-level** — add `ai-gateway-auth-inbound` to an application's
   `inboundPolicyChain`. Only that application requires an API key.
-- **Route-level** — add `ai-gateway-auth-v2-inbound` on the route **before** the
+- **Route-level** — add `ai-gateway-auth-inbound` on the route **before** the
   loader (or before the executor on executor-only routes). That requires an API
   key for every application on the route.
 - **Internal applications** — for an application that is only called from inside
@@ -215,22 +215,22 @@ application-selected chains.
 ### 3. Set an application's policy chain
 
 An application can inherit the options from `policies.json`. Include
-`ai-gateway-auth-v2-inbound` when this application should require an API key:
+`ai-gateway-auth-inbound` when this application should require an API key:
 
 ```json
 {
   "inboundPolicyChain": [
     {
-      "name": "ai-gateway-auth-v2-inbound"
+      "name": "ai-gateway-auth-inbound"
     },
     {
-      "name": "ai-gateway-model-filtering-v2-inbound"
+      "name": "ai-gateway-model-filtering-inbound"
     },
     {
-      "name": "ai-gateway-fallback-model-v2-inbound"
+      "name": "ai-gateway-fallback-model-inbound"
     },
     {
-      "name": "ai-gateway-metering-v2-inbound",
+      "name": "ai-gateway-metering-inbound",
       "options": {
         "budgetRules": [
           {
@@ -248,7 +248,7 @@ An application can inherit the options from `policies.json`. Include
       }
     },
     {
-      "name": "ai-gateway-semantic-cache-v2-inbound"
+      "name": "ai-gateway-semantic-cache-inbound"
     }
   ]
 }
@@ -265,7 +265,7 @@ An application can also provide a complete options object for an entry:
 {
   "inboundPolicyChain": [
     {
-      "name": "ai-gateway-model-filtering-v2-inbound",
+      "name": "ai-gateway-model-filtering-inbound",
       "options": {
         "models": {
           "completions": {
@@ -290,7 +290,7 @@ under `permissions` fail closed:
 {
   "inboundPolicyChain": [
     {
-      "name": "ai-gateway-model-filtering-v2-inbound",
+      "name": "ai-gateway-model-filtering-inbound",
       "permissions": {
         "canEdit": true,
         "canRemove": false
@@ -366,8 +366,8 @@ distinct value gets its own budget.
 
 The expression grammar, the selectable properties, what a value must be, and
 what happens when an expression does not resolve are documented once, on the
-[AI Gateway Metering](/docs/policies/ai-gateway-metering-v2-inbound) policy
-page. The same grammar applies here.
+[AI Gateway Metering](/docs/policies/ai-gateway-metering-inbound) policy page.
+The same grammar applies here.
 
 Two things are specific to application configuration. A policy that sets a value
 an expression reads must run before Semantic Cache, which can answer without
@@ -426,7 +426,7 @@ every request. Add a `remove-headers-inbound` entry after the metering entry:
 ```json
 [
   { "name": "set-budget-dimension" },
-  { "name": "ai-gateway-metering-v2-inbound" },
+  { "name": "ai-gateway-metering-inbound" },
   {
     "name": "remove-headers-inbound",
     "options": { "headers": ["x-budget-customer"] }

package/docs/policies/{ai-gateway-configuration-executor-v2-inbound → ai-gateway-configuration-executor-inbound}/intro.md

@@ -5,8 +5,8 @@ Applications may also include authentication in their own chain. This makes it
 possible to offer different routing, caching, guardrail, metering, and tracing
 behavior from one AI Gateway deployment.
 
-Prefer placing `ai-gateway-configuration-loader-v2-inbound` before this executor
-on the route so loading and chain execution stay separate. When the loader is
+Prefer placing `ai-gateway-configuration-loader-inbound` before this executor on
+the route so loading and chain execution stay separate. When the loader is
 omitted, this executor still loads configuration itself.
 
 The gateway owner decides which policy declarations are available, while

package/docs/policies/{ai-gateway-configuration-executor-v2-inbound → ai-gateway-configuration-executor-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-configuration-executor-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-configuration-executor-inbound.json",
   "type": "object",
   "title": "AI Gateway Configuration Executor",
   "isDeprecated": false,
@@ -10,9 +10,9 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "ai-gateway-configuration-executor-v2",
+  "policyType": "ai-gateway-configuration-executor",
   "products": ["ai-gateway"],
-  "description": "Loads the app configuration for the request (when auth or the configuration loader has not already), runs the inbound policy chain from that configuration, and enforces limits inherited from parent teams or the gateway root.\n\nPlace this policy on AI Gateway routes after optional authentication and optional `ai-gateway-configuration-loader-v2-inbound`. When either of those already populated the app-configuration channel, this policy reuses it. Otherwise it loads the configuration with the route's `app_id` path parameter. Applications select from policies pre-declared by the gateway. Applications without a `inboundPolicyChain`, or with an empty chain, run no application-selected policies. Entry options replace the declaration's options as a complete object; omit them to inherit the declaration, including environment-backed credentials. Each occurrence receives a private deep copy of its entry options, so a policy mutating its options cannot corrupt the cached app configuration.",
+  "description": "Loads the app configuration for the request (when auth or the configuration loader has not already), runs the inbound policy chain from that configuration, and enforces limits inherited from parent teams or the gateway root.\n\nPlace this policy on AI Gateway routes after optional authentication and optional `ai-gateway-configuration-loader-inbound`. When either of those already populated the app-configuration channel, this policy reuses it. Otherwise it loads the configuration with the route's `app_id` path parameter. Applications select from policies pre-declared by the gateway. Applications without a `inboundPolicyChain`, or with an empty chain, run no application-selected policies. Entry options replace the declaration's options as a complete object; omit them to inherit the declaration, including environment-backed credentials. Each occurrence receives a private deep copy of its entry options, so a policy mutating its options cannot corrupt the cached app configuration.",
   "deprecatedMessage": "",
   "required": ["handler"],
   "properties": {
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AIGatewayConfigurationExecutorV2InboundPolicy",
+          "const": "AIGatewayConfigurationExecutorInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-configuration-executor-v2",
-          "title": "AIGatewayConfigurationExecutorV2InboundPolicyOptions",
+          "title": "AIGatewayConfigurationExecutorInboundPolicyOptions",
           "type": "object",
           "description": "Options for loading each application's AI Gateway configuration and running its inbound policy chain.",
           "additionalProperties": false,
@@ -41,14 +40,14 @@
               "type": "number",
               "default": 10,
               "minimum": 2,
-              "description": "The time in seconds to cache app configurations loaded by app\\_id. Defaults to 10 seconds when omitted. Higher values decrease latency; lower values pick up portal changes sooner. Cached results remain valid until the cache expires even if the configuration changes in the portal. This cache is only used when neither ai-gateway-auth-v2-inbound nor ai-gateway-configuration-loader-v2-inbound already loaded the configuration for the request."
+              "description": "The time in seconds to cache app configurations loaded by app\\_id. Defaults to 10 seconds when omitted. Higher values decrease latency; lower values pick up portal changes sooner. Cached results remain valid until the cache expires even if the configuration changes in the portal. This cache is only used when neither ai-gateway-auth-inbound nor ai-gateway-configuration-loader-inbound already loaded the configuration for the request."
             }
           }
         }
       },
       "examples": [
         {
-          "export": "AIGatewayConfigurationExecutorV2InboundPolicy",
+          "export": "AIGatewayConfigurationExecutorInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "cacheTtlSeconds": 10

package/docs/policies/{ai-gateway-configuration-loader-v2-inbound → ai-gateway-configuration-loader-inbound}/doc.md

@@ -1,15 +1,15 @@
 The AI Gateway Configuration Loader loads each application's configuration into
 the request-scoped app-configuration channel. Configuration comes from
-route-level `ai-gateway-auth-v2-inbound` when that policy already ran, otherwise
+route-level `ai-gateway-auth-inbound` when that policy already ran, otherwise
 from the route's `app_id` path parameter via Gateway Service.
 
 This policy does **not** run `inboundPolicyChain`. Pair it with
-`ai-gateway-configuration-executor-v2-inbound` when applications select policies
+`ai-gateway-configuration-executor-inbound` when applications select policies
 dynamically. If you omit this loader, the executor still loads configuration
 before running the chain.
 
 Applications can still require API keys later by including
-`ai-gateway-auth-v2-inbound` in their own `inboundPolicyChain`.
+`ai-gateway-auth-inbound` in their own `inboundPolicyChain`.
 
 ## Build an AI Gateway from scratch
 
@@ -22,10 +22,10 @@ Add the loader, the executor, and every policy an application may select to
 {
   "policies": [
     {
-      "name": "ai-gateway-configuration-loader-v2-inbound",
-      "policyType": "ai-gateway-configuration-loader-v2",
+      "name": "ai-gateway-configuration-loader-inbound",
+      "policyType": "ai-gateway-configuration-loader",
       "handler": {
-        "export": "AIGatewayConfigurationLoaderV2InboundPolicy",
+        "export": "AIGatewayConfigurationLoaderInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -33,10 +33,10 @@ Add the loader, the executor, and every policy an application may select to
       }
     },
     {
-      "name": "ai-gateway-configuration-executor-v2-inbound",
-      "policyType": "ai-gateway-configuration-executor-v2",
+      "name": "ai-gateway-configuration-executor-inbound",
+      "policyType": "ai-gateway-configuration-executor",
       "handler": {
-        "export": "AIGatewayConfigurationExecutorV2InboundPolicy",
+        "export": "AIGatewayConfigurationExecutorInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -70,8 +70,8 @@ Place the loader before the executor on each AI Gateway route:
     },
     "policies": {
       "inbound": [
-        "ai-gateway-configuration-loader-v2-inbound",
-        "ai-gateway-configuration-executor-v2-inbound"
+        "ai-gateway-configuration-loader-inbound",
+        "ai-gateway-configuration-executor-inbound"
       ]
     }
   }
@@ -80,17 +80,17 @@ Place the loader before the executor on each AI Gateway route:
 
 Authentication is optional and placement controls its scope:
 
-- **App-level** — add `ai-gateway-auth-v2-inbound` to an application's
+- **App-level** — add `ai-gateway-auth-inbound` to an application's
   `inboundPolicyChain`. Only that application requires an API key.
-- **Route-level** — add `ai-gateway-auth-v2-inbound` on the route **before** the
+- **Route-level** — add `ai-gateway-auth-inbound` on the route **before** the
   loader. That requires an API key for every application on the route.
 
 ### Executor-only routes
 
-Routes that list only `ai-gateway-configuration-executor-v2-inbound` keep
-working. The executor loads configuration when the channel is empty, then runs
-the chain. Use the dedicated loader when you want other route policies between
-load and chain execution, or a clearer separation of concerns.
+Routes that list only `ai-gateway-configuration-executor-inbound` keep working.
+The executor loads configuration when the channel is empty, then runs the chain.
+Use the dedicated loader when you want other route policies between load and
+chain execution, or a clearer separation of concerns.
 
 ## Configuration checklist
 

package/docs/policies/ai-gateway-configuration-loader-inbound/intro.md

@@ -0,0 +1,6 @@
+The AI Gateway Configuration Loader loads each application's configuration into
+the request-scoped channel — reusing the channel from route-level
+`ai-gateway-auth-inbound` when present, otherwise fetching by path `app_id`. It
+does not run the application's policy chain; place
+`ai-gateway-configuration-executor-inbound` after it for that. When this loader
+is omitted, the executor still loads configuration itself.

package/docs/policies/{ai-gateway-configuration-loader-v2-inbound → ai-gateway-configuration-loader-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-configuration-loader-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-configuration-loader-inbound.json",
   "type": "object",
   "title": "AI Gateway Configuration Loader",
   "isDeprecated": false,
@@ -10,9 +10,9 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "ai-gateway-configuration-loader-v2",
+  "policyType": "ai-gateway-configuration-loader",
   "products": ["ai-gateway"],
-  "description": "Loads the AI Gateway app configuration for the request into the request-scoped channel and does nothing else.\n\nPlace this policy on AI Gateway routes before `ai-gateway-configuration-executor-v2-inbound` when you want configuration loading separated from chain execution. When `ai-gateway-auth-v2-inbound` already populated the channel, this policy reuses it. Otherwise it loads the configuration with the route's `app_id` path parameter.\n\nIf this policy is omitted, the configuration executor still loads configuration itself before running the application chain.",
+  "description": "Loads the AI Gateway app configuration for the request into the request-scoped channel and does nothing else.\n\nPlace this policy on AI Gateway routes before `ai-gateway-configuration-executor-inbound` when you want configuration loading separated from chain execution. When `ai-gateway-auth-inbound` already populated the channel, this policy reuses it. Otherwise it loads the configuration with the route's `app_id` path parameter.\n\nIf this policy is omitted, the configuration executor still loads configuration itself before running the application chain.",
   "deprecatedMessage": "",
   "required": ["handler"],
   "properties": {
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AIGatewayConfigurationLoaderV2InboundPolicy",
+          "const": "AIGatewayConfigurationLoaderInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-configuration-loader-v2",
-          "title": "AIGatewayConfigurationLoaderV2InboundPolicyOptions",
+          "title": "AIGatewayConfigurationLoaderInboundPolicyOptions",
           "type": "object",
           "description": "Options for loading each application's AI Gateway configuration into the request-scoped channel.",
           "additionalProperties": false,
@@ -41,14 +40,14 @@
               "type": "number",
               "default": 10,
               "minimum": 2,
-              "description": "The time in seconds to cache app configurations loaded by app\\_id. Defaults to 10 seconds when omitted. Higher values decrease latency; lower values pick up portal changes sooner. Cached results remain valid until the cache expires even if the configuration changes in the portal. When ai-gateway-auth-v2-inbound already loaded the configuration for the request, this cache is not used."
+              "description": "The time in seconds to cache app configurations loaded by app\\_id. Defaults to 10 seconds when omitted. Higher values decrease latency; lower values pick up portal changes sooner. Cached results remain valid until the cache expires even if the configuration changes in the portal. When ai-gateway-auth-inbound already loaded the configuration for the request, this cache is not used."
             }
           }
         }
       },
       "examples": [
         {
-          "export": "AIGatewayConfigurationLoaderV2InboundPolicy",
+          "export": "AIGatewayConfigurationLoaderInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "cacheTtlSeconds": 10

package/docs/policies/ai-gateway-dlp-inbound/schema.json

@@ -30,7 +30,6 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-dlp",
           "type": "object",
           "title": "AIGatewayDlpInboundPolicyOptions",
           "description": "The options for the Data Loss Prevention (DLP) policy. Scans the content of AI requests and responses — system prompts, messages, and tool-call arguments — for sensitive data such as credit cards, national identifiers, and API keys, applying a per-rule action (mask, block, or log). Detection runs entirely inside the gateway; streaming responses are scanned as they stream (or collected and scanned whole with `streaming.mode: \"buffer\"`).",

package/docs/policies/{ai-gateway-fallback-model-v2-inbound → ai-gateway-fallback-model-inbound}/doc.md

@@ -34,10 +34,10 @@ A fallback that names the same model as the primary selection is skipped.
 
 ```json
 {
-  "name": "ai-gateway-fallback-model-v2-inbound",
-  "policyType": "ai-gateway-fallback-model-v2",
+  "name": "ai-gateway-fallback-model-inbound",
+  "policyType": "ai-gateway-fallback-model",
   "handler": {
-    "export": "AIGatewayFallbackModelV2InboundPolicy",
+    "export": "AIGatewayFallbackModelInboundPolicy",
     "module": "$import(@zuplo/runtime)",
     "options": {
       "models": {

package/docs/policies/{ai-gateway-fallback-model-v2-inbound → ai-gateway-fallback-model-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-fallback-model-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-fallback-model-inbound.json",
   "type": "object",
   "title": "AI Gateway Fallback Model",
   "isDeprecated": false,
@@ -10,7 +10,7 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "ai-gateway-fallback-model-v2",
+  "policyType": "ai-gateway-fallback-model",
   "products": ["ai-gateway"],
   "description": "Adds failure and quota fallbacks to an existing AI Gateway model selection.\n\nPlace this policy after AI Gateway Model Filtering. It never creates a model selection, so a misplaced policy cannot bypass filtering.",
   "deprecatedMessage": "",
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AIGatewayFallbackModelV2InboundPolicy",
+          "const": "AIGatewayFallbackModelInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,9 +30,8 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-fallback-model-v2",
           "type": "object",
-          "title": "AIGatewayFallbackModelV2InboundPolicyOptions",
+          "title": "AIGatewayFallbackModelInboundPolicyOptions",
           "description": "Options for adding failure and quota fallbacks to an existing AI Gateway model selection.",
           "additionalProperties": false,
           "required": ["models"],
@@ -110,7 +109,7 @@
       },
       "examples": [
         {
-          "export": "AIGatewayFallbackModelV2InboundPolicy",
+          "export": "AIGatewayFallbackModelInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "models": {

package/docs/policies/{galileo-tracing-v2-inbound → ai-gateway-galileo-tracing-inbound}/doc.md

@@ -18,10 +18,10 @@ traces:
 
 ```json
 {
-  "name": "galileo-tracing-v2-inbound",
-  "policyType": "galileo-tracing-v2",
+  "name": "ai-gateway-galileo-tracing-inbound",
+  "policyType": "ai-gateway-galileo-tracing",
   "handler": {
-    "export": "GalileoTracingV2InboundPolicy",
+    "export": "AIGatewayGalileoTracingInboundPolicy",
     "module": "$import(@zuplo/runtime)",
     "options": {
       "apiKey": "$env(GALILEO_API_KEY)",

package/docs/policies/{galileo-tracing-v2-inbound → ai-gateway-galileo-tracing-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/galileo-tracing-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-galileo-tracing-inbound.json",
   "type": "object",
   "title": "Galileo Tracing",
   "isDeprecated": false,
@@ -10,7 +10,7 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "galileo-tracing-v2",
+  "policyType": "ai-gateway-galileo-tracing",
   "products": ["ai-gateway"],
   "description": "Galileo Tracing Inbound Policy",
   "deprecatedMessage": "",
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "GalileoTracingV2InboundPolicy",
+          "const": "AIGatewayGalileoTracingInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "galileo-tracing-v2",
-          "title": "Galileo Tracing",
+          "title": "AIGatewayGalileoTracingInboundPolicyOptions",
           "description": "Track AI Gateway requests and responses using Galileo's LLM observability platform.",
           "type": "object",
           "examples": [
@@ -88,7 +87,7 @@
       },
       "examples": [
         {
-          "export": "GalileoTracingV2InboundPolicy",
+          "export": "AIGatewayGalileoTracingInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "apiKey": "$env(GALILEO_API_KEY)",

package/docs/policies/ai-gateway-internal-only-inbound/doc.md

@@ -44,15 +44,15 @@ Declare the policy in `config/policies.json`:
 ```
 
 Then select it in the application's `inboundPolicyChain` in place of
-`ai-gateway-auth-v2-inbound`. Put it first so nothing else runs for a rejected
+`ai-gateway-auth-inbound`. Put it first so nothing else runs for a rejected
 request:
 
 ```json
 {
   "inboundPolicyChain": [
     { "name": "ai-gateway-internal-only-inbound" },
-    { "name": "ai-gateway-model-filtering-v2-inbound" },
-    { "name": "ai-gateway-metering-v2-inbound" }
+    { "name": "ai-gateway-model-filtering-inbound" },
+    { "name": "ai-gateway-metering-inbound" }
   ]
 }
 ```

package/docs/policies/ai-gateway-internal-only-inbound/schema.json

@@ -30,7 +30,6 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-internal-only",
           "title": "AIGatewayInternalOnlyInboundPolicyOptions",
           "type": "object",
           "description": "The options for this policy. It has none.",

package/docs/policies/{ai-gateway-metering-v2-inbound → ai-gateway-metering-inbound}/doc.md

@@ -21,7 +21,7 @@ Semantic Cache so cache hits count toward request limits.
 
 ```json
 {
-  "name": "ai-gateway-metering-v2-inbound",
+  "name": "ai-gateway-metering-inbound",
   "options": {
     "throwOnFailure": false,
     "budgetRules": [

package/docs/policies/{ai-gateway-metering-v2-inbound → ai-gateway-metering-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-metering-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-metering-inbound.json",
   "type": "object",
   "title": "AI Gateway Metering",
   "isDeprecated": false,
@@ -10,7 +10,7 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "ai-gateway-metering-v2",
+  "policyType": "ai-gateway-metering",
   "products": ["ai-gateway"],
   "description": "Meters AI Gateway usage and enforces limits configured by the application.\n\nThe authentication policy must run before this policy so the app configuration id is available for meter storage and analytics.",
   "deprecatedMessage": "",
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AIGatewayMeteringV2InboundPolicy",
+          "const": "AIGatewayMeteringInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-metering-v2",
-          "title": "AIGatewayMeteringV2InboundPolicyOptions",
+          "title": "AIGatewayMeteringInboundPolicyOptions",
           "type": "object",
           "description": "Options for metering AI Gateway usage and enforcing request-time limits.",
           "additionalProperties": false,
@@ -338,7 +337,7 @@
       },
       "examples": [
         {
-          "export": "AIGatewayMeteringV2InboundPolicy",
+          "export": "AIGatewayMeteringInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "budgetRules": [