@adcp/sdk 7.11.0 → 7.11.2

package/ADCP_VERSION

@@ -1 +1 @@
-3.0.12
+3.0.18

package/compliance/cache/{3.0.12 → 3.0.18}/domains/creative/index.yaml

@@ -328,7 +328,8 @@ phases:
         response_schema_ref: "creative/preview-creative-response.json"
         doc_ref: "/creative/task-reference/preview_creative"
         comply_scenario: creative_flow
-        stateful: true
+        requires_tool: preview_creative
+        stateful: false
         expected: |
           Return a preview of the display creative:
           - preview_url: rendered preview the buyer can inspect

package/compliance/cache/{3.0.12/protocols → 3.0.18/domains}/media-buy/creative-reception.yaml

@@ -194,6 +194,7 @@ phases:
         response_schema_ref: "creative/preview-creative-response.json"
         doc_ref: "/creative/task-reference/preview_creative"
         comply_scenario: creative_flow
+        requires_tool: preview_creative
         stateful: true
         expected: |
           Return a preview showing the creative in your platform's environment.

package/compliance/cache/{3.0.12/protocols → 3.0.18/domains}/media-buy/scenarios/measurement_terms_rejected.yaml

@@ -12,9 +12,10 @@ narrative: |
   measurement_terms negotiation is a round-trip. The buyer proposes a measurement vendor,
   window, and variance tolerance on each package; the seller either accepts (returning
   measurement_terms echoed in the response) or rejects with TERMS_REJECTED and a message
-  explaining what is unacceptable. The buyer mints a fresh idempotency_key and retries
-  create_media_buy with the adjusted payload — reusing the prior key against a different
-  body MUST be rejected with IDEMPOTENCY_CONFLICT per spec.
+  explaining what is unacceptable. Because only successful responses are cached,
+  the buyer may retry the corrected payload with the same idempotency_key after a
+  TERMS_REJECTED response; if the first request had succeeded, reusing that key
+  against a different body would be rejected with IDEMPOTENCY_CONFLICT.
 
   This scenario sends an intentionally aggressive first proposal (max_variance_percent: 0
   with a window the seller does not guarantee), verifies the seller rejects with
@@ -58,7 +59,9 @@ phases:
           measurement support in the response.
         sample_request:
           buying_mode: "brief"
-          brief: "Premium video inventory with measurement guarantees. Q2 flight, $50K."
+          brief: "Premium video inventory with measurement guarantees. Q3 flight, $50K."
+          filters:
+            is_fixed_price: true
           account:
             brand:
               domain: "acmeoutdoor.example"
@@ -74,6 +77,9 @@ phases:
           - check: field_present
             path: "products[0].product_id"
             description: "At least one product returned"
+          - check: field_present
+            path: "products[0].pricing_options[0].fixed_price"
+            description: "The captured pricing option is fixed-price; fixed-price storyboards do not send bid_price"
 
   - id: reject_terms
     title: "Seller rejects unworkable terms"
@@ -106,9 +112,9 @@ phases:
             brand:
               domain: "acmeoutdoor.example"
             operator: "pinnacle-agency.example"
-          idempotency_key: "$generate:uuid_v4#measurement_terms_rejected_aggressive_terms"
-          start_time: "2026-05-01T00:00:00Z"
-          end_time: "2026-05-31T23:59:59Z"
+          idempotency_key: "$generate:uuid_v4#media_buy_seller_measurement_terms_rejected_reject_terms_create_media_buy_aggressive_terms"
+          start_time: "2026-07-01T00:00:00Z"
+          end_time: "2026-09-30T23:59:59Z"
           packages:
             - product_id: "$context.product_id"
               budget: 25000
@@ -117,7 +123,7 @@ phases:
                 billing_measurement:
                   vendor:
                     domain: "videoamp.example"
-                  measurement_window: "c30"
+                  measurement_window: "c28"
                   max_variance_percent: 0
                 makegood_policy:
                   available_remedies: ["credit"]
@@ -163,9 +169,9 @@ phases:
             brand:
               domain: "acmeoutdoor.example"
             operator: "pinnacle-agency.example"
-          idempotency_key: "$generate:uuid_v4#measurement_terms_rejected_relaxed_terms"
-          start_time: "2026-05-01T00:00:00Z"
-          end_time: "2026-05-31T23:59:59Z"
+          idempotency_key: "$generate:uuid_v4#media_buy_seller_measurement_terms_rejected_accept_terms_create_media_buy_relaxed_terms"
+          start_time: "2026-07-01T00:00:00Z"
+          end_time: "2026-09-30T23:59:59Z"
           packages:
             - product_id: "$context.product_id"
               budget: 25000
