compliance(media-buy): available_actions should be runnable by sales-non-guaranteed-only sellers

.changeset/available-actions-non-guaranteed.md

@@ -0,0 +1,6 @@
+---
+---
+
+compliance(media-buy): the `available_actions` scenario uses a non-guaranteed product fixture so `sales-non-guaranteed`-only sellers can run it.
+
+`available_actions.yaml` seeded a guaranteed-only product, so its `create_buy_from_product` step (and the whole available-actions enforcement flow that follows) failed with a terminal `DELIVERY_MODE_NOT_SUPPORTED` for sellers that declare only `specialisms: ["sales-non-guaranteed"]`. The `allowed_actions` behavior the scenario actually grades is delivery-type-agnostic, so the fixture is switched to `non_guaranteed` (floor-priced) — the same fix applied to the base `media_buy_seller` flow. The packaged `dist/compliance/` cache is generated from this source.

static/compliance/source/protocols/media-buy/scenarios/available_actions.yaml

@@ -62,7 +62,12 @@ fixtures:
     - product_id: "available_actions_display"
       name: "Available Actions Display Package"
       description: "Display inventory fixture used to verify product allowed actions become buy available actions."
-      delivery_type: "guaranteed"
+      # Non-guaranteed so this scenario is runnable by sales-non-guaranteed-only
+      # sellers (a guaranteed-only fixture made create_buy_from_product fail with
+      # DELIVERY_MODE_NOT_SUPPORTED, cascading the whole available-actions flow).
+      # The allowed_actions below — what this scenario actually grades — are
+      # delivery-type-agnostic. Mirrors the base media-buy flow fix.
+      delivery_type: "non_guaranteed"
       channels: ["display"]
       format_ids:
         - id: "display_300x250"
@@ -91,7 +96,7 @@ fixtures:
       pricing_option_id: "available_actions_cpm"
       pricing_model: "cpm"
       currency: "USD"
-      fixed_price: 8.0
+      floor_price: 8.0
 
 phases:
   - id: discover_product_action_template