@adcp/sdk 14.0.0-rc.49 → 14.0.0-rc.50

package/compliance/cache/{3.1.18/domains → 3.1.24/protocols}/media-buy/scenarios/governance_conditions.yaml

@@ -4,11 +4,18 @@ title: "Seller attaches conditions when governance approves with conditions"
 category: media_buy_seller
 summary: "Verifies that the seller attaches governance conditions to the buy when governance approves with conditions."
 track: media_buy
+requires:
+  - multi_agent
+default_agent: sales
 required_tools:
   - sync_governance
   - get_products
   - create_media_buy
 
+requires_capability:
+  path: media_buy.governance_aware
+  equals: true
+
 narrative: |
   This is a multi-agent test. The test harness sets up a governance plan on a governance
   agent with custom policies that trigger conditions (e.g., "CTV buys require weekly
@@ -53,6 +60,7 @@ phases:
     steps:
       - id: sync_plans
         title: "Create conditional governance plan"
+        agent: governance
         task: sync_plans
         schema_ref: "governance/sync-plans-request.json"
         response_schema_ref: "governance/sync-plans-response.json"
@@ -82,6 +90,9 @@ phases:
                 - policy_id: "ugc_brand_safety"
                   enforcement: "must"
                   policy: "UGC placements require brand safety review before activation."
+        context_outputs:
+          - name: plan_id
+            path: "plans[0].plan_id"
         validations:
           - check: response_schema
             description: "Response matches sync-plans-response.json schema"
@@ -91,6 +102,7 @@ phases:
     steps:
       - id: sync_accounts
         title: "Establish account with seller"
+        agent: sales
         task: sync_accounts
         schema_ref: "account/sync-accounts-request.json"
         response_schema_ref: "account/sync-accounts-response.json"
@@ -115,6 +127,7 @@ phases:
 
       - id: sync_governance
         title: "Register governance agent with seller"
+        agent: sales
         task: sync_governance
         schema_ref: "account/sync-governance-request.json"
         response_schema_ref: "account/sync-governance-response.json"
@@ -143,6 +156,7 @@ phases:
     steps:
       - id: get_products_brief
         title: "Discover CTV products"
+        agent: sales
         task: get_products
         schema_ref: "media-buy/get-products-request.json"
         response_schema_ref: "media-buy/get-products-response.json"
@@ -172,6 +186,7 @@ phases:
 
       - id: create_media_buy_conditions
         title: "Create CTV buy (governance approves with conditions)"
+        agent: sales
         task: create_media_buy
         schema_ref: "media-buy/create-media-buy-request.json"
         response_schema_ref: "media-buy/create-media-buy-response.json"
@@ -192,6 +207,7 @@ phases:
               domain: "acmeoutdoor.example"
             operator: "pinnacle-agency.example"
             sandbox: true
+          plan_id: "$context.plan_id"
           start_time: "asap"
           end_time: "2099-06-30T23:59:59Z"
           packages:

package/compliance/cache/{3.1.18 → 3.1.24}/protocols/media-buy/scenarios/measurement_terms_rejected.yaml

@@ -1,25 +1,20 @@
 id: media_buy_seller/measurement_terms_rejected
-version: "1.0.0"
+version: "1.0.1"
 title: "Seller rejects unworkable measurement_terms"
 category: media_buy_seller
-summary: "Buyer proposes measurement_terms the seller will not accept; seller returns TERMS_REJECTED; buyer retries with seller-compatible terms."
+summary: "Buyer proposes unworkable measurement_terms and the seller returns TERMS_REJECTED."
 track: media_buy
 required_tools:
   - get_products
   - create_media_buy
 
 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.
+  The buyer proposes a measurement vendor, window, and variance tolerance on each
+  package. This universal scenario sends intentionally unworkable terms and verifies
+  that the seller rejects them with TERMS_REJECTED and an explanatory message.
 
-  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
-  TERMS_REJECTED, then retries with a relaxed proposal that falls inside the seller's
-  stated tolerance and expects a successful create_media_buy.
+  AdCP 3.1 has no capability bit for measurement-term acceptance, so the optional
+  relaxed-terms success arm is deliberately not graded on this maintenance line.
 
 agent:
   interaction_model: media_buy_seller
@@ -140,64 +135,3 @@ phases:
             path: "context.correlation_id"
             value: "measurement_terms_rejected--aggressive"
             description: "Context correlation_id returned unchanged"
-
-  - id: accept_terms
-    title: "Buyer retries with acceptable terms"
-    narrative: |
-      The buyer relaxes measurement_terms to match the seller's stated capability
-      (c7 window, 10% variance, makegood remedies) and retries. The seller accepts and
-      returns the confirmed terms echoed in the response.
-
-    steps:
-      - id: create_media_buy_relaxed_terms
-        title: "Propose seller-compatible measurement_terms"
-        task: create_media_buy
-        schema_ref: "media-buy/create-media-buy-request.json"
-        response_schema_ref: "media-buy/create-media-buy-response.json"
-        doc_ref: "/media-buy/task-reference/create_media_buy"
-        comply_scenario: create_media_buy
-        stateful: true
-        expected: |
-          The buy succeeds. The response echoes the accepted measurement_terms (possibly
-          normalized by the seller).
-
-        sample_request:
-          brand:
-            domain: "acmeoutdoor.example"
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-          idempotency_key: "$generate:uuid_v4#media_buy_seller_measurement_terms_rejected_accept_terms_create_media_buy_relaxed_terms"
-          start_time: "asap"
-          end_time: "2099-09-30T23:59:59Z"
-          packages:
-            - product_id: "$context.product_id"
-              budget: 25000
-              pricing_option_id: "$context.pricing_option_id"
-              measurement_terms:
-                billing_measurement:
-                  vendor:
-                    domain: "videoamp.example"
-                  measurement_window: "c7"
-                  max_variance_percent: 10
-                makegood_policy:
-                  available_remedies: ["additional_delivery", "credit"]
-
-          context:
-            correlation_id: "measurement_terms_rejected--relaxed"
-        validations:
-          - check: response_schema
-            description: "Response matches create-media-buy-response.json schema"
-          - check: field_present
-            path: "media_buy_id"
-            description: "Seller returns a media_buy_id after accepting terms"
-          - check: field_present
-            path: "context"
-            description: "Response echoes back the context object"
-          - check: field_value
-            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.1.18 → 3.1.24}/protocols/media-buy/scenarios/pending_creatives_to_start.yaml