@@ -194,3 +200,5 @@ phases:
             path: "context.correlation_id"
             value: "measurement_terms_rejected--relaxed"
             description: "Context correlation_id returned unchanged"
+        reviewer_checks:
+          - "Reviewer MUST confirm the seller releases the idempotency claim after a TERMS_REJECTED response. Probe: send the aggressive-terms request (same key, step 1), then retry with the same key and corrected terms (this step) — the seller MUST return a fresh media_buy_id, not IDEMPOTENCY_CONFLICT. A seller that caches rejected requests would make this two-step retry pattern impossible. See security.mdx#idempotency rule 3 ('Only successful responses are cached')."

package/compliance/cache/{3.0.12.previous → 3.0.18}/domains/media-buy/scenarios/proposal_finalize.yaml

@@ -8,6 +8,12 @@ required_tools:
   - get_products
   - create_media_buy
 
+# `media_buy.supports_proposals` is defined in the 3.1 schema. On 3.0.x,
+# absence is treated as false so non-proposal sellers skip this scenario.
+requires_capability:
+  path: media_buy.supports_proposals
+  equals: true
+
 narrative: |
   Proposals are curated media plans that the seller generates alongside products. The buyer
   reviews proposals, refines them (adjust budget splits, swap products, add constraints),

package/compliance/cache/{3.0.12.previous/protocols → 3.0.18/domains}/media-buy/state-machine.yaml

@@ -4,8 +4,18 @@ title: "Media buy state machine lifecycle"
 category: media_buy_state_machine
 summary: "Validates media buy state transitions: create, pause, resume, cancel, and terminal state enforcement."
 track: media_buy
+
+# This storyboard drives pause/resume immediately after create_media_buy. That
+# only works for sellers that explicitly declare auto-approval; manual-review
+# sellers may legitimately remain pending until approval and should not fail
+# an active-state transition test they cannot reach through the buyer surface.
+requires_capability:
+  path: media_buy.creative_approval_mode
+  equals: auto_approve
+
 required_tools:
   - create_media_buy
+  - sync_creatives
   - update_media_buy
 
 narrative: |
@@ -13,9 +23,10 @@ narrative: |
   paused, completed, rejected, canceled. Transitions between states must follow the spec — you cannot
   resume a canceled buy or pause a completed one.
 
-  This storyboard creates a media buy, walks it through pause/resume/cancel transitions, then
-  verifies that the agent rejects updates to a buy in a terminal state (canceled or completed).
-  It also tests package-level pause/resume independent of the media buy status.
+  This storyboard applies to sellers that declare media_buy.creative_approval_mode:
+  auto_approve. It creates a media buy, walks it through pause/resume/cancel transitions,
+  then verifies that the agent rejects updates to a buy in a terminal state (canceled or
+  completed). It also tests package-level pause/resume independent of the media buy status.
 
   The state machine is the backbone of media buy reliability. If an agent allows invalid
   transitions, buyers cannot trust the status field and automation breaks down.
@@ -25,6 +36,7 @@ agent:
   capabilities:
     - sells_media
     - accepts_briefs
+    - accepts_creatives
   examples:
     - "Any AdCP seller with media buy support"
 
@@ -108,9 +120,11 @@ phases:
             correlation_id: "media_buy_state_machine--discover_products"
         context_outputs:
           - name: product_id
-            path: 'products[0].product_id'
+            path: "products[0].product_id"
           - name: pricing_option_id
-            path: 'products[0].pricing_options[0].pricing_option_id'
+            path: "products[0].pricing_options[0].pricing_option_id"
+          - name: product_format_id
+            path: "products[0].format_ids[0]"
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
@@ -134,11 +148,60 @@ phases:
           - check: field_present
             path: "products[0].format_ids[0].id"
             description: "Format IDs include id — must be accepted back in sync_creatives"
