@adcp/sdk 15.9.6 → 15.9.8

package/compliance/cache/{3.1.29 → 3.1.30}/universal/stale-response-advisory.yaml

@@ -30,7 +30,7 @@ narrative: |
 
   The stale-cache forcing phases require comply_test_controller with the
   force_upstream_unavailable scenario. Steps requiring the controller grade not_applicable for
-  agents that do not advertise it. The non-emission guard (Phase 3) runs for all agents.
+  agents that do not advertise it. The healthy non-emission guard runs before outage forcing.
 
 agent:
   interaction_model: media_buy_seller
@@ -45,8 +45,8 @@ caller:
 
 prerequisites:
   description: |
-    Phase 2 (stale-cache forcing) requires comply_test_controller with
-    force_upstream_unavailable support. Phase 3 (non-emission guard) runs for all agents.
+    The stale-cache forcing phase requires comply_test_controller with
+    force_upstream_unavailable support. The healthy non-emission guard runs before outage forcing.
   test_kit: "test-kits/acme-outdoor.yaml"
 
 phases:
@@ -87,7 +87,67 @@ phases:
             value: "stale_response_advisory--get_capabilities"
             description: "Context correlation_id returned unchanged"
 
+  - id: non_emission_guard
+    title: "No STALE_RESPONSE on healthy upstream response"
+    narrative: |
+      STALE_RESPONSE MUST NOT be emitted when the upstream is healthy. Per the normative
+      error-code description, sellers MUST NOT emit STALE_RESPONSE when the cache hit is
+      within freshness target or when no cached payload exists — the correct code for a
+      completely unavailable upstream with no cache is SERVICE_UNAVAILABLE.
+
+      Run this healthy request before forcing any outage. It also warms the cache for
+      the same brief and account used by the subsequent stale-cache probe.
+
+    steps:
+      - id: no_stale_on_healthy_upstream
+        title: "STALE_RESPONSE absent on healthy upstream response"
+        narrative: |
+          A normal get_products request against a healthy upstream MUST NOT emit
+          STALE_RESPONSE. Sellers that unconditionally emit STALE_RESPONSE on every
+          get_products response are non-conformant — the code is only valid when a
+          specific cache-fallback condition is active.
+
+          NOTE: No machine-enforced absence check for STALE_RESPONSE exists today — the
+          `field_absent` primitive rejects errors[] entirely, but other error codes are
+          valid. The schema and correlation_id checks below prove conformance for
+          non-STALE_RESPONSE flows; a dedicated `error_code_absent` check kind would
+          close this gap. TODO: add check primitive when runner contract supports it.
+        task: get_products
+        schema_ref: "media-buy/get-products-request.json"
+        response_schema_ref: "media-buy/get-products-response.json"
+        doc_ref: "/media-buy/task-reference/get_products"
+        comply_scenario: stale_response_non_emission
+        stateful: false
+        expected: |
+          Return products normally. errors[] may be absent or present with codes other
+          than STALE_RESPONSE. STALE_RESPONSE MUST NOT appear unless the seller is
+          actively serving from a stale cache entry past its freshness target.
+
+        sample_request:
+          buying_mode: "brief"
+          brief: "Display advertising"
+          account:
+            brand:
+              domain: "acmeoutdoor.example"
+            operator: "pinnacle-agency.example"
+            sandbox: true
+          context:
+            correlation_id: "stale_response_advisory--no_stale_on_healthy"
+        validations:
+          - check: response_schema
+            description: "Response matches get-products-response.json schema on healthy upstream"
+          - check: field_present
+            path: "context"
+            description: "Response echoes back the context object"
+          - check: field_value
+            path: "context.correlation_id"
+            value: "stale_response_advisory--no_stale_on_healthy"
+            description: "Context correlation_id returned unchanged"
+
   - id: stale_response_forcing
+    requires_capability:
+      path: compliance_testing.scenarios
+      contains: force_upstream_unavailable
     title: "Force stale-cache condition and verify advisory-success wire placement"
     narrative: |
       The test controller forces an upstream dependency unavailable while a stale cache entry
@@ -127,6 +187,9 @@ phases:
             tool: "get_products"
             upstream_name: "inventory-service"
           account:
+            brand:
+              domain: "acmeoutdoor.example"
+            operator: "pinnacle-agency.example"
             sandbox: true
           context:
             correlation_id: "stale_response_advisory--force_upstream_unavailable"
@@ -184,6 +247,7 @@ phases:
             brand:
               domain: "acmeoutdoor.example"
             operator: "pinnacle-agency.example"
+            sandbox: true
           context:
             correlation_id: "stale_response_advisory--stale_response_wire_placement"
         validations:
@@ -191,105 +255,49 @@ phases:
             description: "Response matches get-products-response.json schema even under stale cache"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted — remove permanent_advisory and severity fields. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted — remove permanent_advisory and severity fields. See issue #4934."
           - check: field_present
             path: "errors"
             description: "errors[] is present on a stale-cache response"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."
           - check: field_value
             path: "errors[0].code"
             value: "STALE_RESPONSE"
             description: "First errors[] entry carries STALE_RESPONSE code"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."
           - check: field_value
             path: "errors[0].details.served_from_cache"
             value: true
             description: "details.served_from_cache is true per error-details/stale-response.json"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."
           - check: field_present
             path: "errors[0].details.cache_age_seconds"
             description: "details.cache_age_seconds is present (required details field)"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."
           - check: field_present
             path: "context"
             description: "Response echoes back the context object on stale-cache advisory"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."
           - check: field_value
             path: "context.correlation_id"
             value: "stale_response_advisory--stale_response_wire_placement"
             description: "Context correlation_id returned unchanged"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."
           - check: field_present
             path: "products[0]"
             description: "Response payload is non-empty (products[] has at least one entry from stale cache)"
             severity: advisory
             permanent_advisory:
