@adcp/sdk 15.8.1 → 16.0.0-beta.1

package/compliance/cache/3.2.3/domains/media-buy/scenarios/completed_views_buy_flow.yaml

@@ -1,348 +0,0 @@
-id: media_buy_seller/completed_views_buy_flow
-version: "1.0.0"
-title: "Seller fulfills a video media buy with a completed_views optimization goal (target CPCV)"
-category: media_buy_seller
-summary: "Verifies that a seller advertising completed_views in supported_optimization_metrics can accept a media buy whose metric-kind optimization_goal targets completed views at a buyer-supplied view_duration_seconds, reject view_duration_seconds values not in the product's metric_optimization.supported_view_durations, and report completed_views + completion_rate on delivery. Sibling to reach_buy_flow on the video-completion side: sellers without video inventory (display-only DSPs, retail-media networks, audio-only sellers without video products) grade not_applicable."
-track: media_buy
-
-# Gate: scenario runs only when the seller declares completed_views in
-# media_buy.supported_optimization_metrics (proposed in #4669). Sellers
-# without video inventory or whose video products don't optimize for
-# completion (display-only DSPs, retail-media networks, audio-only
-# sellers without video) grade `not_applicable`, not failing. Gating
-# on the explicit metric in supported_optimization_metrics avoids
-# over-claiming against the broad delivery-tracking community.
-# Requires runner support for the `contains:` matcher (adcp-client >= 7.70).
-requires_capability:
-  path: media_buy.supported_optimization_metrics
-  contains: "completed_views"
-
-required_tools:
-  - get_products
-  - create_media_buy
-  - get_media_buy_delivery
-  - comply_test_controller
-
-invariants:
-  - status.monotonic
-
-narrative: |
-  A "completed-views buy" (CPCV — cost per completed view) is a video or
-  audio media buy whose optimization_goal is metric-kind with metric:
-  completed_views, a buyer-supplied view_duration_seconds (e.g., 2 for
-  Snap/LinkedIn defaults, 6 for TikTok, 15 for Meta ThruPlay), and a
-  target.kind: cost_per target. The view_duration_seconds value MUST be
-  in the product's metric_optimization.supported_view_durations — silent
-  rounding to the seller's nearest supported duration would create
-  measurement discrepancies (a buyer targeting 6-second completion would
-  unknowingly be billed against 2-second or 15-second completion).
-
-  Discriminating behaviors this scenario verifies:
-  1. create_media_buy with metric: completed_views, a view_duration_seconds
-     value declared in the product's supported_view_durations, and a
-     target.kind: cost_per target is accepted.
-  2. create_media_buy with a view_duration_seconds value NOT in the
-     product's supported_view_durations is rejected with INVALID_REQUEST.
-     error.field points at the offending view_duration_seconds path.
-     optimization-goal.json:50-53 makes this requirement explicit:
-     "Sellers must reject goals with unsupported values — silent rounding
-     would create measurement discrepancies."
-  3. get_media_buy_delivery surfaces totals.completed_views and
-     totals.completion_rate on delivery. completion_rate is defined in
-     delivery-metrics.json as completed_views / impressions; sellers
-     optimizing for completed_views MUST populate both fields.
-
-  The 999-second view_duration is chosen for the rejection arm because
-  no honest video product will declare a 999-second duration in
-  supported_view_durations — common values are 2, 6, 15, and 30. A
-  seller that round-trips 999 as accepted is demonstrating they don't
-  validate against their product capability declarations.
-
-agent:
-  interaction_model: media_buy_seller
-  capabilities:
-    - sells_media
-    - supports_non_guaranteed
-  examples:
-    - "CTV sellers optimizing for video completion"
-    - "Social platforms with video completion goals (Meta ThruPlay, TikTok 6-second views)"
-    - "Audio sellers optimizing for podcast/stream completion"
-    - "Online video DSPs with CPCV pricing"
-
-caller:
-  role: buyer_agent
-  example: "Pinnacle Agency (buyer)"
-
-prerequisites:
-  description: |
-    The seller must implement comply_test_controller with simulate_delivery
-    (already required for delivery_reporting). simulate_delivery injects
-    impressions and completed_views so get_media_buy_delivery has something
-    to surface for the completion-optimized buy.
-
-    The buyer fixture supplies a brand, an operator, and video-channel
-    targeting parameters sufficient to exercise the view_duration_seconds
-    binding contract and the unsupported-value rejection.
-  test_kit: "test-kits/acme-outdoor.yaml"
-  controller_seeding: true
-
-fixtures:
-  products:
-    - product_id: "cpcv_video_q2"
-      delivery_type: "non_guaranteed"
-      channels: ["olv"]
-      format_options:
-        - format_option_id: "video_30s"
-          format_kind: "video_hosted"
-          params:
-            duration_ms_exact: 30000
-  pricing_options:
-    - product_id: "cpcv_video_q2"
-      pricing_option_id: "auction_cpm"
-      pricing_model: "cpm"
-      currency: "USD"
-      floor_price: 12.00
-
-phases:
-
-  - id: setup
-    title: "Establish account and discover products"
-    steps:
-      - id: sync_accounts
-        title: "Establish account"
-        task: sync_accounts
-        schema_ref: "account/sync-accounts-request.json"
-        response_schema_ref: "account/sync-accounts-response.json"
-        doc_ref: "/accounts/tasks/sync_accounts"
-        stateful: true
-        expected: |
-          Return the account with account_id and status active.
-        sample_request:
-          accounts:
-            - brand:
-                domain: "acmeoutdoor.example"
-              operator: "pinnacle-agency.example"
-              billing: "operator"
-          idempotency_key: "$generate:uuid_v4#completed_views_buy_flow_setup_sync_accounts"
-        validations:
-          - check: response_schema
-            description: "Response matches sync-accounts-response.json schema"
-          - check: field_present
-            path: "accounts[0].account_id"
-            description: "Account has a platform-assigned ID"
-
-      - id: get_products_for_cpcv
-        title: "Discover video products that support completed_views optimization"
-        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"
-        stateful: false
-        expected: |
-          Return at least one video product whose metric_optimization
-          capabilities include completed_views as an optimization metric and
-          declare supported_view_durations. The buyer selects a duration
-          from that list for the create_media_buy call below.
-        sample_request:
-          idempotency_key: "$generate:uuid_v4#media_buy_seller_completed_views_buy_flow_setup_get_products_for_cpcv"
-          buying_mode: "brief"
-          brief: "Online video / CTV, US adults 25-54. Q2 flight ~$30K, optimizing for completed views at a 6-second threshold with target CPCV."
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-        validations:
-          - check: response_schema
-            description: "Response matches get-products-response.json schema"
-          - check: field_present
-            path: "products"
-            description: "Response contains products"
-
-  - id: create_cpcv_buy
-    title: "Create a completed-views buy at a supported view_duration"
-    narrative: |
-      The buyer creates a media buy whose package carries a metric-kind
-      optimization_goal with metric: completed_views, view_duration_seconds:
-      6 (a common supported value for online video — TikTok native, Meta
-      6-second qualifier), and target.kind: cost_per at $0.05 per completed
-      view. The seller should accept and return a media_buy_id used for
-      subsequent delivery checks.
-
-    steps:
-      - id: create_media_buy_cpcv
-        title: "Create media buy with metric-kind completed_views goal"
-        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"
-        stateful: true
-        expected: |
-          Create the media buy. Response carries a media_buy_id used for
-          subsequent get_media_buy_delivery calls.
-        sample_request:
-          brand:
-            domain: "acmeoutdoor.example"
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-          start_time: "asap"
-          end_time: "2099-06-30T23:59:59Z"
-          packages:
-            - product_id: "cpcv_video_q2"
-              budget: 30000
-              pricing_option_id: "auction_cpm"
-              optimization_goals:
-                - kind: "metric"
-                  metric: "completed_views"
-                  view_duration_seconds: 6
-                  target:
-                    kind: "cost_per"
-                    value: 0.05
-                  priority: 1
-          idempotency_key: "$generate:uuid_v4#completed_views_buy_flow_create_cpcv_buy_create_media_buy"
-        context_outputs:
-          - name: media_buy_id
-            path: "media_buy_id"
-        validations:
-          - check: response_schema
-            description: "Response matches create-media-buy-response.json schema"
-          - check: field_present
-            path: "media_buy_id"
-            description: "Media buy has a platform-assigned ID"
-
-  - id: rejection_unsupported_view_duration
-    title: "Reject a completed_views goal whose view_duration_seconds is not in supported_view_durations"
-    narrative: |
-      Silent acceptance of a view_duration_seconds value not declared in
-      the product's metric_optimization.supported_view_durations is a
-      façade — the seller either rounds to the nearest supported duration
-      (creating measurement discrepancies where the buyer thinks they're
-      paying for 999-second completion but is billed against the rounded
-      duration) or runs without a duration (delivery becomes uncomparable).
-      The seller MUST reject with INVALID_REQUEST and set error.field to
-      the offending view_duration_seconds path. Same shape as the
-      unsupported reach_unit rejection in reach_buy_flow.
-
-      optimization-goal.json:50-53 makes this requirement explicit:
-      "Sellers declare which durations they support in
-      metric_optimization.supported_view_durations. Sellers must reject
-      goals with unsupported values — silent rounding would create
-      measurement discrepancies."
-
-      The literal 999 is chosen because no honest video product will
-      declare a 999-second duration — common values are 2, 6, 15, and 30.
-
-    steps:
-      - id: create_media_buy_with_phantom_view_duration
-        title: "Submit a completed_views goal whose view_duration_seconds is not in supported_view_durations"
-        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"
-        expect_error: true
-        negative_path: payload_well_formed
-        stateful: false
-        expected: |
-          Reject with INVALID_REQUEST. error.field points at the offending
-          view_duration_seconds path. media_buy_id is not allocated.
-        sample_request:
-          brand:
-            domain: "acmeoutdoor.example"
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-          start_time: "asap"
-          end_time: "2099-06-30T23:59:59Z"
-          packages:
-            - product_id: "cpcv_video_q2"
-              budget: 5000
-              pricing_option_id: "auction_cpm"
-              optimization_goals:
-                - kind: "metric"
-                  metric: "completed_views"
-                  view_duration_seconds: 999
-                  target:
-                    kind: "cost_per"
-                    value: 0.05
-          idempotency_key: "$generate:uuid_v4#completed_views_buy_flow_rejection_unsupported_view_duration"
-        validations:
-          - check: error_code
-            allowed_values: ["INVALID_REQUEST"]
-            description: "Seller rejects the unsupported view_duration_seconds with INVALID_REQUEST"
-          - check: field_value
-            path: "errors[0].field"
-            value: "packages[0].optimization_goals[0].view_duration_seconds"
-            description: "Error.field points at the offending view_duration_seconds path (core/error.json defines field as deterministic JSONPath-lite — literal equality)"
-
-  - id: cpcv_delivery
-    title: "Delivery reporting carries completed_views and completion_rate"
-    narrative: |
-      The discriminating assertion of the completed-views buy mode:
-      delivery reporting MUST surface completed_views and completion_rate
-      — not just impressions and spend. The runner injects simulated
-      impressions and completed_views via the test controller, then
-      verifies get_media_buy_delivery returns completed_views +
-      completion_rate on totals.
-
-      completion_rate is defined in delivery-metrics.json as
-      completed_views / impressions; sellers optimizing for completed_views
-      at a target view_duration_seconds are committing to populate both
-      fields on delivery responses.
-
-    steps:
-      - id: simulate_cpcv_delivery
-        title: "Inject impressions + completed_views + spend"
-        task: comply_test_controller
-        requires_tool: comply_test_controller
-        stateful: true
-        expected: |
-          The test controller acknowledges the simulated delivery.
-        sample_request:
-          account:
-            sandbox: true
-          scenario: "simulate_delivery"
-          params:
-            media_buy_id: "$context.media_buy_id"
-            impressions: 500000
-            completed_views: 350000
-            reported_spend:
-              amount: 18000.00
-              currency: "USD"
-        validations:
-          - check: field_value
-            path: "success"
-            allowed_values: [true]
-            description: "Delivery simulation succeeds"
-
-      - id: get_cpcv_delivery
-        title: "Get delivery and verify completed_views + completion_rate metrics"
-        task: get_media_buy_delivery
-        schema_ref: "media-buy/get-media-buy-delivery-request.json"
-        response_schema_ref: "media-buy/get-media-buy-delivery-response.json"
-        doc_ref: "/media-buy/task-reference/get_media_buy_delivery"
-        stateful: true
-        expected: |
-          Delivery response includes totals.completed_views (the completion
-          count at the declared view_duration_seconds threshold) and
-          totals.completion_rate (completed_views / impressions). These two
-          fields are the discriminating output of completed-views
-          optimization and are required on completion-optimized buys.
-        sample_request:
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-          media_buy_ids:
-            - "$context.media_buy_id"
-          include_package_daily_breakdown: true
-        validations:
-          - check: response_schema
-            description: "Response matches get-media-buy-delivery-response.json schema"
-          - check: field_present
-            path: "media_buy_deliveries[0].totals.completed_views"
-            description: "Completed-views count surfaced at the buy level (at the declared view_duration_seconds threshold)"
-          - check: field_present
-            path: "media_buy_deliveries[0].totals.completion_rate"
-            description: "Completion rate surfaced at the buy level (completed_views / impressions)"