+
+      - id: sync_creative
+        title: "Sync a creative for the test buy"
+        narrative: |
+          Upload a creative using the exact format_id returned by get_products. The
+          subsequent create_media_buy request assigns this creative to the package so
+          the created buy is pausable instead of legitimately remaining in
+          pending_creatives.
+        task: sync_creatives
+        schema_ref: "creative/sync-creatives-request.json"
+        response_schema_ref: "creative/sync-creatives-response.json"
+        doc_ref: "/creative/task-reference/sync_creatives"
+        comply_scenario: creative_sync
+        stateful: true
+        expected: |
+          Accept the creative into the account library so it can be assigned on
+          create_media_buy.
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.example"
+            operator: "pinnacle-agency.example"
+          creatives:
+            - creative_id: "state_machine_display_creative"
+              name: "Acme Outdoor State Machine Creative"
+              format_id: "$context.product_format_id"
+              assets:
+                image:
+                  asset_type: "image"
+                  url: "https://cdn.pinnacle-agency.example/state-machine-display.png"
+                  width: 300
+                  height: 250
+                  mime_type: "image/png"
+
+          idempotency_key: "$generate:uuid_v4#media_buy_state_machine_setup_sync_creative"
+          context:
+            correlation_id: "media_buy_state_machine--sync_creative"
+        validations:
+          - check: response_schema
+            description: "Response matches sync-creatives-response.json schema"
+          - check: field_present
+            path: "context"
+            description: "Response echoes back the context object"
+          - check: field_value
+            path: "context.correlation_id"
+            value: "media_buy_state_machine--sync_creative"
+            description: "Context correlation_id returned unchanged"
+
       - id: create_buy
         title: "Create the test media buy"
         narrative: |
-          Create a media buy using the discovered product. This buy will be used for
-          all subsequent state transition tests.
+          Create a media buy using the discovered product and synced creative. This
+          buy will be used for all subsequent state transition tests.
         task: create_media_buy
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
@@ -157,27 +220,33 @@ phases:
             operator: "pinnacle-agency.example"
           brand:
             domain: "acmeoutdoor.example"
-          start_time: "2026-05-01T00:00:00Z"
-          end_time: "2026-05-31T23:59:59Z"
+          start_time: "asap"
+          end_time: "2099-09-30T23:59:59Z"
           packages:
-            - product_id: "test-product"
+            - product_id: "$context.product_id"
               budget: 10000
-              pricing_option_id: "test-pricing"
+              pricing_option_id: "$context.pricing_option_id"
+              creative_assignments:
+                - creative_id: "state_machine_display_creative"
 
           idempotency_key: "$generate:uuid_v4#media_buy_state_machine_setup_create_buy"
           context:
             correlation_id: "media_buy_state_machine--create_buy"
         context_outputs:
           - name: media_buy_id
-            path: 'media_buy_id'
+            path: "media_buy_id"
           - name: package_id
-            path: 'packages[0].package_id'
+            path: "packages[0].package_id"
         validations:
           - check: response_schema
             description: "Response matches create-media-buy-response.json schema"
           - check: field_present
             path: "media_buy_id"
             description: "Response includes a media_buy_id"
+          - check: field_value
+            path: "status"
+            allowed_values: ["active"]
+            description: "Auto-approval state-machine test starts from an active media buy"
 
           - check: field_present
             path: "context"

package/compliance/cache/{3.0.12 → 3.0.18}/index.json