-              reason: "Gated on force_upstream_unavailable runner support. Promote to required when widely adopted. See issue #4934."
-
-  - id: non_emission_guard
-    title: "No STALE_RESPONSE on healthy upstream response"
-    narrative: |
-      STALE_RESPONSE MUST NOT be emitted when the upstream is healthy. Per the normative
-      error-code description, sellers MUST NOT emit STALE_RESPONSE when the cache hit is
-      within freshness target or when no cached payload exists — the correct code for a
-      completely unavailable upstream with no cache is SERVICE_UNAVAILABLE.
-
-      This phase sends a normal get_products request and verifies no STALE_RESPONSE appears.
-      Runs for all agents — no controller required.
-
-    steps:
-      - id: no_stale_on_healthy_upstream
-        title: "STALE_RESPONSE absent on healthy upstream response"
-        narrative: |
-          A normal get_products request against a healthy upstream MUST NOT emit
-          STALE_RESPONSE. Sellers that unconditionally emit STALE_RESPONSE on every
-          get_products response are non-conformant — the code is only valid when a
-          specific cache-fallback condition is active.
-
-          NOTE: No machine-enforced absence check for STALE_RESPONSE exists today — the
-          `field_absent` primitive rejects errors[] entirely, but other error codes are
-          valid. The schema and correlation_id checks below prove conformance for
-          non-STALE_RESPONSE flows; a dedicated `error_code_absent` check kind would
-          close this gap. TODO: add check primitive when runner contract supports it.
-        task: get_products
-        schema_ref: "media-buy/get-products-request.json"
-        response_schema_ref: "media-buy/get-products-response.json"
-        doc_ref: "/media-buy/task-reference/get_products"
-        comply_scenario: stale_response_non_emission
-        stateful: false
-        expected: |
-          Return products normally. errors[] may be absent or present with codes other
-          than STALE_RESPONSE. STALE_RESPONSE MUST NOT appear unless the seller is
-          actively serving from a stale cache entry past its freshness target.
-
-        sample_request:
-          buying_mode: "brief"
-          brief: "Display advertising for outdoor lifestyle campaign"
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-          context:
-            correlation_id: "stale_response_advisory--no_stale_on_healthy"
-        validations:
-          - check: response_schema
-            description: "Response matches get-products-response.json schema on healthy upstream"
-          - check: field_present
-            path: "context"
-            description: "Response echoes back the context object"
-          - check: field_value
-            path: "context.correlation_id"
-            value: "stale_response_advisory--no_stale_on_healthy"
-            description: "Context correlation_id returned unchanged"
+              reason: "Gated on force_upstream_unavailable being advertised in the seller's comply_test_controller scenarios. Promote to required when widely adopted. See issue #4934."

package/compliance/cache/{3.1.29 → 3.1.30}/universal/storyboard-schema.yaml

@@ -922,6 +922,13 @@
 #   Omitting `negative_path` when `expect_error: true` behaves as `schema_invalid`
 #   (backwards-compatible default).
 #
+# enrich_request: true (optional — only with expect_error: true and
+#   negative_path: payload_well_formed). Opt this semantic rejection probe into
+#   the normal per-task request enricher, including discovered auction bids.
+#   The default for negative probes preserves the authored request exactly;
+#   intentionally malformed requests MUST NOT set this flag. Explicit fixture
+#   values still win, and governance-authorized payloads remain unmodified.
+#
 # sample_request_skip_schema: boolean (optional — explicit opt-out of schema
 #   validation for a step regardless of `expect_error` / `negative_path`. Use
 #   sparingly; prefer `negative_path: schema_invalid` for intentionally malformed

package/compliance/cache/{3.2.5/protocols → 3.2.8/domains}/creative/scenarios/billing_out_of_band.yaml

@@ -143,6 +143,7 @@ phases:
             operator: "pinnacle-agency.example"
             operator_unit:
               id: "compliance-creative_billing_out_of_band-07c4ce40"
+            sandbox: true
           idempotency_key: "$generate:uuid_v4#creative_billing_out_of_band_report_usage"
           reporting_period:
             start: "2099-07-01T00:00:00Z"

package/compliance/cache/{3.2.5/protocols → 3.2.8/domains}/creative/scenarios/canonical_supported_formats.yaml

@@ -151,6 +151,7 @@ phases:
             operator: "pinnacle-agency.example"
             operator_unit:
               id: "compliance-creative_canonical_supported_formats-5b23e65e"
+            sandbox: true
           brand:
             domain: "acmeoutdoor.example"
           quality: "draft"
@@ -209,6 +210,7 @@ phases:
             operator: "pinnacle-agency.example"
             operator_unit:
               id: "compliance-creative_canonical_supported_formats-5b23e65e"
+            sandbox: true
           brand:
             domain: "acmeoutdoor.example"
           quality: "draft"

package/compliance/cache/{3.2.5 → 3.2.8}/domains/creative/scenarios/creative_lifecycle_webhooks.yaml

@@ -409,11 +409,13 @@ phases:
       - id: expect_status_changed_webhook
         title: "Assert suspended → rejected webhook payload"
         task: expect_webhook
+        triggered_by: force_creative_rejected
         filter:
           body:
             notification_type: "creative.status_changed"
             creative_id: "acme_lifecycle_banner_001"
             subscriber_id: "buyer-primary"
+            transition.to: "rejected"
         timeout_seconds: 30
         expect_idempotency_key: true
         webhook_payload_schema_ref: "creative/creative-status-changed-webhook.json"