@T-UC-010-main-mcp (BR-UC-010-…feature:59) and @T-UC-010-main-rest (:90) both assert media_buy.supported_pricing_models but xfail at the harness fixture — only @T-UC-010-pricing is wired.
Surfaced in #1677, which grades supported_pricing_models on the wire via @T-UC-010-pricing across a2a/mcp/rest with a stronger content check (non-empty + cpm present + enum-valid) than these two presence-only "should include" scenarios. Wiring the two main-flow scenarios pulls in the whole capabilities-response contract (~10 unrelated assertions plus Given steps that don't yet exist), i.e. a UC-010-wide harness task rather than a pricing one.
Tracked as the follow-up so #1677's field is not left with two dormant sibling scenarios.
@T-UC-010-main-mcp(BR-UC-010-…feature:59) and@T-UC-010-main-rest(:90) both assertmedia_buy.supported_pricing_modelsbut xfail at the harness fixture — only@T-UC-010-pricingis wired.Surfaced in #1677, which grades
supported_pricing_modelson the wire via@T-UC-010-pricingacross a2a/mcp/rest with a stronger content check (non-empty +cpmpresent + enum-valid) than these two presence-only "should include" scenarios. Wiring the two main-flow scenarios pulls in the whole capabilities-response contract (~10 unrelated assertions plus Given steps that don't yet exist), i.e. a UC-010-wide harness task rather than a pricing one.Tracked as the follow-up so #1677's field is not left with two dormant sibling scenarios.