@admoai/sdk-scenarios 1.0.0 → 1.2.0

package/scenarios.feature

@@ -0,0 +1,597 @@
+# GENERATED from scenarios.json — do not edit; regenerate with: go run ./tools/sdkfeaturegen
+#
+# scenarios.json is what the iOS, Android and Flutter manifest runners execute: the live
+# scenarios against a real decision-engine, the @fixture scenarios offline against the golden
+# decision wire shipped in the package. This is its readable rendering: what every AdMoai SDK
+# promises a publisher's app, in the same words for all three. CI regenerates it and fails on
+# any difference, so it cannot drift from what the runners execute.
+# How it is published and kept fresh: docs/guides/sdk-ci.md, Section 7.
+# Manifest schemaVersion: 2
+
+Feature: Cross-SDK decision & tracking contract
+  Shared cross-SDK E2E scenario manifest. ONE definition, executed by a thin interpreter in each
+  SDK, so the three suites cannot drift. Declarative only: given a request, expect an outcome.
+  Sponsored Pin tracking scenarios add `pinTracking`: the point-tracking calls an app makes on
+  the served pins, as data, and the beacons that must reach the engine. Procedural scenarios
+  (log capture, concurrency, retry, TTL waits) stay hand-written per SDK. Mirrored
+  byte-identically into all three repos; a checksum test fails the build if the copies diverge.
+  Every expected value here was verified against a live local decision-engine before being
+  written. `fixtureScenarios` (schemaVersion 2) run offline: each decodes one golden
+  decision-wire file (ui/platform/lib/ad-formats/golden-wire in adhub, shipped in this package
+  under fixtures/golden-wire/) after optional `edits`, and asserts what the publisher's app
+  reads from the decoded creative. `contentKeys` is the exact set of plain content keys (slides
+  and matched points are asserted through their own fields); a key in `contentKeysAbsent` must
+  decode as absent (null), never as an empty string or a placeholder; a null in `metadata` means
+  absent. A runner that does not execute fixtureScenarios must refuse schemaVersion 2.
+
+  @L @native
+  Scenario: L1 — a normal native ad serves with complete, well-formed metadata
+    Given the app requests placement "home"
+    Then an ad is served
+    And exactly 1 decision is returned
+    And the creative carries complete metadata: ad, creative, placement and template ids
+    And the creative's priority is one of standard, sponsorship, house
+    And the creative is not a Journey Ad
+    And the creative's format is "native"
+
+  @L @native
+  Scenario: L5 — a placement with no eligible ad returns a clean no-ad, not an error
+    Given the app requests placement "postroll"
+    Then no ad is served, and the placement answers with a clean no-fill
+    And exactly 1 decision is returned
+
+  @L @native
+  Scenario: L6 — the advertiser block is complete (name, legalName, logoUrl)
+    Given the app requests placement "home"
+    Then an ad is served
+    And the creative names its advertiser: name, legal name and logo
+
+  @L @native
+  Scenario: L7 — the template block carries a non-empty key
+    Given the app requests placement "home"
+    Then an ad is served
+    And the creative names its template
+
+  @L @native
+  Scenario: L8 — a served native ad exposes an impression URL, a click URL and non-empty contents
+    Given the app requests placement "home"
+    Then an ad is served
+    And the creative carries its content fields
+    And the creative exposes an impression URL
+    And the creative exposes at least 1 click URL
+
+  @M
+  Scenario: M1 — count=2 returns at most two creatives, and they are distinct
+    Given the app requests placement "promotions"
+    And placement "promotions" asks for 2 creatives
+    Then an ad is served
+    And exactly 1 decision is returned
+    And at most 2 creatives are returned
+    And the returned creatives are all different
+
+  @M
+  Scenario: M2 — three placements in one request each get their own correctly-keyed decision
+    Given the app requests placement "home"
+    And the app requests placement "promotions"
+    And the app requests placement "search"
+    Then an ad is served
+    And exactly 3 decisions are returned
+    And every requested placement comes back with its own decision
+
+  @M
+  Scenario: M3 — an advertiserId filter still serves that advertiser's ad
+    Given the app requests placement "promotions"
+    And placement "promotions" is restricted to advertiser "advertiser_01JEPGMJXARVYSJA0CAM9FQ79Y"
+    Then an ad is served
+    And the creative names its advertiser: name, legal name and logo
+
+  @M
+  Scenario: M5 — format=native on a mixed placement returns a native ad
+    Given the app requests placement "promotions"
+    And placement "promotions" asks for format "native"
+    Then an ad is served
+    And the creative's format is "native"
+
+  @M
+  Scenario: M6 — format=video on the same mixed placement returns a video ad instead
+    Given the app requests placement "promotions"
+    And placement "promotions" asks for format "video"
+    Then an ad is served
+    And the creative's format is "video"
+
+  @M
+  Scenario: M7 — omitting format still serves — the engine chooses
+    Given the app requests placement "promotions"
+    Then an ad is served
+
+  @M
+  Scenario: M8 — a journey-owned placement and a normal placement resolve independently in ONE request
+    Given the app requests placement "promotions"
+    And the app requests placement "home"
+    And the request carries a fresh session id
+    And the user has opted in to Journey Ads
+    Then an ad is served
+    And exactly 2 decisions are returned
+
+  @P @video
+  Scenario: P1 — a non-skippable JSON video exposes json delivery and five video events (no skip)
+    Given the app requests placement "json_none"
+    Then an ad is served
+    And the creative's format is "video"
+    And the creative is delivered as "json"
+    And the creative exposes exactly 5 video event URLs
+    And the video events include start, first_quartile, midpoint, third_quartile, complete
+
+  @P @video
+  Scenario: P2 — a vast_tag ad exposes its tag URL and surfaces NO engine-side beacons (no double count)
+    Given the app requests placement "vasttag_none"
+    Then an ad is served
+    And the creative is delivered as "vast_tag"
+    And the creative exposes no engine impression URL, because the VAST owns the impression
+    And the creative exposes exactly 0 video event URLs
+    And the creative exposes a VAST tag URL
+
+  @P @video
+  Scenario: P3 — a vast_xml ad exposes base64 that decodes to a VAST document, and no beacons
+    Given the app requests placement "vastxml_none"
+    Then an ad is served
+    And the creative is delivered as "vast_xml"
+    And the creative exposes no engine impression URL, because the VAST owns the impression
+    And the creative exposes exactly 0 video event URLs
+    And the creative's inline VAST XML decodes to a VAST document
+
+  @P @video
+  Scenario: P6 — a skippable video resolves skippability from ENGINE METADATA, plus a sixth skip event
+    Given the app requests placement "json_none_skippable"
+    Then an ad is served
+    And the creative exposes exactly 6 video event URLs
+    And the metadata says the video is skippable
+    And the metadata's skip offset is 5 seconds
+    And the SDK's skippable helper says the video is skippable
+    And the SDK's skip-offset helper returns "5"
+
+  @P @video
+  Scenario: P8 — an end-card video reports its configured endCardMode
+    Given the app requests placement "json_native_endcard"
+    Then an ad is served
+    And the end-card mode is "native_endcard"
+
+  @V @validation
+  Scenario: V1 — an unknown placement key raises a typed validation error, not a silent no-fill
+    Given the app requests placement "definitely_not_a_real_placement"
+    Then the request fails
+    And the SDK surfaces a typed validation error with HTTP status 422
+    And the engine's error code is 10017
+
+  @V @validation
+  Scenario: V3 — an unknown custom-targeting key is rejected by the engine
+    Given the app requests placement "home"
+    And the custom target "not_a_configured_preset" is "x"
+    Then the request fails
+    And the SDK surfaces a typed validation error with HTTP status 422
+    And the engine's error code is 10028
+
+  @V @validation
+  Scenario: V4 — the SDK deduplicates a repeated custom key, so the engine never sees the duplicate that would fail the whole request
+    Sent raw over HTTP this same payload returns 422 code 10031, and the engine aborts
+    validation for the ENTIRE request — every placement, not just the offending target. All
+    three SDKs dedupe by key (last write wins), so a publisher cannot reach that state through
+    the public API. This scenario is the live proof of that guard: it must SERVE, and both
+    placements must come back.
+
+    Given the app requests placement "home"
+    And the app requests placement "promotions"
+    And the custom target "category" is "sports"
+    And the custom target "category" is "news"
+    Then an ad is served
+    And exactly 2 decisions are returned
+    And every requested placement comes back with its own decision
+
+  @V @validation
+  Scenario: V5 — a single valid custom target does not break serving
+    Given the app requests placement "home"
+    And the custom target "category" is "sports"
+    Then an ad is served
+
+  @V @validation
+  Scenario: V6 — a count above the documented maximum is rejected
+    Given the app requests placement "home"
+    And placement "home" asks for 99 creatives
+    Then the request fails
+    And the SDK surfaces a typed validation error with HTTP status 422
+    And the engine's error code is 10016
+
+  @V @validation
+  Scenario: V9 — a request with no placements fails locally, before any network call
+    Given the app requests no placements
+    Then the request fails
+    And the SDK rejects the request itself, before any network call
+
+  @Z @legacy-version
+  Scenario: Z1 — API version 2025-01-01 still serves a native ad and never a journey block
+    Given the app sends X-Decision-Version "2025-01-01"
+    And the app requests placement "home"
+    Then an ad is served
+    And the creative carries complete metadata: ad, creative, placement and template ids
+    And the creative is not a Journey Ad
+
+  @Z @legacy-version
+  Scenario: Z2 — omitting the version header still serves (engine falls back to the oldest active version)
+    Given the app sends no X-Decision-Version header
+    And the app requests placement "home"
+    Then an ad is served
+    And the creative is not a Journey Ad
+
+  @SP @sponsored-pin
+  Scenario: SP1 — a radius search returns the campaign's own shops, nearest first
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 2 pins
+    And the pins are ordered nearest first
+    And every pin is one of the advertiser's locations, with a name and a distance
+
+  @SP @sponsored-pin
+  Scenario: SP2 — a bounds search returns them too — the other shape a map can ask with
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins inside the map area north -33.3, south -33.55, east -70.45, west -70.65, around (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 2 pins
+    And every pin is one of the advertiser's locations, with a name and a distance
+
+  @SP @sponsored-pin
+  Scenario: SP3 — every returned shop carries its own view, tap and click beacons
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And every pin carries its own view, tap and click beacons
+
+  @SP @sponsored-pin
+  Scenario: SP4 — every returned shop carries a resolved destination, its own or the creative's
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And every pin carries a resolved destination URL
+
+  @SP @sponsored-pin
+  Scenario: SP5 — the request's limit narrows how many shops come back
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    And the search asks for at most 2 pins
+    Then an ad is served
+    And the ad carries exactly 2 pins
+
+  @SP @sponsored-pin
+  Scenario: SP6 — a tight radius excludes the shops outside it
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 1500 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries exactly 1 pin
+
+  @SP @sponsored-pin
+  Scenario: SP7 — without a distance search a Sponsored Pin campaign does not serve at all
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    Then no ad is served, and the placement answers with a clean no-fill
+
+  @SP @sponsored-pin
+  Scenario: SP8 — on the older API version the ad still serves, silently carrying no pins — the failure an integrator must recognise
+    Given the app sends no X-Decision-Version header
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries no pins
+
+  @SP @sponsored-pin
+  Scenario: SP9 — a map's first render sends every shop's view beacon exactly once
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 1 pin
+    And every pin carries its own view, tap and click beacons
+    When the app shows every pin
+    Then each shown pin's view beacon reaches the engine exactly once per response, and no pin the app never showed sends one
+    And the engine accepts every beacon
+
+  @SP @sponsored-pin
+  Scenario: SP10 — re-rendering the same response sends no view beacon again
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 1 pin
+    And every pin carries its own view, tap and click beacons
+    When the app shows every pin
+    And the app shows every pin
+    And the app shows every pin
+    Then each shown pin's view beacon reaches the engine exactly once per response, and no pin the app never showed sends one
+    And the engine accepts every beacon
+
+  @SP @sponsored-pin
+  Scenario: SP11 — a render that brings new shops into view sends views only for the new ones
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 4 pins
+    And every pin carries its own view, tap and click beacons
+    When the app shows the first 2 pins
+    And the app shows pins 2 to 4
+    And the app shows the first 4 pins
+    Then each shown pin's view beacon reaches the engine exactly once per response, and no pin the app never showed sends one
+    And the engine accepts every beacon
+
+  @SP @sponsored-pin
+  Scenario: SP12 — a new decision response reports the same shops again, once
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 1 pin
+    And every pin carries its own view, tap and click beacons
+    When the app shows every pin
+    And the app fetches a new decision response for the same search
+    And the app shows every pin
+    And the app shows every pin
+    Then each shown pin's view beacon reaches the engine exactly once per response, and no pin the app never showed sends one
+    And a new response carries new view beacons for the same pins
+    And the engine accepts every beacon
+
+  @SP @sponsored-pin
+  Scenario: SP13 — single-pin views follow the same once-per-response rule as the bulk call
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 1 pin
+    And every pin carries its own view, tap and click beacons
+    When the app shows pin 1 on its own
+    And the app shows pin 1 on its own
+    And the app shows every pin
+    And the app shows pin 1 on its own
+    Then each shown pin's view beacon reaches the engine exactly once per response, and no pin the app never showed sends one
+    And the engine accepts every beacon
+
+  @SP @sponsored-pin
+  Scenario: SP14 — taps and clicks are sent on every call, never de-duplicated
+    Given the app sends X-Decision-Version "2025-11-01"
+    And the app requests placement "poi"
+    And the app searches for pins within 20000 m of (-33.4175, -70.6065)
+    Then an ad is served
+    And the ad carries at least 1 pin
+    And every pin carries its own view, tap and click beacons
+    When the app shows every pin
+    And the user taps pin 1
+    And the user taps pin 1
+    And the user clicks pin 1
+    And the user clicks pin 1
+    And the app shows every pin
+    Then each shown pin's view beacon reaches the engine exactly once per response, and no pin the app never showed sends one
+    And every tap and every click sends its beacon, on every call
+    And the engine accepts every beacon
+
+  @F @fixture
+  Scenario: F1 — a Native Display creative exposes its standard format, version and template source
+    Given the app decodes the golden card.full response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "card"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "card"
+    And the creative's contents are exactly "image", "brand_logo", "headline", "supporting_text", "cta_text", "destination_url"
+    And the click trackers are exactly "default"
+    And the creative has no custom event tracker
+
+  @F @fixture
+  Scenario: F2 — a Native Display creative leaves every optional field it was served without absent
+    Given the app decodes the golden card.minimal response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "card"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "card"
+    And the creative's contents are exactly "image", "destination_url"
+    And "brand_logo", "headline", "supporting_text", "cta_text" decode as absent, never as an empty string or a placeholder
+    And the click trackers are exactly "default"
+    And the creative has no custom event tracker
+
+  @F @fixture
+  Scenario: F3 — a template based on a standard keeps the standard's identity and exposes the operator's addition by key
+    Given the app decodes the golden card.derived response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "card"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "based_on_standard"
+    And the template key is "city_promo_display"
+    And the creative's contents are exactly "image", "headline", "destination_url", "promo_code"
+    And the click trackers are exactly "default"
+    And the custom event trackers are exactly "save_offer"
+
+  @F @fixture
+  Scenario: F4 — a Carousel exposes its slides in server order, each with its id, position, contents and own trackers, and no creative-level click
+    Given the app decodes the golden carousel.full response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "carousel"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "carousel"
+    And the creative's contents are exactly "brand_logo", "disclaimer"
+    And the creative has no click tracker
+    And the creative has no custom event tracker
+    And there are 3 slides in server order
+    And slide 1 is "slide_01JDY02N8MA2K2HKQ74989YS99" with contents "image", "headline", "supporting_text", "cta_text", "destination_url", view trackers "slide_view" and click trackers "default"
+    And slide 2 is "slide_01JD04H8GY801VF8Y0FHETP6XA" with contents "image", "headline", "supporting_text", "cta_text", "destination_url", view trackers "slide_view" and click trackers "default"
+    And slide 3 is "slide_01JDRGMFSTZXQ7ES1QBCF0DR2X" with contents "image", "headline", "supporting_text", "cta_text", "destination_url", view trackers "slide_view" and click trackers "default"
+
+  @F @fixture
+  Scenario: F5 — a minimal Carousel still exposes its slides and leaves the optional brand logo and disclaimer absent
+    Given the app decodes the golden carousel.minimal response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "carousel"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "carousel"
+    And the creative has no plain contents
+    And "brand_logo", "disclaimer" decode as absent, never as an empty string or a placeholder
+    And the creative has no click tracker
+    And the creative has no custom event tracker
+    And there are 2 slides in server order
+    And slide 1 is "slide_01JDZ725G8017BHW9RQJX7Y56S" with contents "image", "destination_url", view trackers "slide_view" and click trackers "default"
+    And slide 2 is "slide_01JD4GNH6TH0XPP5YWCMDKN029" with contents "image", "destination_url", view trackers "slide_view" and click trackers "default"
+
+  @F @fixture
+  Scenario: F6 — a Carousel based on a standard exposes its slides and the operator's addition
+    Given the app decodes the golden carousel.derived response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "carousel"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "based_on_standard"
+    And the template key is "city_carousel"
+    And the creative's contents are exactly "promo_code"
+    And the creative has no click tracker
+    And the creative has no custom event tracker
+    And there are 2 slides in server order
+    And slide 1 is "slide_01JDS1H8VEM0ABE2PQ0JY6S38W" with contents "image", "destination_url", view trackers "slide_view" and click trackers "default"
+    And slide 2 is "slide_01JDDGXJE0JDBY21Y9KEJDD54A" with contents "image", "destination_url", view trackers "slide_view" and click trackers "default"
+
+  @F @fixture
+  Scenario: F7 — a Tap-to-expand creative exposes expand and close as custom events, apart from its click
+    Given the app decodes the golden expandable_banner.full response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "expandable_banner"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "expandable_banner"
+    And the creative's contents are exactly "teaser_image", "teaser_headline", "expanded_image", "headline", "supporting_text", "cta_text", "destination_url", "disclaimer"
+    And the click trackers are exactly "default"
+    And the custom event trackers are exactly "expand", "close"
+
+  @F @fixture
+  Scenario: F8 — a minimal Tap-to-expand creative leaves its optional texts absent and keeps expand and close
+    Given the app decodes the golden expandable_banner.minimal response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "expandable_banner"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "expandable_banner"
+    And the creative's contents are exactly "teaser_image", "expanded_image", "destination_url"
+    And "teaser_headline", "headline", "supporting_text", "cta_text", "disclaimer" decode as absent, never as an empty string or a placeholder
+    And the click trackers are exactly "default"
+    And the custom event trackers are exactly "expand", "close"
+
+  @F @fixture
+  Scenario: F9 — a Branded Assets creative exposes asset tap as a custom event, apart from its click
+    Given the app decodes the golden branded_assets.full response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "branded_assets"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "branded_assets"
+    And the creative's contents are exactly "branded_image", "accessible_label", "destination_url"
+    And the click trackers are exactly "default"
+    And the custom event trackers are exactly "asset_tap"
+
+  @F @fixture
+  Scenario: F10 — a Branded Assets creative without a destination has no click, only the asset tap
+    Given the app decodes the golden branded_assets.minimal response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "branded_assets"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "branded_assets"
+    And the creative's contents are exactly "branded_image"
+    And "accessible_label", "destination_url" decode as absent, never as an empty string or a placeholder
+    And the creative has no click tracker
+    And the custom event trackers are exactly "asset_tap"
+
+  @F @fixture
+  Scenario: F11 — a Standard Video exposes its video events and click, and no skippable setting
+    Given the app decodes the golden standard_video.full response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "standard_video"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "standard_video"
+    And the creative's contents are exactly "video_asset", "poster_image", "brand_logo", "headline", "supporting_text", "cta_text", "destination_url", "disclaimer"
+    And the click trackers are exactly "default"
+    And the creative has no custom event tracker
+    And the video event trackers are exactly "start", "first_quartile", "midpoint", "third_quartile", "complete"
+    And the creative exposes no skippable setting
+
+  @F @fixture
+  Scenario: F12 — a Standard Video without a destination has no click action or click tracker
+    Given the app decodes the golden standard_video.minimal response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "standard_video"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "standard_video"
+    And the creative's contents are exactly "video_asset", "poster_image"
+    And "brand_logo", "headline", "supporting_text", "cta_text", "destination_url", "disclaimer" decode as absent, never as an empty string or a placeholder
+    And the creative has no click tracker
+    And the creative has no custom event tracker
+    And the video event trackers are exactly "start", "first_quartile", "midpoint", "third_quartile", "complete"
+    And the creative exposes no skippable setting
+
+  @F @fixture
+  Scenario: F13 — a Sponsored Pin creative keeps decoding its matched points as it does today
+    Given the app decodes the golden sponsored_pin_location.full response
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "sponsored_pin_location"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "sponsored_pin_location"
+    And the creative's contents are exactly "pinImage", "image", "headline", "description", "ctaText", "defaultDestinationUrl"
+    And the click trackers are exactly "default"
+    And the creative has no custom event tracker
+    And the creative exposes 2 matched points
+
+  @F @fixture
+  Scenario: F14 — a creative served before the standards (gate off) decodes as today, with the three standard fields absent
+    The engine omits the three standard fields while is_standard_native_formats_enabled is off;
+    this is that wire. Absent means null, never an empty string or a placeholder (BR-SDK-01,
+    BR-SDK-09).
+
+    Given the app decodes the golden card.full response
+    And with the metadata field "effectiveStandardFormatKey" removed
+    And with the metadata field "effectiveStandardFormatVersion" removed
+    And with the metadata field "templateSource" removed
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is absent
+    And the creative's effectiveStandardFormatVersion is absent
+    And the creative's templateSource is absent
+    And the template key is "card"
+    And the creative's contents are exactly "image", "brand_logo", "headline", "supporting_text", "cta_text", "destination_url"
+    And the click trackers are exactly "default"
+    And the creative has no custom event tracker
+
+  @F @fixture
+  Scenario: F15 — fields the SDK does not know yet, at any level, never break decoding
+    An additive field the engine starts sending later must be ignored, not fail the response
+    (BR-SDK-01).
+
+    Given the app decodes the golden carousel.full response
+    And with an unknown response field "futureField" added
+    And with an unknown creative field "futureField" added
+    And with an unknown metadata field "futureField" added
+    And with an unknown content field "futureField" added on every content entry
+    And with an unknown slide field "futureField" added on every slide
+    Then the response decodes
+    And the creative's effectiveStandardFormatKey is "carousel"
+    And the creative's effectiveStandardFormatVersion is 1
+    And the creative's templateSource is "admoai_standard"
+    And the template key is "carousel"
+    And the creative's contents are exactly "brand_logo", "disclaimer"
+    And the creative has no click tracker
+    And the creative has no custom event tracker
+    And there are 3 slides in server order
+    And slide 1 is "slide_01JDY02N8MA2K2HKQ74989YS99" with contents "image", "headline", "supporting_text", "cta_text", "destination_url", view trackers "slide_view" and click trackers "default"
+    And slide 2 is "slide_01JD04H8GY801VF8Y0FHETP6XA" with contents "image", "headline", "supporting_text", "cta_text", "destination_url", view trackers "slide_view" and click trackers "default"
+    And slide 3 is "slide_01JDRGMFSTZXQ7ES1QBCF0DR2X" with contents "image", "headline", "supporting_text", "cta_text", "destination_url", view trackers "slide_view" and click trackers "default"