@@ -1,17 +1,16 @@
 id: media_buy_seller/pending_creatives_to_start
-version: "1.0.0"
+version: "1.0.1"
 title: "Creative sync unblocks pending_creatives → pending_start"
 category: media_buy_seller
 summary: "Verifies that a media buy created without creatives sits in pending_creatives until sync_creatives completes, then transitions to pending_start."
 track: media_buy
 
-# This scenario requires an explicit auto-approval declaration. Sellers that
-# declare `require_human`, or omit the field because approval behavior is
-# legacy-unspecified, grade not_applicable rather than false-failing on a
-# manual-review workflow.
+# This scenario requires a creative library. The 3.1 runner supports one
+# storyboard-level capability predicate, so the auto-approval predicate is
+# repeated on each phase below to preserve both applicability conditions.
 requires_capability:
-  path: media_buy.creative_approval_mode
-  equals: auto_approve
+  path: creative.has_creative_library
+  equals: true
 
 required_tools:
   - get_products
@@ -52,6 +51,9 @@ prerequisites:
 
 phases:
   - id: setup
+    requires_capability: &auto_approval_gate
+      path: media_buy.creative_approval_mode
+      equals: auto_approve
     title: "Discover products and formats"
     steps:
       - id: get_products_brief
@@ -91,6 +93,7 @@ phases:
             description: "The captured pricing option is fixed-price; fixed-price storyboards do not send bid_price"
 
   - id: create_without_creatives
+    requires_capability: *auto_approval_gate
     title: "Create media buy without creative_assignments"
     narrative: |
       The buyer intentionally omits creative_assignments. The seller must accept the
@@ -168,6 +171,7 @@ phases:
             description: "Created package echoes package-level context for legacy package correlation"
 
   - id: supply_creatives
+    requires_capability: *auto_approval_gate
     title: "Supply creatives and assign to the package"
     narrative: |
       The buyer syncs a creative with the format the product requires, then updates the
@@ -260,6 +264,7 @@ phases:
             description: "Envelope task-status is completed on synchronous update success (protocol-envelope.json required: [status])"
 
   - id: verify_transition
+    requires_capability: *auto_approval_gate
     title: "Verify the status transition"
     narrative: |
       Independently of the update_media_buy response, call get_media_buys to confirm the

package/compliance/cache/{3.1.18 → 3.1.24}/protocols/media-buy/scenarios/provenance_audit_observation.yaml

@@ -126,6 +126,7 @@ phases:
       - id: sync_creatives_carveout_claim
         title: "Submit creative that carries an audit-worthy carve-out claim"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
@@ -257,6 +258,7 @@ phases:
       - id: query_directed_audit_observation
         title: "Assert directed carve-out audit observation"
         task: comply_test_controller