package/compliance/cache/3.2.3/domains/media-buy/scenarios/create_media_buy_async.yaml

@@ -1,265 +0,0 @@
-id: media_buy_seller/create_media_buy_async
-version: "1.0.0"
-title: "Seller returns submitted task envelope when create_media_buy goes async"
-category: media_buy_seller
-summary: "Verifies the AdCP-payload wire shape of the submitted-arm response from create_media_buy: status='submitted', task_id present, no media_buy_id and no packages on the envelope."
-track: media_buy
-
-# The submitted response arm is a production protocol path, but forcing a
-# seller into it is a sandbox-only compliance capability. Gate the entire
-# storyboard on the controller scenario advertisement so sellers that cannot
-# deterministically exercise this path skip before phase execution.
-requires_capability:
-  path: compliance_testing.scenarios
-  contains: force_create_media_buy_arm
-
-required_tools:
-  - create_media_buy
-  - comply_test_controller
-
-narrative: |
-  When create_media_buy cannot confirm the buy synchronously — e.g., the seller is
-  routing the request through IO signing, batch processing, or any out-of-band human
-  workflow — the task layer carries the result, not the response. The seller emits the
-  submitted task envelope: status='submitted', task_id present, no media_buy_id, no
-  packages. The buyer then invokes get_task_status with task_id (or waits for a webhook)
-  until the task completes and the media_buy_id arrives in the terminal result.
-
-  This scenario anchors the AdCP-payload-level invariant for that envelope. Three things
-  matter and are easy to regress:
-
-  1. status MUST be the literal string 'submitted' (not 'pending', not a MediaBuyStatus
-     value, not omitted)
-  2. task_id MUST be present at the top of the payload in snake_case on every transport;
-     it is distinct from an A2A transport Task id
-  3. media_buy_id and packages MUST NOT appear on the envelope — they land on the task's
-     completion artifact, not here. Sellers that return media_buy_id with status='submitted'
-     break the buyer's polling contract; buyers cannot tell whether the buy is queued or
-     confirmed.
-
-  Determinism. The submitted arm is implementation-dependent — most sellers route most
-  buys synchronously. To make this storyboard runnable across implementations, the test
-  harness uses comply_test_controller force_create_media_buy_arm to drive the next
-  create_media_buy call into the submitted arm. The directive is keyed to the caller's
-  authenticated sandbox account (account + principal pair). The storyboard applies only
-  when get_adcp_capabilities advertises force_create_media_buy_arm under
-  compliance_testing.scenarios; other sellers skip before phase execution.
-
-  Round-trip integrity. The deterministic task_id is captured from the controller
-  response and reused as the expected task_id on the create_media_buy assertion, so the
-  storyboard catches sellers that fabricate a fresh task_id instead of honoring the
-  registered directive.
-
-  Out of scope (by design). Transport-level wire-shape assertions — including the A2A
-  completed-Task mapping and the prohibition on duplicating task_id in artifact metadata,
-  plus MCP structuredContent envelope details — are runner-side concerns, not storyboard
-  assertions. The runner exercises this scenario against both transports and probes the
-  transport envelope independently. See adcp-client#904 for the runner-side probes; this
-  storyboard provides the deterministic driver.
-
-  The submitted → completed transition (forcing the task to resolve and asserting the
-  completion artifact carries media_buy_id) is deferred to a follow-up scenario. It needs
-  a force_task_completion controller scenario that does not exist yet.
-
-agent:
-  interaction_model: media_buy_seller
-  capabilities:
-    - sells_media
-    - supports_test_controller
-  examples:
-    - "Sellers that route some create_media_buy calls through IO signing or batch processing"
-    - "Any seller exposing comply_test_controller in sandbox mode"
-
-caller:
-  role: buyer_agent
-  example: "Pinnacle Agency (buyer)"
-
-prerequisites:
-  description: |
-    Seller exposes comply_test_controller in sandbox mode and advertises
-    force_create_media_buy_arm under compliance_testing.scenarios. The
-    directive is keyed to the caller's authenticated sandbox account. Sellers
-    that omit the scenario grade not_applicable before phase execution because
-    buyer-initiated requests alone cannot deterministically drive the submitted
-    arm.
-  test_kit: "test-kits/acme-outdoor.yaml"
-  controller_seeding: true
-
-fixtures:
-  accounts:
-    - account_id: "acct_acmeoutdoor_example_sandbox_ac44d6637e8e"
-      fixture:
-        brand:
-          domain: "acmeoutdoor.example"
-        operator: "pinnacle-agency.example"
-        operator_unit:
-          id: "compliance-media_buy_seller_create_media_buy_as-58faf10a"
-        billing: "operator"
-        status: "active"
-        sandbox: true
-  products:
-    - product_id: "async_signed_io_q2"
-      delivery_type: "guaranteed"
-      channels: ["olv"]
-      format_options:
-        - format_option_id: "video_30s"
-          format_kind: "video_hosted"
-          params:
-            duration_ms_exact: 30000
-  pricing_options:
-    - product_id: "async_signed_io_q2"
-      pricing_option_id: "cpm_guaranteed"
-      pricing_model: "cpm"
-      currency: "USD"
-      fixed_price: 18.0
-
-phases:
-  - id: force_submitted_arm
-    title: "Drive next create_media_buy into submitted arm"
-    narrative: |
-      Tell the controller that the next create_media_buy call from the caller's
-      authenticated sandbox account should return the submitted task envelope.
-      The controller stores the directive against the (account, principal) pair
-      and consumes it on the next create_media_buy call. Sellers that do not
-      implement force_create_media_buy_arm return UNKNOWN_SCENARIO and the
-      runner grades this storyboard not_applicable.
-
-    steps:
-      - id: force_arm_submitted
-        title: "Force submitted arm on next create_media_buy"
-        requires_tool: comply_test_controller
-        narrative: |
-          Direct the controller to return the submitted envelope with a
-          deterministic task_id on the buyer's next create_media_buy call. The
-          message field is set to a representative IO-signing explanation so
-          buyers exercising prompt-injection sanitization on submitted.message
-          have a stable string to assert against.
-        task: comply_test_controller
-        comply_scenario: create_media_buy
-        stateful: true
-        context_outputs:
-          - name: forced_task_id
-            path: "forced.task_id"
-        expected: |
-          Return a successful directive:
-          - success: true
-          - forced.arm: submitted
-          - forced.task_id: deterministic task handle the next create_media_buy will return
-
-        sample_request:
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-            operator_unit:
-              id: "compliance-media_buy_seller_create_media_buy_as-58faf10a"
-            sandbox: true
-          scenario: "force_create_media_buy_arm"
-          params:
-            arm: "submitted"
-            task_id: "task_async_signed_io_q2"
-            message: "Awaiting IO signature from sales team; typical turnaround 2–4 hours"
-          context:
-            correlation_id: "create_media_buy_async--force_arm_submitted"
-        validations:
-          - check: field_value
-            path: "success"
-            allowed_values: [true]
-            description: "Controller accepts the directive"
-          - check: field_value
-            path: "forced.arm"
-            value: "submitted"
-            description: "Controller echoes the forced arm"
-          - check: field_present
-            path: "forced.task_id"
-            description: "Controller echoes the deterministic task_id"
-          - check: field_present
-            path: "context"
-            description: "Response echoes back the context object"
-          - check: field_value
-            path: "context.correlation_id"
-            value: "create_media_buy_async--force_arm_submitted"
-            description: "Context correlation_id returned unchanged"
-
-  - id: submitted_arm_response
-    title: "create_media_buy returns submitted task envelope"
-    narrative: |
-      The buyer makes a normal create_media_buy call. Because the controller
-      registered a directive against this sandbox account, the seller MUST emit
-      the submitted task envelope: status='submitted', task_id matching the
-      forced value, no media_buy_id, no packages.
-
-      The response_schema check carries the absence invariant — the submitted
-      arm in create-media-buy-response.json has not.anyOf clauses for both
-      media_buy_id and packages, so a seller that emits either under
-      status='submitted' fails schema validation. The explicit field_value
-      check on status pins the literal 'submitted' value, since a malformed
-      seller might omit the discriminator and still satisfy the parent oneOf
-      via the error or success branch. The task_id check uses the captured
-      $context.forced_task_id so the storyboard fails if the seller ignores
-      the registered directive and fabricates its own task_id.
-
-    steps:
-      - id: create_media_buy_submitted
-        title: "Call create_media_buy and observe the submitted envelope"
-        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: |
-          Return the submitted task envelope:
-          - status: 'submitted' (literal, not a MediaBuyStatus value)
-          - task_id: matches the value registered by force_create_media_buy_arm
-          - no media_buy_id (issued on task completion, not here)
-          - no packages (issued on task completion, not here)
-          - message (optional): seller's explanation of the wait
-
-        sample_request:
-          brand:
-            domain: "acmeoutdoor.example"
-          account:
-            brand:
-              domain: "acmeoutdoor.example"
-            operator: "pinnacle-agency.example"
-            operator_unit:
-              id: "compliance-media_buy_seller_create_media_buy_as-58faf10a"
-            sandbox: true
-          start_time: "asap"
-          end_time: "2099-09-30T23:59:59Z"
-          packages:
-            - product_id: "async_signed_io_q2"
-              budget: 30000
-              pricing_option_id: "cpm_guaranteed"
-          push_notification_config:
-            url: "https://buyer.example/webhooks/adcp"
-            operation_id: "op_create_media_buy_async_submitted"
-            authentication:
-              schemes:
-                - "HMAC-SHA256"
-              credentials: "media-buy-seller-webhook-secret-token"
-          idempotency_key: "$generate:uuid_v4#media_buy_seller_create_media_buy_async_submitted_arm_response_create_media_buy_submitted"
-          context:
-            correlation_id: "create_media_buy_async--create_media_buy_submitted"
-        validations:
-          - check: response_schema
-            description: "Response matches create-media-buy-response.json — submitted-arm not.required clauses block media_buy_id and packages"
-          - check: field_value
-            path: "status"
-            value: "submitted"
-            description: "Status is the literal 'submitted' task-status value, not a MediaBuyStatus"
-          - check: field_present
-            path: "task_id"
-            description: "task_id is present at the top of the AdCP envelope in snake_case and remains distinct from any A2A transport Task id"
-          - check: field_value
-            path: "task_id"
-            value: "$context.forced_task_id"
-            description: "task_id matches the captured value from the controller directive — sellers that fabricate a fresh task_id instead of honoring the registered one fail here"
-          - check: field_present
-            path: "context"
-            description: "Response echoes back the context object"
-          - check: field_value
-            path: "context.correlation_id"
-            value: "create_media_buy_async--create_media_buy_submitted"
-            description: "Context correlation_id returned unchanged"