@zuplo/cli 7.2.0 → 7.2.1

package/node_modules/@zuplo/runtime/out/types/index.d.ts

@@ -333,8 +333,8 @@ export declare interface AIGatewayConfigurationLoaderV2InboundPolicyOptions {
 }
 
 /**
- * AI Gateway DLP Inbound Policy
- * @title AI Gateway DLP
+ * Data Loss Prevention (DLP) Inbound Policy for the AI Gateway
+ * @title Data Loss Prevention (DLP)
  * @product ai-gateway
  * @hidden
  * @requiresAI
@@ -366,7 +366,7 @@ export declare function AIGatewayDlpInboundPolicy(
 ): Promise<ZuploRequest | Response>;
 
 /**
- * The options for the AI Gateway 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 and streaming responses are scanned as they stream.
+ * 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 and streaming responses are scanned as they stream.
  * @public
  */
 export declare interface AIGatewayDlpInboundPolicyOptions {
@@ -379,10 +379,6 @@ export declare interface AIGatewayDlpInboundPolicyOptions {
    * Exact strings that are never flagged by any rule — documentation samples like Stripe's public test card `4242 4242 4242 4242`, or your own support email address. Matching is case-sensitive against the exact detected text, including when a value arrives split across streaming chunks.
    */
   allowValues?: string[];
-  /**
-   * The replacement text for masked matches. The `{type}` token inserts the detected type id in UPPER_SNAKE form (for example `[CONTACT_EMAIL]`), which keeps masked conversations legible to the model. Individual rules can override this.
-   */
-  mask?: string;
   /**
    * Default evidence level for rules that do not set their own. See the per-rule `detection` description for the level semantics. There are no numeric confidence thresholds to tune — levels are the whole dial.
    */
@@ -4871,19 +4867,23 @@ declare interface DlpCustomRule {
    */
   context?: string[];
   /**
-   * What happens when this type is found. `mask` replaces the matched text with a placeholder and the conversation continues; `block` rejects the request or terminates the response with an error naming only the detected types (never the values); `log` records a finding and lets the traffic pass unchanged — use it to trial a rule before enforcing it; `off` excludes this type from a group enabled by a broader key.
+   * What happens when this rule matches, in BOTH directions. `mask` replaces the matched text with a placeholder and the conversation continues; `block` rejects the request or terminates the response with an error naming only the rule's name (never the values); `log` records a finding and lets the traffic pass unchanged; `off` disables the rule. A rule states either `action` or the directional pair (`inboundAction`/`outboundAction`), never both.
    */
-  action: "mask" | "block" | "log" | "off";
+  action?: "mask" | "block" | "log" | "off";
   /**
-   * Where the rule applies. `inbound` scans what callers send the model (system prompt, message text, and tool-call arguments); `outbound` scans what the model sends back (buffered responses whole, streaming responses chunk by chunk). Defaults to `both`.
+   * What happens when this rule matches in what callers send the model. Use with `outboundAction` to give the rule different behavior per direction. Omitting it (or `off`) leaves the inbound direction unscanned for this rule. Cannot be combined with `action`.
    */
-  direction?: "both" | "inbound" | "outbound";
+  inboundAction?: "mask" | "block" | "log" | "off";
+  /**
+   * What happens when this rule matches in what the model sends back. Omitting it (or `off`) leaves the outbound direction unscanned for this rule. Cannot be combined with `action`.
+   */
+  outboundAction?: "mask" | "block" | "log" | "off";
   /**
    * How much evidence a match needs before this rule acts. `corroborated` additionally requires one of the type's context words near the match (types that define no context words behave as `standard`); `standard` uses the catalog as tuned — distinctive shapes act on their own while ambiguous shapes need nearby context; `aggressive` counts every pattern match and is false-positive-prone — pair it with the `log` action for audits. Overrides the policy-level `detection` for this rule.
    */
   detection?: "corroborated" | "standard" | "aggressive";
   /**
-   * Replacement text for this rule when `action` is `mask`, overriding the policy-level `mask`. The `{type}` token inserts the detected type id in UPPER_SNAKE form (for example `[CONTACT_EMAIL]`).
+   * Replacement text for this rule's masked matches. The `{type}` token inserts the detected type id in UPPER_SNAKE form, so the default turns a matched email into `[CONTACT_EMAIL]` — typed placeholders keep masked conversations legible to the model. Set a literal like `[REDACTED]` to hide the type.
    */
   mask?: string;
   partialMask?: DlpPartialMask;
@@ -4898,26 +4898,30 @@ declare interface DlpPartialMask {
 
 declare interface DlpRule {
   /**
-   * What happens when this type is found. `mask` replaces the matched text with a placeholder and the conversation continues; `block` rejects the request or terminates the response with an error naming only the detected types (never the values); `log` records a finding and lets the traffic pass unchanged — use it to trial a rule before enforcing it; `off` excludes this type from a group enabled by a broader key.
+   * What happens when this type is found, in BOTH directions. `mask` replaces the matched text with a placeholder and the conversation continues; `block` rejects the request or terminates the response with an error naming only the detected types (never the values); `log` records a finding and lets the traffic pass unchanged — use it to trial a rule before enforcing it; `off` excludes this type from a group enabled by a broader key. A rule states either `action` or the directional pair (`inboundAction`/`outboundAction`), never both.
+   */
+  action?: "mask" | "block" | "log" | "off";
+  /**
+   * What happens when this type is found in what callers send the model (system prompt, message text, and tool-call arguments). Use with `outboundAction` to give one type different behavior per direction — for example mask PII on the way in and block it on the way out. Omitting it (or `off`) leaves the inbound direction unscanned for this type. Cannot be combined with `action`.
    */
-  action: "mask" | "block" | "log" | "off";
+  inboundAction?: "mask" | "block" | "log" | "off";
   /**
-   * Where the rule applies. `inbound` scans what callers send the model (system prompt, message text, and tool-call arguments); `outbound` scans what the model sends back (buffered responses whole, streaming responses chunk by chunk). Defaults to `both`.
+   * What happens when this type is found in what the model sends back (buffered responses whole, streaming responses as they stream). Omitting it (or `off`) leaves the outbound direction unscanned for this type. Cannot be combined with `action`.
    */
-  direction?: "both" | "inbound" | "outbound";
+  outboundAction?: "mask" | "block" | "log" | "off";
   /**
    * How much evidence a match needs before this rule acts. `corroborated` additionally requires one of the type's context words near the match (types that define no context words behave as `standard`); `standard` uses the catalog as tuned — distinctive shapes act on their own while ambiguous shapes need nearby context; `aggressive` counts every pattern match and is false-positive-prone — pair it with the `log` action for audits. Overrides the policy-level `detection` for this rule.
    */
   detection?: "corroborated" | "standard" | "aggressive";
   /**
-   * Replacement text for this rule when `action` is `mask`, overriding the policy-level `mask`. The `{type}` token inserts the detected type id in UPPER_SNAKE form (for example `[CONTACT_EMAIL]`).
+   * Replacement text for this rule's masked matches. The `{type}` token inserts the detected type id in UPPER_SNAKE form, so the default turns a matched email into `[CONTACT_EMAIL]` — typed placeholders keep masked conversations legible to the model. Set a literal like `[REDACTED]` to hide the type.
    */
   mask?: string;
   partialMask?: DlpPartialMask;
 }
 
 /**
- * What to find and what to do about it. Each key is a built-in data type id (like `id-us-ssn`) or a group selector (like `pii` or `secret`, plus any dash-aligned id prefix such as `secret-aws`); each value is a rule object whose required `action` says what happens when that type is found. Types you do not mention are not scanned. The most specific key wins — an exact id beats a prefix beats a group — and the winning entry decides everything for its type, direction included. When one stretch of text matches multiple rules, the severest action wins (block > mask > log). At least one rule must scan something.
+ * What to find and what to do about it. Each key is a built-in data type id (like `id-us-ssn`) or a group selector (like `pii` or `secret`, plus any dash-aligned id prefix such as `secret-aws`); each value is a rule object stating either one `action` for both directions or a directional pair (`inboundAction`/`outboundAction`) — for example mask PII inbound and block it outbound. Types you do not mention are not scanned. The most specific key wins — an exact id beats a prefix beats a group — and the winning entry decides everything for its type. When one stretch of text matches multiple rules, the severest action wins (block > mask > log). At least one rule must scan something.
  * @public
  */
 declare interface DlpRules {

package/node_modules/@zuplo/runtime/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@zuplo/runtime",
   "type": "module",
-  "version": "7.2.0",
+  "version": "7.2.1",
   "repository": "https://github.com/zuplo/zuplo",
   "author": "Zuplo, Inc.",
   "exports": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zuplo/cli",
-  "version": "7.2.0",
+  "version": "7.2.1",
   "repository": "https://github.com/zuplo/zuplo",
   "author": "Zuplo, Inc.",
   "type": "module",
@@ -28,10 +28,10 @@
     "@opentelemetry/api": "1.9.0",
     "@opentelemetry/api-logs": "0.220.0",
     "@swc/core": "1.10.18",
-    "@zuplo/core": "7.2.0",
+    "@zuplo/core": "7.2.1",
     "@zuplo/editor": "1.0.31094607111",
-    "@zuplo/openapi-tools": "7.2.0",
-    "@zuplo/runtime": "7.2.0",
+    "@zuplo/openapi-tools": "7.2.1",
+    "@zuplo/runtime": "7.2.1",
     "chalk": "5.4.1",
     "chokidar": "3.5.3",
     "cookie": "1.0.2",
@@ -62,8 +62,8 @@
     "workerd": "1.20241230.0",
     "yargs": "17.7.2",
     "zod": "4.4.3",
-    "@zuplo/graphql": "7.2.0",
-    "@zuplo/otel": "7.2.0"
+    "@zuplo/graphql": "7.2.1",
+    "@zuplo/otel": "7.2.1"
   },
   "bundleDependencies": [
     "@inquirer/prompts",