+        requires_tool: comply_test_controller
         schema_ref: "compliance/comply-test-controller-request.json"
         response_schema_ref: "compliance/comply-test-controller-response.json"
         doc_ref: "/building/implementation/comply-test-controller"
@@ -296,6 +298,7 @@ phases:
       - id: query_edited_audit_observation
         title: "Assert edited carve-out audit observation"
         task: comply_test_controller
+        requires_tool: comply_test_controller
         schema_ref: "compliance/comply-test-controller-request.json"
         response_schema_ref: "compliance/comply-test-controller-response.json"
         doc_ref: "/building/implementation/comply-test-controller"

package/compliance/cache/{3.1.18 → 3.1.24}/protocols/media-buy/scenarios/provenance_enforcement.yaml

@@ -152,6 +152,7 @@ phases:
       - id: sync_creatives_no_provenance
         title: "Submit creative with no provenance object"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
@@ -219,6 +220,7 @@ phases:
       - id: sync_creatives_no_digital_source_type
         title: "Submit creative with provenance but no digital_source_type"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
@@ -289,6 +291,7 @@ phases:
       - id: sync_creatives_off_list_verifier
         title: "Submit creative pointing at an off-list verifier"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
@@ -376,6 +379,7 @@ phases:
       - id: sync_creatives_missing_disclosure
         title: "Submit creative with provenance but no disclosure"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
@@ -447,6 +451,7 @@ phases:
       - id: sync_creatives_with_disclosure
         title: "Resubmit with disclosure metadata populated and an on-list verify_agent"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"

package/compliance/cache/{3.1.18 → 3.1.24}/protocols/media-buy/scenarios/provenance_truth_of_claim.yaml

@@ -145,6 +145,7 @@ phases:
       - id: sync_creatives_contradicted
         title: "Submit creative whose claim contradicts the verifier's verdict"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"
@@ -235,6 +236,7 @@ phases:
       - id: sync_creatives_consistent
         title: "Submit creative whose claim matches the verifier's verdict"
         task: sync_creatives
+        requires_tool: sync_creatives
         schema_ref: "creative/sync-creatives-request.json"
         response_schema_ref: "creative/sync-creatives-response.json"
         doc_ref: "/creative/task-reference/sync_creatives"

package/compliance/cache/{3.1.18 → 3.1.24}/protocols/media-buy/scenarios/refine_products.yaml

@@ -1,5 +1,5 @@
 id: media_buy_seller/refine_products
-version: "1.0.0"
+version: "1.0.1"
 title: "Seller handles product refinement"
 category: media_buy_seller
 summary: "Verifies that a media buy seller supports buying_mode: refine with product-level and request-level changes."
@@ -7,6 +7,10 @@ track: media_buy
 required_tools:
   - get_products
 
+requires_capability:
+  path: media_buy.buying_modes
+  contains: refine
+
 narrative: |
   After a buyer receives products from a brief, they refine the results without starting
   over. The buyer calls get_products with buying_mode: refine and a refine array describing

package/compliance/cache/{3.1.18 → 3.1.24}/specialisms/creative-generative/generative-seller.yaml

@@ -5,7 +5,6 @@ category: creative_generative
 summary: "Seller agent that generates creatives from briefs at buy time — no pre-built assets required."
 track: media_buy
 required_tools:
-  - sync_governance
   - get_products
   - create_media_buy
   - list_creative_formats
@@ -39,12 +38,9 @@ narrative: |
   programmatic inventory but can't accept a pre-built VAST tag or display banner is incoherent.
   The generative capability is additive to standard programmatic creative acceptance.
 
-  This storyboard focuses on the generative creative delta. The account setup includes
-  governance agent registration before the buy flow; proposal refinement works identically
-  to the base media_buy_seller storyboard.
-
-context:
-  governance_agent_url: "https://test-agent.adcontextprotocol.org"
+  This storyboard focuses on the generative creative delta. Governance-aware creation is
+  covered by the dedicated multi-agent scenario; proposal refinement works identically to
+  the base media_buy_seller storyboard.
 
 agent:
   interaction_model: media_buy_seller
@@ -165,7 +161,7 @@ phases:
           accounts:
             - brand:
                 domain: "acmeoutdoor.example"
-              operator: "pinnacle-agency.example"
+              operator: "generative-seller.pinnacle-agency.example"
               billing: "operator"
               payment_terms: "net_30"
 
@@ -189,50 +185,6 @@ phases:
             path: "context.correlation_id"
             value: "creative_generative--seller--sync_accounts"
             description: "Context correlation_id returned unchanged"