@@ -1,6 +1,7 @@
 {
-  "adcp_version": "3.0.12",
-  "generated_at": "2026-05-13T10:39:52.556Z",
+  "published_version": "3.0.18",
+  "adcp_version": "3.0.18",
+  "generated_at": "2026-06-16T06:36:57.102Z",
   "universal": [
     "capability-discovery",
     "collection-lists-pagination-integrity",

package/compliance/cache/{3.0.12 → 3.0.18}/protocols/creative/index.yaml

@@ -328,7 +328,8 @@ phases:
         response_schema_ref: "creative/preview-creative-response.json"
         doc_ref: "/creative/task-reference/preview_creative"
         comply_scenario: creative_flow
-        stateful: true
+        requires_tool: preview_creative
+        stateful: false
         expected: |
           Return a preview of the display creative:
           - preview_url: rendered preview the buyer can inspect

package/compliance/cache/{3.0.12.previous/domains → 3.0.18/protocols}/media-buy/creative-reception.yaml

@@ -194,6 +194,7 @@ phases:
         response_schema_ref: "creative/preview-creative-response.json"
         doc_ref: "/creative/task-reference/preview_creative"
         comply_scenario: creative_flow
+        requires_tool: preview_creative
         stateful: true
         expected: |
           Return a preview showing the creative in your platform's environment.

package/compliance/cache/{3.0.12.previous → 3.0.18}/protocols/media-buy/scenarios/measurement_terms_rejected.yaml

@@ -12,9 +12,10 @@ narrative: |
   measurement_terms negotiation is a round-trip. The buyer proposes a measurement vendor,
   window, and variance tolerance on each package; the seller either accepts (returning
   measurement_terms echoed in the response) or rejects with TERMS_REJECTED and a message
-  explaining what is unacceptable. The buyer mints a fresh idempotency_key and retries
-  create_media_buy with the adjusted payload — reusing the prior key against a different
-  body MUST be rejected with IDEMPOTENCY_CONFLICT per spec.
+  explaining what is unacceptable. Because only successful responses are cached,
+  the buyer may retry the corrected payload with the same idempotency_key after a
+  TERMS_REJECTED response; if the first request had succeeded, reusing that key
+  against a different body would be rejected with IDEMPOTENCY_CONFLICT.
 
   This scenario sends an intentionally aggressive first proposal (max_variance_percent: 0
   with a window the seller does not guarantee), verifies the seller rejects with
@@ -58,7 +59,9 @@ phases:
           measurement support in the response.
         sample_request:
           buying_mode: "brief"
-          brief: "Premium video inventory with measurement guarantees. Q2 flight, $50K."
+          brief: "Premium video inventory with measurement guarantees. Q3 flight, $50K."
+          filters:
+            is_fixed_price: true
           account:
             brand:
               domain: "acmeoutdoor.example"
@@ -74,6 +77,9 @@ phases:
           - check: field_present
             path: "products[0].product_id"
             description: "At least one product returned"
+          - check: field_present
+            path: "products[0].pricing_options[0].fixed_price"
+            description: "The captured pricing option is fixed-price; fixed-price storyboards do not send bid_price"
 
   - id: reject_terms
     title: "Seller rejects unworkable terms"
@@ -106,9 +112,9 @@ phases:
             brand:
               domain: "acmeoutdoor.example"
             operator: "pinnacle-agency.example"
-          idempotency_key: "$generate:uuid_v4#measurement_terms_rejected_aggressive_terms"
-          start_time: "2026-05-01T00:00:00Z"
-          end_time: "2026-05-31T23:59:59Z"
+          idempotency_key: "$generate:uuid_v4#media_buy_seller_measurement_terms_rejected_reject_terms_create_media_buy_aggressive_terms"
+          start_time: "2026-07-01T00:00:00Z"
+          end_time: "2026-09-30T23:59:59Z"
           packages:
             - product_id: "$context.product_id"
               budget: 25000
@@ -117,7 +123,7 @@ phases:
                 billing_measurement:
                   vendor:
                     domain: "videoamp.example"
-                  measurement_window: "c30"
+                  measurement_window: "c28"
                   max_variance_percent: 0
                 makegood_policy:
                   available_remedies: ["credit"]
@@ -163,9 +169,9 @@ phases:
             brand:
               domain: "acmeoutdoor.example"
             operator: "pinnacle-agency.example"
-          idempotency_key: "$generate:uuid_v4#measurement_terms_rejected_relaxed_terms"
-          start_time: "2026-05-01T00:00:00Z"
-          end_time: "2026-05-31T23:59:59Z"
+          idempotency_key: "$generate:uuid_v4#media_buy_seller_measurement_terms_rejected_accept_terms_create_media_buy_relaxed_terms"
+          start_time: "2026-07-01T00:00:00Z"
+          end_time: "2026-09-30T23:59:59Z"
           packages:
             - product_id: "$context.product_id"
               budget: 25000
@@ -194,3 +200,5 @@ phases:
             path: "context.correlation_id"
             value: "measurement_terms_rejected--relaxed"
             description: "Context correlation_id returned unchanged"
+        reviewer_checks:
+          - "Reviewer MUST confirm the seller releases the idempotency claim after a TERMS_REJECTED response. Probe: send the aggressive-terms request (same key, step 1), then retry with the same key and corrected terms (this step) — the seller MUST return a fresh media_buy_id, not IDEMPOTENCY_CONFLICT. A seller that caches rejected requests would make this two-step retry pattern impossible. See security.mdx#idempotency rule 3 ('Only successful responses are cached')."

package/compliance/cache/{3.0.12 → 3.0.18}/protocols/media-buy/scenarios/proposal_finalize.yaml

@@ -8,6 +8,12 @@ required_tools:
   - get_products
   - create_media_buy
 
+# `media_buy.supports_proposals` is defined in the 3.1 schema. On 3.0.x,
+# absence is treated as false so non-proposal sellers skip this scenario.
+requires_capability:
+  path: media_buy.supports_proposals
+  equals: true
+
 narrative: |
   Proposals are curated media plans that the seller generates alongside products. The buyer
   reviews proposals, refines them (adjust budget splits, swap products, add constraints),

package/compliance/cache/{3.0.12 → 3.0.18}/protocols/media-buy/state-machine.yaml

@@ -4,8 +4,18 @@ title: "Media buy state machine lifecycle"
 category: media_buy_state_machine
 summary: "Validates media buy state transitions: create, pause, resume, cancel, and terminal state enforcement."
 track: media_buy
+
+# This storyboard drives pause/resume immediately after create_media_buy. That
+# only works for sellers that explicitly declare auto-approval; manual-review
+# sellers may legitimately remain pending until approval and should not fail
+# an active-state transition test they cannot reach through the buyer surface.
+requires_capability:
+  path: media_buy.creative_approval_mode
+  equals: auto_approve
+
 required_tools:
   - create_media_buy
+  - sync_creatives
   - update_media_buy
 
 narrative: |
@@ -13,9 +23,10 @@ narrative: |
   paused, completed, rejected, canceled. Transitions between states must follow the spec — you cannot
   resume a canceled buy or pause a completed one.
 
-  This storyboard creates a media buy, walks it through pause/resume/cancel transitions, then
-  verifies that the agent rejects updates to a buy in a terminal state (canceled or completed).
-  It also tests package-level pause/resume independent of the media buy status.
+  This storyboard applies to sellers that declare media_buy.creative_approval_mode:
+  auto_approve. It creates a media buy, walks it through pause/resume/cancel transitions,
+  then verifies that the agent rejects updates to a buy in a terminal state (canceled or
+  completed). It also tests package-level pause/resume independent of the media buy status.
 
   The state machine is the backbone of media buy reliability. If an agent allows invalid
   transitions, buyers cannot trust the status field and automation breaks down.
@@ -25,6 +36,7 @@ agent:
   capabilities:
     - sells_media
     - accepts_briefs
+    - accepts_creatives
   examples:
     - "Any AdCP seller with media buy support"
 
@@ -108,9 +120,11 @@ phases:
             correlation_id: "media_buy_state_machine--discover_products"
         context_outputs:
           - name: product_id
-            path: 'products[0].product_id'
+            path: "products[0].product_id"
           - name: pricing_option_id
-            path: 'products[0].pricing_options[0].pricing_option_id'
+            path: "products[0].pricing_options[0].pricing_option_id"
+          - name: product_format_id
+            path: "products[0].format_ids[0]"
         validations:
           - check: response_schema
             description: "Response matches get-products-response.json schema"
@@ -134,11 +148,60 @@ phases:
           - check: field_present
             path: "products[0].format_ids[0].id"
             description: "Format IDs include id — must be accepted back in sync_creatives"
+
+      - id: sync_creative
+        title: "Sync a creative for the test buy"
+        narrative: |
+          Upload a creative using the exact format_id returned by get_products. The
+          subsequent create_media_buy request assigns this creative to the package so
+          the created buy is pausable instead of legitimately remaining in
+          pending_creatives.
+        task: sync_creatives
+        schema_ref: "creative/sync-creatives-request.json"
+        response_schema_ref: "creative/sync-creatives-response.json"
+        doc_ref: "/creative/task-reference/sync_creatives"
+        comply_scenario: creative_sync
+        stateful: true
+        expected: |
+          Accept the creative into the account library so it can be assigned on
+          create_media_buy.
+
+        sample_request:
+          account:
+            brand:
+              domain: "acmeoutdoor.example"
+            operator: "pinnacle-agency.example"
+          creatives:
+            - creative_id: "state_machine_display_creative"
+              name: "Acme Outdoor State Machine Creative"
+              format_id: "$context.product_format_id"
+              assets:
+                image:
+                  asset_type: "image"
+                  url: "https://cdn.pinnacle-agency.example/state-machine-display.png"
+                  width: 300
+                  height: 250
+                  mime_type: "image/png"
+
+          idempotency_key: "$generate:uuid_v4#media_buy_state_machine_setup_sync_creative"
+          context:
+            correlation_id: "media_buy_state_machine--sync_creative"
+        validations:
+          - check: response_schema
+            description: "Response matches sync-creatives-response.json schema"
+          - check: field_present
+            path: "context"
+            description: "Response echoes back the context object"
+          - check: field_value
+            path: "context.correlation_id"
+            value: "media_buy_state_machine--sync_creative"
+            description: "Context correlation_id returned unchanged"
+
       - id: create_buy
         title: "Create the test media buy"
         narrative: |
-          Create a media buy using the discovered product. This buy will be used for
-          all subsequent state transition tests.
+          Create a media buy using the discovered product and synced creative. This
+          buy will be used for all subsequent state transition tests.
         task: create_media_buy
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
@@ -157,27 +220,33 @@ phases:
             operator: "pinnacle-agency.example"
           brand:
             domain: "acmeoutdoor.example"
-          start_time: "2026-05-01T00:00:00Z"
-          end_time: "2026-05-31T23:59:59Z"
+          start_time: "asap"
+          end_time: "2099-09-30T23:59:59Z"
           packages:
-            - product_id: "test-product"
+            - product_id: "$context.product_id"
               budget: 10000
-              pricing_option_id: "test-pricing"
+              pricing_option_id: "$context.pricing_option_id"
+              creative_assignments:
+                - creative_id: "state_machine_display_creative"
 
           idempotency_key: "$generate:uuid_v4#media_buy_state_machine_setup_create_buy"
           context:
             correlation_id: "media_buy_state_machine--create_buy"
         context_outputs:
           - name: media_buy_id
-            path: 'media_buy_id'
+            path: "media_buy_id"
           - name: package_id
-            path: 'packages[0].package_id'
+            path: "packages[0].package_id"
         validations:
           - check: response_schema
             description: "Response matches create-media-buy-response.json schema"
           - check: field_present
             path: "media_buy_id"
             description: "Response includes a media_buy_id"
+          - check: field_value
+            path: "status"
+            allowed_values: ["active"]
+            description: "Auto-approval state-machine test starts from an active media buy"
 
           - check: field_present
             path: "context"

package/compliance/cache/{3.0.12.previous → 3.0.18}/specialisms/creative-template/index.yaml

@@ -213,6 +213,7 @@ phases:
         response_schema_ref: "creative/preview-creative-response.json"
         doc_ref: "/creative/task-reference/preview_creative"
         comply_scenario: creative_flow
+        requires_tool: preview_creative
         stateful: false
         expected: |
           Return a preview render. The response should include:

package/compliance/cache/{3.0.12 → 3.0.18}/test-kits/webhook-receiver-runner.yaml

@@ -2,15 +2,15 @@
 #
 # Applies to:
 #   - universal/webhook-emission.yaml (primary consumer — grades outbound
-#     webhook conformance: idempotency_key presence, stability across retries,
-#     and RFC 9421 signature validity when 9421 is in effect)
-#   - universal/idempotency.yaml (replay-side-effect invariant — "no duplicate
-#     webhooks on replay" step is gated on this contract being in scope)
+#     webhook conformance: operation_id echo, idempotency_key presence,
+#     stability across retries, idempotency replay side effects, and RFC 9421
+#     signature validity when 9421 is in effect)
 #   - Any future storyboard that needs to observe outbound webhooks.
 #
 # The webhook-emission universal grades an agent's outbound-webhook
-# conformance: idempotency_key presence and stability across retries, and —
-# when the 9421 webhook profile is in effect — RFC 9421 signature validity per
+# conformance: operation_id echo, idempotency_key presence and stability
+# across retries, absence of duplicate webhooks on request replay, and — when
+# the 9421 webhook profile is in effect — RFC 9421 signature validity per
 # docs/building/implementation/security.mdx#webhook-callbacks.
 #
 # Storyboards are unidirectional by default (runner → agent). Verifying what
@@ -28,15 +28,15 @@ id: webhook_receiver_runner
 applies_to:
   universals:
     - webhook-emission
-    - idempotency
 
 description: |
   Coordination contract between a black-box runner hosting a webhook receiver
   and a webhook-emitting agent under test. The runner mints per-step HTTPS
   endpoints, injects them into push_notification_config.url on the steps that
   trigger webhooks, observes incoming deliveries via @adcp/client AsyncHandler
-  hooks, and asserts on idempotency_key presence, idempotency_key stability
-  across retries, and (when advertised) 9421 signature validity.
+  hooks, and asserts on operation_id echo, idempotency_key presence,
+  idempotency_key stability across retries, absence of duplicate webhooks on
+  request replay, and (when advertised) 9421 signature validity.
 
 endpoint_scope: sandbox
 # Storyboards that drive webhook emission typically call spend-committing