zuplo 7.3.2 → 7.4.3

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

@@ -1,9 +1,9 @@
 # AI Gateway Metering
 
-AI Gateway Metering records application usage and enforces budgets before the
-provider request runs. It meters spend, tokens, and requests. Each meter has
-independent daily and monthly periods and an optional warning threshold that
-notifies without blocking.
+AI Gateway Metering records application usage and configures the app's own
+budgets before the provider request runs. It meters spend, tokens, and requests.
+Each meter has independent daily and monthly periods and an optional warning
+threshold that notifies without blocking.
 
 When a limit is exceeded, the policy activates the model selection's
 `quotaFallback` when AI Gateway Fallback Model supplied one. Otherwise it
@@ -52,16 +52,16 @@ The supported meters are `costs`, `tokens`, and `requests`. Each meter can have
 
 ## Team limits
 
-Limits configured on a parent team or the bucket root are enforced automatically
-through a server-side hierarchical check against aggregated usage. The
-`options.limits` settings govern only the app running this policy; the server
-walks the ancestor chain and reports the first exceeded limit.
+The `options.limits` settings govern only the app running this policy. Limits
+configured on a parent team or the gateway root are enforced centrally after the
+application's policy chain, whether or not this policy appears in that chain. An
+inherited limit activates the selected model's quota fallback when available and
+otherwise returns `429 Too Many Requests`.
 
-An exceeded team or gateway limit follows the same configured model-fallback or
-429 response path as an app limit. Ancestor enforcement cannot be disabled from
-the app's policy-chain entry. When the hierarchical check is unavailable,
-`throwOnFailure` controls the behavior: the default skips enforcement for that
-request while continuing to meter it, and `true` fails the request.
+An application cannot disable inherited enforcement through its policy chain. If
+the central hierarchical check is unavailable, the request proceeds. The
+policy's `throwOnFailure` option controls failures while checking or recording
+the app's own limits; it does not change inherited-limit behavior.
 
 ## Set limits from custom code
 

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

@@ -12,7 +12,7 @@
   "requiresAI": true,
   "policyType": "ai-gateway-metering-v2",
   "products": ["ai-gateway"],
-  "description": "Meters AI Gateway usage and enforces app and ancestor usage limits.\n\nLimits configured on parent teams or the bucket root are enforced through a server-side hierarchical check.\n\nThe authentication policy must run before this policy so the app configuration id is available for meter storage and analytics.",
+  "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": "",
   "required": ["handler"],
   "properties": {

package/docs/programmable-api/environment.mdx

@@ -4,7 +4,7 @@ sidebar_label: Environment Variables
 ---
 
 The `environment` object provides access to environment variables in your Zuplo
-API gateway. It returns a record of environment variable names to their values.
+Gateway. It returns a record of environment variable names to their values.
 
 :::info{title="Configuration Guide"}
 

package/docs/programmable-api/jwt-service-plugin.mdx

@@ -30,7 +30,7 @@ Some of the common use cases for the JWT service plugin include:
 
 - Securing downstream APIs by issuing JWTs that can be used to verify that the
   request is coming from your Zuplo API
-- Securing requests to other Zuplo API gateways (for example, when using the
+- Securing requests to other Zuplo Gateways (for example, when using the
   [Federated Gateway](../dedicated/federated-gateways.mdx) capability on Zuplo
   managed dedicated deployments.)
 - Calling third-party APIs that can be configured with federated identity such

package/docs/programmable-api/logger.mdx

@@ -3,7 +3,7 @@ title: Logger
 ---
 
 The `Logger` interface provides structured logging capabilities throughout your
-Zuplo API gateway. The logger is accessible via the `context.log` property and
+Zuplo Gateway. The logger is accessible via the `context.log` property and
 supports multiple log levels.
 
 ## Interface

package/docs/programmable-api/runtime-errors.mdx

@@ -3,7 +3,7 @@ title: Runtime Errors
 ---
 
 Zuplo provides specialized error classes for handling runtime and configuration
-errors in your API gateway.
+errors in your Zuplo Gateway.
 
 ## RuntimeError
 

package/docs/programmable-api/zuplo-context.mdx

@@ -266,9 +266,9 @@ export default async function (request: ZuploRequest, context: ZuploContext) {
 
 ### `invokeRoute`
 
-Invokes another route within the same API gateway. This enables internal routing
-and composition of multiple routes. The invoked route runs with a new context
-that has `parentContext` set to the current context.
+Invokes another route within the same Zuplo Gateway. This enables internal
+routing and composition of multiple routes. The invoked route runs with a new
+context that has `parentContext` set to the current context.
 
 ```ts
 export default async function (request: ZuploRequest, context: ZuploContext) {

package/docs/self-hosted/overview.md

@@ -4,9 +4,9 @@ sidebar_label: Overview
 ---
 
 Zuplo Self-Hosted (also known as on-prem) is a deployment model where you run
-the Zuplo API Gateway on your own infrastructure — any cloud or private data
-center. Zuplo Self-Hosted runs exclusively on Kubernetes and is installed with a
-single Helm chart into your cluster.
+the Zuplo Gateway on your own infrastructure — any cloud or private data center.
+Zuplo Self-Hosted runs exclusively on Kubernetes and is installed with a single
+Helm chart into your cluster.
 
 Self-hosted deployment might be the right choice for you if you need:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.3.2",
+  "version": "7.4.3",
   "type": "module",
   "description": "The programmable API Gateway",
   "author": "Zuplo, Inc.",
@@ -19,9 +19,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.3.2",
-    "@zuplo/core": "7.3.2",
-    "@zuplo/runtime": "7.3.2",
-    "@zuplo/test": "7.3.2"
+    "@zuplo/cli": "7.4.3",
+    "@zuplo/core": "7.4.3",
+    "@zuplo/runtime": "7.4.3",
+    "@zuplo/test": "7.4.3"
   }
 }