-      - id: sync_governance
-        title: "Register governance agent"
-        narrative: |
-          The buyer registers the configured governance agent on the account before
-          creating the media buy with generative creative support.
-        task: sync_governance
-        schema_ref: "account/sync-governance-request.json"
-        response_schema_ref: "account/sync-governance-response.json"
-        doc_ref: "/accounts/tasks/sync_governance"
-        stateful: true
-        expected: |
-          Acknowledge governance registration for the account:
-          - status: synced
-          - governance_agents[0].url echoes the configured governance agent
-
-        sample_request:
-          accounts:
-            - account:
-                brand:
-                  domain: "acmeoutdoor.example"
-                operator: "pinnacle-agency.example"
-              governance_agents:
-                - url: "$context.governance_agent_url"
-                  authentication:
-                    schemes: ["Bearer"]
-                    credentials: "gov-token-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
-
-          idempotency_key: "$generate:uuid_v4#creative_generative_seller_account_setup_sync_governance"
-          context:
-            correlation_id: "creative_generative--seller--sync_governance"
-        validations:
-          - check: response_schema
-            description: "Response matches sync-governance-response.json schema"
-          - check: field_value
-            path: "accounts[0].status"
-            value: "synced"
-            description: "Governance agent is registered on the account"
-          - check: field_present
-            path: "context"
-            description: "Response echoes back the context object"
-          - check: field_value
-            path: "context.correlation_id"
-            value: "creative_generative--seller--sync_governance"
-            description: "Context correlation_id returned unchanged"
   - id: format_discovery
     title: "Format discovery"
     narrative: |
@@ -342,7 +294,7 @@ phases:
           account:
             brand:
               domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
 
           context:
             correlation_id: "creative_generative--seller--get_products_brief"
@@ -414,7 +366,7 @@ phases:
           account:
             brand:
               domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
           start_time: "asap"
           end_time: "2099-06-30T23:59:59Z"
           packages:
@@ -494,7 +446,7 @@ phases:
           account:
             brand:
               domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
           creatives:
             - creative_id: "gen_display_summer_sale"
               name: "Summer Sale - Generated Display 300x250"
@@ -594,7 +546,7 @@ phases:
           account:
             brand:
               domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
           creatives:
             - creative_id: "static_display_300x250"
               name: "Trail Pro 3000 - Pre-built Display 300x250"
@@ -648,7 +600,7 @@ phases:
           account:
             brand:
               domain: "nonexistent-brand-xyz.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
           creatives:
             - creative_id: "gen_invalid_brand"
               name: "Invalid Brand Test"
@@ -719,7 +671,7 @@ phases:
           account:
             brand:
               domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
           creatives:
             - creative_id: "gen_display_summer_sale"
               name: "Summer Sale - Generated Display 300x250"
@@ -797,7 +749,7 @@ phases:
           account:
             brand:
               domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
+            operator: "generative-seller.pinnacle-agency.example"
           media_buy_ids:
             - "$context.media_buy_id"
           include_package_daily_breakdown: true

package/compliance/cache/{3.1.18 → 3.1.24}/specialisms/creative-generative/index.yaml

@@ -216,8 +216,8 @@ phases:
             path: "creative_manifest.assets"
             description: "Output manifest includes generated assets"
           - check: field_present
-            path: "creative_manifest.format_id"
-            description: "Output manifest includes format_id"
+            path: "creative_manifest.format_kind"
+            description: "Output manifest includes format_kind"
 
           - check: field_present
             path: "context"
@@ -438,8 +438,8 @@ phases:
             path: "creative_manifest.assets"
             description: "Production manifest includes assets"
           - check: field_present
-            path: "creative_manifest.format_id"
-            description: "Production manifest includes format_id"
+            path: "creative_manifest.format_kind"
+            description: "Production manifest includes format_kind"
 
           - check: field_present
             path: "context"
@@ -558,8 +558,8 @@ phases:
           - check: response_schema
             description: "Response matches build-creative-response.json schema"
           - check: field_present
-            path: "creative_manifest.format_id"
-            description: "Generated manifest includes format_id"
+            path: "creative_manifest.format_kind"
+            description: "Generated manifest includes format_kind"
           - check: field_present
             path: "context"
             description: "Response echoes back the context object"
@@ -727,7 +727,7 @@ phases:
           - check: response_schema
             description: "Response matches build-creative-response.json schema"
           - check: field_present
-            path: "creative_manifest.format_id"
+            path: "creative_manifest.format_kind"
             description: "Creative manifest returned"
 
       - id: expect_substitution_safe