@adcp/sdk 12.0.6 → 12.1.1

package/compliance/cache/{3.1.2/protocols → 3.1.5.previous/domains}/creative/scenarios/evaluator_auth.yaml

@@ -1,5 +1,5 @@
 id: creative/evaluator_auth
-version: "1.0.0"
+version: "1.0.1"
 title: "Creative evaluator authentication boundary"
 category: creative
 summary: "Verifies that build_creative evaluator pointers use the verifier allowlist, keep credentials out of payloads, and invoke accepted evaluator agents through get_creative_features."
@@ -94,11 +94,11 @@ phases:
           context:
             correlation_id: "creative_evaluator_auth--get_capabilities"
         context_outputs:
-          - key: "supports_evaluator"
+          - name: "supports_evaluator"
             path: "creative.supports_evaluator"
-          - key: "build_capability_id"
+          - name: "build_capability_id"
             path: "creative.supported_formats[0].capability_id"
-          - key: "creative_feature_id"
+          - name: "creative_feature_id"
             path: "governance.creative_features[0].feature_id"
         validations:
           - check: response_schema
@@ -111,6 +111,9 @@ phases:
   - id: evaluator_capability_contract
     title: "Confirm experimental feature declaration"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true"
     narrative: |
       Because evaluator support is experimental, agents that set
@@ -162,6 +165,9 @@ phases:
   - id: reject_off_list_evaluator
     title: "Reject an off-list evaluator URL"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer supplies a well-formed external evaluator URL that is not in the
@@ -219,6 +225,9 @@ phases:
   - id: reject_off_list_feature_agent
     title: "Reject an off-list feature_agent URL"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer supplies a well-formed `feature_agent.agent_url` alongside an
@@ -281,6 +290,9 @@ phases:
   - id: payload_credentials_advisory
     title: "Keep evaluator credentials out of the payload"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer attempts to pass an evaluator API key inside the evaluator
@@ -356,6 +368,9 @@ phases:
   - id: accepted_evaluator_invocation
     title: "Invoke an accepted evaluator"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer supplies an accepted external evaluator URL. The creative agent
@@ -433,6 +448,9 @@ phases:
   - id: accepted_evaluator_unavailable_degrades
     title: "Degrade when an accepted evaluator is unavailable"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       An accepted evaluator can be unreachable or can reject the producing

package/compliance/cache/{3.1.2 → 3.1.5.previous}/domains/media-buy/scenarios/available_actions.yaml

@@ -62,7 +62,13 @@ 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. Keep this fixture non-guaranteed when extending
+      # the scenario; it mirrors the base media-buy flow compatibility fix.
+      delivery_type: "non_guaranteed"
       channels: ["display"]
       format_ids:
         - id: "display_300x250"
@@ -91,7 +97,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

package/compliance/cache/{3.1.2.previous/protocols → 3.1.5.previous/domains}/media-buy/scenarios/inventory_list_no_match.yaml

@@ -59,7 +59,7 @@ phases:
           Return products the seller carries.
         sample_request:
           buying_mode: "brief"
-          brief: "Video inventory on outdoor lifestyle programming. Q3 flight."
+          brief: "Outdoor lifestyle programming. Q3 flight."
           filters:
             is_fixed_price: true
           account:

package/compliance/cache/{3.1.2.previous → 3.1.5.previous}/domains/media-buy/scenarios/inventory_list_targeting.yaml

@@ -63,7 +63,7 @@ phases:
 
         sample_request:
           buying_mode: "brief"
-          brief: "Video inventory on outdoor lifestyle programming. Q3 flight, $30K budget."
+          brief: "Outdoor lifestyle programming. Q3 flight, $30K budget."
           filters:
             is_fixed_price: true
           account:

package/compliance/cache/{3.1.2.previous → 3.1.5.previous}/index.json

@@ -1,7 +1,7 @@
 {
-  "published_version": "3.1.2",
-  "adcp_version": "3.1.2",
-  "generated_at": "2026-07-08T13:55:55.314Z",
+  "published_version": "3.1.5",
+  "adcp_version": "3.1.5",
+  "generated_at": "2026-07-24T14:33:07.340Z",
   "universal": [
     "billing-gate-dispatch",
     "canonical-format-validate-input",

package/compliance/cache/{3.1.2.previous → 3.1.5.previous}/protocols/creative/scenarios/canonical_supported_formats.yaml

@@ -1,5 +1,5 @@
 id: creative/canonical_supported_formats
-version: "1.0.0"
+version: "1.0.1"
 title: "Creative canonical supported formats"
 category: creative
 summary: "Verifies the 3.1 creative-agent canonical path: targetable supported_formats capability IDs, build_creative routing, and unsupported target rejection."
@@ -69,7 +69,7 @@ phases:
           context:
             correlation_id: "creative_canonical_supported_formats--get_capabilities"
         context_outputs:
-          - key: "image_build_capability_id"
+          - name: "image_build_capability_id"
             path: "creative.supported_formats[0].capability_id"
         validations:
           - check: response_schema
@@ -77,10 +77,9 @@ phases:
           - check: field_present
             path: "creative.supported_formats"
             description: "Creative canonical supported formats are advertised"
-          - check: field_value
+          - check: field_present
             path: "creative.supported_formats[0].capability_id"
-            value: "training_image_generation"
-            description: "The image build path has a stable local capability_id"
+            description: "The advertised canonical format entry carries a capability_id for build routing"
           - check: field_value
             path: "creative.supported_formats[0].format.format_kind"
             value: "image"
@@ -91,9 +90,6 @@ phases:
           - check: field_absent
             path: "creative.supported_formats[0].format.format_option_id"
             description: "Creative-agent build routing uses capability_id, not product format_option_id"
-          - check: field_absent
-            path: "creative.supported_formats[1].capability_id"
-            description: "Storyboard fixture only advertises implemented canonical build paths"
           - check: field_value
             path: "context.correlation_id"
             value: "creative_canonical_supported_formats--get_capabilities"

package/compliance/cache/{3.1.2.previous/domains → 3.1.5.previous/protocols}/creative/scenarios/evaluator_auth.yaml

@@ -1,5 +1,5 @@
 id: creative/evaluator_auth
-version: "1.0.0"
+version: "1.0.1"
 title: "Creative evaluator authentication boundary"
 category: creative
 summary: "Verifies that build_creative evaluator pointers use the verifier allowlist, keep credentials out of payloads, and invoke accepted evaluator agents through get_creative_features."
@@ -94,11 +94,11 @@ phases:
           context:
             correlation_id: "creative_evaluator_auth--get_capabilities"
         context_outputs:
-          - key: "supports_evaluator"
+          - name: "supports_evaluator"
             path: "creative.supports_evaluator"
-          - key: "build_capability_id"
+          - name: "build_capability_id"
             path: "creative.supported_formats[0].capability_id"
-          - key: "creative_feature_id"
+          - name: "creative_feature_id"
             path: "governance.creative_features[0].feature_id"
         validations:
           - check: response_schema
@@ -111,6 +111,9 @@ phases:
   - id: evaluator_capability_contract
     title: "Confirm experimental feature declaration"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true"
     narrative: |
       Because evaluator support is experimental, agents that set
@@ -162,6 +165,9 @@ phases:
   - id: reject_off_list_evaluator
     title: "Reject an off-list evaluator URL"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer supplies a well-formed external evaluator URL that is not in the
@@ -219,6 +225,9 @@ phases:
   - id: reject_off_list_feature_agent
     title: "Reject an off-list feature_agent URL"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer supplies a well-formed `feature_agent.agent_url` alongside an
@@ -281,6 +290,9 @@ phases:
   - id: payload_credentials_advisory
     title: "Keep evaluator credentials out of the payload"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer attempts to pass an evaluator API key inside the evaluator
@@ -356,6 +368,9 @@ phases:
   - id: accepted_evaluator_invocation
     title: "Invoke an accepted evaluator"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       The buyer supplies an accepted external evaluator URL. The creative agent
@@ -433,6 +448,9 @@ phases:
   - id: accepted_evaluator_unavailable_degrades
     title: "Degrade when an accepted evaluator is unavailable"
     optional: true
+    requires_capability:
+      path: "creative.supports_evaluator"
+      equals: true
     skip_if: "context.supports_evaluator != true || !context.build_capability_id || !context.creative_feature_id"
     narrative: |
       An accepted evaluator can be unreachable or can reject the producing

package/compliance/cache/{3.1.2.previous/domains → 3.1.5.previous/protocols}/media-buy/scenarios/available_actions.yaml

@@ -62,7 +62,13 @@ 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. Keep this fixture non-guaranteed when extending
+      # the scenario; it mirrors the base media-buy flow compatibility fix.
+      delivery_type: "non_guaranteed"
       channels: ["display"]
       format_ids:
         - id: "display_300x250"
@@ -91,7 +97,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

package/compliance/cache/{3.1.2/domains → 3.1.5.previous/protocols}/media-buy/scenarios/inventory_list_no_match.yaml

@@ -59,7 +59,7 @@ phases:
           Return products the seller carries.
         sample_request:
           buying_mode: "brief"
-          brief: "Video inventory on outdoor lifestyle programming. Q3 flight."
+          brief: "Outdoor lifestyle programming. Q3 flight."
           filters:
             is_fixed_price: true
           account:

package/compliance/cache/{3.1.2.previous → 3.1.5.previous}/protocols/media-buy/scenarios/inventory_list_targeting.yaml

@@ -63,7 +63,7 @@ phases:
 
         sample_request:
           buying_mode: "brief"
-          brief: "Video inventory on outdoor lifestyle programming. Q3 flight, $30K budget."
+          brief: "Outdoor lifestyle programming. Q3 flight, $30K budget."
           filters:
             is_fixed_price: true
           account:

package/compliance/cache/{3.1.2 → 3.1.5.previous}/test-kits/parallel-dispatch-runner.yaml

@@ -142,7 +142,7 @@ cross_response_check_kinds:
 # than wait-and-replay. The runner MUST resolve IDEMPOTENCY_IN_FLIGHT
 # responses to their eventual cached response before applying cross-response
 # checks: when the runner observes IDEMPOTENCY_IN_FLIGHT, it waits the
-# `error.details.retry_after` seconds and retries the SAME idempotency_key
+# top-level `error.retry_after` seconds and retries the SAME idempotency_key
 # (per the buyer-side normative behavior). The cross-response check then
 # operates on the resolved response set, not the raw initial set.
 #

package/compliance/cache/{3.1.2 → 3.1.5.previous}/test-kits/rate-limit-trip-runner.yaml

@@ -31,7 +31,8 @@ description: |
   fires up to `max_attempts` sequential requests with fresh
   `idempotency_key` values and otherwise-identical canonical payloads. On
   the first `RATE_LIMITED` response it captures the request's idempotency
-  key, sleeps `error.details.retry_after` seconds, and then re-submits the
+  key, sleeps the RATE_LIMITED response's top-level `error.retry_after`
+  seconds, and then re-submits the
   same key with the same payload. The cross-step assertion compares the
   replay response against the rate-limit response and fails if the replay
   returned the cached `RATE_LIMITED`.
@@ -57,7 +58,7 @@ harness_mode: black_box
 #   1. A response with envelope error_code = RATE_LIMITED is observed.
 #      The runner captures the request's idempotency_key into the
 #      step's context as `rate_limited_key`, captures the response's
-#      `error.details.retry_after` as `retry_after_seconds`, captures
+#      top-level `error.retry_after` as `retry_after_seconds`, captures
 #      the rate-limit response body for the replay assertion, and
 #      proceeds to the wait + replay phase.
 #
@@ -92,7 +93,7 @@ burst_step_contract:
 # --- Wait + replay mechanism ---
 #
 # When a RATE_LIMITED is observed the runner reads
-# `error.details.retry_after` (seconds), waits that long (capped by
+# the RATE_LIMITED response's top-level `error.retry_after` (seconds), waits that long (capped by
 # `rate_limit_trip.replay_max_wait_seconds`, default 30), then re-submits
 # the rate-limited request:
 #
@@ -110,7 +111,7 @@ burst_step_contract:
 # verified.
 #
 # Sellers returning a `RATE_LIMITED` response without
-# `error.details.retry_after` (or with retry_after = 0) fail with
+# top-level `error.retry_after` (or with retry_after = 0) fail with
 # `missing_retry_after` — the retry hint is required to make rate-limit
 # responses actionable, per L1/security.mdx error semantics.
 
@@ -168,5 +169,5 @@ replay_invariant_check_kinds:
 
 reviewer_checks:
   - "Confirm the seller's idempotency-cache implementation explicitly excludes RATE_LIMITED (and other transient-error) responses from the cached-replay path. Review the storage layer or runbook describing which response classes are persisted under idempotency_key."
-  - "Confirm the seller's rate-limit response carries a usable retry_after value (seconds, integer, > 0, ≤ a documented ceiling). A seller that returns retry_after values larger than buyers' realistic retry windows produces unusable rate-limit signaling."
+  - "Confirm the seller's RATE_LIMITED response carries a usable top-level error.retry_after value (seconds, > 0, ≤ a documented ceiling). A seller that returns retry_after values larger than buyers' realistic retry windows produces unusable rate-limit signaling."
   - "Confirm the seller's rate-limit budget is scoped per (authenticated_agent, account) tuple — not shared across all agents or accounts globally — so one agent's burst cannot exhaust another's budget."

package/compliance/cache/{3.1.2 → 3.1.5.previous}/universal/idempotency.yaml

@@ -541,7 +541,7 @@ phases:
         completes, then returns the cached response with `replayed: true`.
       - **Reject-and-redirect**: the second request returns
         `IDEMPOTENCY_IN_FLIGHT` immediately with
-        `error.details.retry_after`. The buyer retries with the same key
+        top-level `error.retry_after`. The buyer retries with the same key
         after the hint elapses and receives the cached response.
 
       This phase exercises both policies via the parallel_dispatch_runner
@@ -633,7 +633,7 @@ phases:
 
         reviewer_checks:
           - "Confirm the seller's claim-row / unique-constraint implementation backs the observed first-insert-wins behavior, rather than a happy-path race the test happened to avoid (review code or runbook describing the INSERT … ON CONFLICT pattern on the scope tuple)."
-          - "If the seller returned IDEMPOTENCY_IN_FLIGHT on the second dispatch, confirm `error.details.retry_after` was populated with a plausible value (seconds, integer, > 0) and that the cached response was available within the hint window. A seller that consistently overshoots retry_after produces brittle retry timing for buyers."
+          - "If the seller returned IDEMPOTENCY_IN_FLIGHT on the second dispatch, confirm top-level `error.retry_after` was populated with a plausible value (seconds, > 0) and that the cached response was available within the hint window. A seller that consistently overshoots retry_after produces brittle retry timing for buyers."
           - "Confirm the seller's in-flight detection does NOT leak across (authenticated_agent, account_id) scope boundaries — probe with a stolen key from a different scope and verify the response shape and timing match the never-seen-key path."
 
   - id: verify_media_buy_count
@@ -701,7 +701,7 @@ phases:
       idempotency-cache insert-rate limiter trips and a request receives
       `RATE_LIMITED`, the response MUST NOT be cached as the canonical
       replay for that idempotency_key. A buyer retrying with the same key
-      after `error.details.retry_after` elapses MUST observe the real
+      after the RATE_LIMITED response's top-level `error.retry_after` elapses MUST observe the real
       handler result (success or a state-dependent error) — not a cached
       rate-limit response that would persist for the entire replay TTL.
 
@@ -743,7 +743,7 @@ phases:
           requests with fresh UUID v4 idempotency_keys and otherwise-identical
           canonical payloads. On the first response with envelope error_code
           = `RATE_LIMITED`, the runner captures the request's
-          `idempotency_key` and the response's `error.details.retry_after`,
+          `idempotency_key` and the RATE_LIMITED response's top-level `error.retry_after`,
           waits that long (capped by `replay_max_wait_seconds`), and
           re-submits the captured key with the same payload but a distinct
           `context.correlation_id` for traceability.
@@ -805,5 +805,5 @@ phases:
 
         reviewer_checks:
           - "Confirm the seller's idempotency-cache implementation explicitly excludes RATE_LIMITED (and other transient-error) responses from the cached-replay path. Review the storage layer or runbook describing which response classes are persisted under idempotency_key."
-          - "Confirm the seller's RATE_LIMITED response carries a usable retry_after value (seconds, integer, > 0, ≤ a documented ceiling). A seller that returns retry_after values larger than buyers' realistic retry windows produces unusable rate-limit signaling."
+          - "Confirm the seller's RATE_LIMITED response carries a usable top-level error.retry_after value (seconds, > 0, ≤ a documented ceiling). A seller that returns retry_after values larger than buyers' realistic retry windows produces unusable rate-limit signaling."
           - "Confirm the seller's rate-limit budget is scoped per (authenticated_agent, account) tuple — not shared across all agents or accounts globally — so one agent's burst cannot exhaust another's budget."

package/compliance/cache/{3.1.2 → 3.1.5.previous}/universal/runner-output-contract.yaml

@@ -1143,6 +1143,10 @@ cascade_rules:
     `skip_result.reasons.peer_substituted`). Steps that skip with
     `not_applicable`, `missing_tool`, or `missing_test_controller` do NOT
     trigger the cascade when the `sole_stateful_step_exemption` below applies.
+    A stateful step's genuine failure or `peer_branch_taken` skip does NOT
+    cascade onto a sibling phase that shares its `branch_set.id` under `any_of`
+    semantics when the `branch_set_cascade_exemption` below applies — such peers
+    are mutually-exclusive alternatives, not a dependency chain.
   sole_stateful_step_exemption: |
     When ALL of the following hold, the runner MUST NOT cascade
     `prerequisite_failed` to downstream stateful phases:
@@ -1189,6 +1193,60 @@ cascade_rules:
     References: adcp-client#1146 (original `not_applicable` exemption);
     adcp-client#1545 (extension to `missing_tool` / `missing_test_controller`);
     adcp-client-python#550 (adopter pattern that surfaced the cross-runner gap).
+  branch_set_cascade_exemption: |
+    When two or more phases share the same `branch_set.id` with `any_of`
+    semantics, the runner MUST NOT cascade `prerequisite_failed` from one peer
+    onto another peer in the same set. When a branch-set peer grades
+    `passed: false` (its alternative was not the path the agent took) or skips
+    with `peer_branch_taken`, that outcome MUST NOT produce `prerequisite_failed`
+    on any sibling phase sharing its `branch_set.id`. Each peer is graded on its
+    own merits, and the set's `any_of` contribution gate credits whichever peer
+    the agent's behavior satisfied.
+
+    Rationale: `any_of` branch-set peers are mutually-exclusive ALTERNATIVES, not
+    a dependency chain. Exactly one branch is the live path for a given agent
+    (e.g., a seller that supports atomic multi-proposal finalize takes
+    `multi_finalize_atomic_path`; one that correctly rejects it with
+    `MULTI_FINALIZE_UNSUPPORTED` takes `multi_finalize_unsupported_path`), so the
+    non-taken peer(s) failing or skipping is the expected shape, not a
+    prerequisite failure. Absent this exemption, `default_cascade` — which lists
+    genuine failures and `peer_branch_taken` as cascade triggers — lets an
+    earlier peer's by-design non-selection skip a later peer the agent actually
+    satisfied, returning an empty `any_of` gate for a conformant agent.
+
+    Scope — `any_of` only: this exemption applies solely to peers whose shared
+    `branch_set` declares `semantics: any_of`. Branch-set semantics where peers
+    legitimately depend on one another (e.g., a future `all_of`) MUST keep
+    cascading; a runner MUST NOT extend the exemption to them.
+
+    `depends_on`-agnostic: the exemption fires whenever two phases share an
+    `any_of` `branch_set.id`, independent of whether the downstream phase's
+    dependency on the peer is the implicit `default_cascade` ("all prior phases")
+    or an explicit `depends_on` naming the peer. `depends_on` answers whether an
+    edge exists between two phases; the cascade exemptions answer how a skip is
+    classified — orthogonal questions. Neither existing exemption
+    (`peer_substituted`, `sole_stateful_step_exemption`) inspects `depends_on`,
+    and this one does not either. No current storyboard declares `depends_on`
+    between `any_of` peers (they are alternatives, not a chain), but the
+    exemption is defined to hold regardless, so an explicit sibling dependency
+    cannot silently reintroduce the cascade.
+
+    N-ary sets (3+ peers): one or more peers failing or skipping with
+    `peer_branch_taken` exempts EVERY sibling in the set, not only one. The
+    single peer the agent satisfies contributes to the gate; the rest regrade to
+    `peer_branch_taken` without cascading. The rule holds for any set
+    cardinality.
+
+    Cross-set cascade is unaffected: a branch-set peer's genuine failure still
+    cascades `prerequisite_failed` to downstream stateful phases that are NOT
+    members of the same `branch_set.id`, exactly as `default_cascade` specifies.
+    Within-phase grading is likewise unchanged. The exemption is scoped strictly
+    to same-`any_of`-set siblings.
+
+    References: adcp-client#2306 (runner fix implementing this exemption in
+    `cascadeForPhase`); adcp-client#2305 (the bug it closed); adcp#5337 (the
+    diagnostic-visibility thread that root-caused the branch-set cascade gap and
+    confirmed the N-ary and `depends_on`-agnostic behavior empirically).
 
 run_summary:
   description: |

package/compliance/cache/{3.1.2.previous → 3.1.5.previous}/universal/storyboard-schema.yaml

@@ -604,6 +604,13 @@
 #   on setup phases, not on sibling consumption phases that may legitimately
 #   skip on different adopters).
 #
+#   Branch-set peers are exempt from this cross-phase cascade: phases sharing a
+#   `branch_set.id` with `any_of` semantics do NOT cascade `prerequisite_failed`
+#   onto one another (they are mutually-exclusive alternatives, not a chain),
+#   independent of whether the dependency is the implicit default or an explicit
+#   `depends_on`. See `runner-output-contract.yaml >
+#   cascade_rules.branch_set_cascade_exemption`.
+#
 #   References: adcp-client#1161 (field introduction); adcp-client#1711
 #   follow-up + adcp#4750 (deterministic_testing scope tightening that
 #   surfaced the documentation gap).
@@ -1862,7 +1869,7 @@
 #   rule 9 may return `IDEMPOTENCY_IN_FLIGHT` on the second (or later) dispatch
 #   rather than block. The runner MUST resolve `IDEMPOTENCY_IN_FLIGHT` responses
 #   to their eventual cached response before applying these checks: wait
-#   `error.details.retry_after` seconds and retry with the SAME idempotency_key,
+#   top-level `error.retry_after` seconds and retry with the SAME idempotency_key,
 #   exactly as the buyer-side normative behavior specifies. The cross-response
 #   check operates on the resolved response set, not the raw initial set. If
 #   resolution exceeds the runner's step-timeout budget, the step grades
@@ -2164,7 +2171,7 @@
 #   and bullet 8 (insert-rate ceiling). The runner drives a sequential fresh-
 #   key burst against the named mutating-op target until a RATE_LIMITED
 #   response appears, then re-submits the same idempotency_key after waiting
-#   `error.details.retry_after` seconds. The cross-step assertion fails if the
+#   the RATE_LIMITED response's top-level `error.retry_after` seconds. The cross-step assertion fails if the
 #   replay returned the cached RATE_LIMITED response shape.
 #
 #   When `max_attempts` requests complete without producing a RATE_LIMITED

package/dist/lib/auth/oauth/authorization-required.d.mts

@@ -83,6 +83,8 @@ export interface DiscoverAuthorizationOptions {
     allowPrivateIp?: boolean;
     /** Override per-probe HTTP timeout (ms). Default inherits from ssrfSafeFetch (10s). */
     timeoutMs?: number;
+    /** Scoped fetch implementation for the agent, PRM, and AS metadata probes. */
+    fetchFn?: typeof fetch;
     /**
      * If provided, use this `WWW-Authenticate` header verbatim instead of
      * re-probing the agent. Use this when you already have a 401 response in
@@ -125,4 +127,5 @@ export declare function discoverAuthorizationRequirements(agentUrl: string, opti
 export declare function probeAuthChallenge(agentUrl: string, options?: {
     allowPrivateIp?: boolean;
     timeoutMs?: number;
+    fetchFn?: typeof fetch;
 }): Promise<WWWAuthenticateChallenge | null>;

package/dist/lib/auth/oauth/authorization-required.d.ts

@@ -83,6 +83,8 @@ export interface DiscoverAuthorizationOptions {
     allowPrivateIp?: boolean;
     /** Override per-probe HTTP timeout (ms). Default inherits from ssrfSafeFetch (10s). */
     timeoutMs?: number;
+    /** Scoped fetch implementation for the agent, PRM, and AS metadata probes. */
+    fetchFn?: typeof fetch;
     /**
      * If provided, use this `WWW-Authenticate` header verbatim instead of
      * re-probing the agent. Use this when you already have a 401 response in
@@ -125,5 +127,6 @@ export declare function discoverAuthorizationRequirements(agentUrl: string, opti
 export declare function probeAuthChallenge(agentUrl: string, options?: {
     allowPrivateIp?: boolean;
     timeoutMs?: number;
+    fetchFn?: typeof fetch;
 }): Promise<WWWAuthenticateChallenge | null>;
 //# sourceMappingURL=authorization-required.d.ts.map

package/dist/lib/auth/oauth/authorization-required.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"authorization-required.d.ts","sourceRoot":"","sources":["../../../../src/lib/auth/oauth/authorization-required.ts"],"names":[],"mappings":"AAaA,OAAO,EAAE,2BAA2B,EAA0B,MAAM,cAAc,CAAC;AACnF,OAAO,EAAwB,KAAK,wBAAwB,EAAE,MAAM,eAAe,CAAC;AA8DpF;;;;GAIG;AACH,MAAM,WAAW,yBAAyB;IACxC,+BAA+B;IAC/B,QAAQ,EAAE,MAAM,CAAC;IACjB,oFAAoF;IACpF,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,sGAAsG;IACtG,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,6EAA6E;IAC7E,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B;;;;;;OAMG;IACH,oBAAoB,CAAC,EAAE,MAAM,EAAE,CAAC;IAChC,kFAAkF;IAClF,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B,+DAA+D;IAC/D,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,uFAAuF;IACvF,oBAAoB,CAAC,EAAE,MAAM,CAAC;IAC9B,iEAAiE;IACjE,eAAe,CAAC,EAAE,MAAM,EAAE,CAAC;IAC3B;;;;;OAKG;IACH,mBAAmB,CAAC,EAAE,MAAM,EAAE,CAAC;IAC/B,sFAAsF;IACtF,cAAc,CAAC,EAAE,UAAU,GAAG,sBAAsB,CAAC;IACrD,6EAA6E;IAC7E,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,0DAA0D;IAC1D,SAAS,EAAE,wBAAwB,CAAC;CACrC;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,qBAAa,uBAAwB,SAAQ,2BAA2B;IACtE,6EAA6E;IAC7E,QAAQ,CAAC,OAAO,EAAG,qBAAqB,CAAU;IAClD,QAAQ,CAAC,YAAY,EAAE,yBAAyB,CAAC;gBAErC,YAAY,EAAE,yBAAyB,EAAE,OAAO,CAAC,EAAE,MAAM;CAStE;AA+BD;;GAEG;AACH,MAAM,WAAW,4BAA4B;IAC3C,iEAAiE;IACjE,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,uFAAuF;IACvF,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB;;;;OAIG;IACH,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAsB,iCAAiC,CACrD,QAAQ,EAAE,MAAM,EAChB,OAAO,GAAE,4BAAiC,GACzC,OAAO,CAAC,yBAAyB,GAAG,IAAI,CAAC,CAgH3C;AAED;;;;;;;;;;;;GAYG;AACH,wBAAsB,kBAAkB,CACtC,QAAQ,EAAE,MAAM,EAChB,OAAO,GAAE;IAAE,cAAc,CAAC,EAAE,OAAO,CAAC;IAAC,SAAS,CAAC,EAAE,MAAM,CAAA;CAAO,GAC7D,OAAO,CAAC,wBAAwB,GAAG,IAAI,CAAC,CAI1C"}
+{"version":3,"file":"authorization-required.d.ts","sourceRoot":"","sources":["../../../../src/lib/auth/oauth/authorization-required.ts"],"names":[],"mappings":"AAaA,OAAO,EAAE,2BAA2B,EAA0B,MAAM,cAAc,CAAC;AACnF,OAAO,EAAwB,KAAK,wBAAwB,EAAE,MAAM,eAAe,CAAC;AA8DpF;;;;GAIG;AACH,MAAM,WAAW,yBAAyB;IACxC,+BAA+B;IAC/B,QAAQ,EAAE,MAAM,CAAC;IACjB,oFAAoF;IACpF,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,sGAAsG;IACtG,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,6EAA6E;IAC7E,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B;;;;;;OAMG;IACH,oBAAoB,CAAC,EAAE,MAAM,EAAE,CAAC;IAChC,kFAAkF;IAClF,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B,+DAA+D;IAC/D,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,uFAAuF;IACvF,oBAAoB,CAAC,EAAE,MAAM,CAAC;IAC9B,iEAAiE;IACjE,eAAe,CAAC,EAAE,MAAM,EAAE,CAAC;IAC3B;;;;;OAKG;IACH,mBAAmB,CAAC,EAAE,MAAM,EAAE,CAAC;IAC/B,sFAAsF;IACtF,cAAc,CAAC,EAAE,UAAU,GAAG,sBAAsB,CAAC;IACrD,6EAA6E;IAC7E,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,0DAA0D;IAC1D,SAAS,EAAE,wBAAwB,CAAC;CACrC;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,qBAAa,uBAAwB,SAAQ,2BAA2B;IACtE,6EAA6E;IAC7E,QAAQ,CAAC,OAAO,EAAG,qBAAqB,CAAU;IAClD,QAAQ,CAAC,YAAY,EAAE,yBAAyB,CAAC;gBAErC,YAAY,EAAE,yBAAyB,EAAE,OAAO,CAAC,EAAE,MAAM;CAStE;AA+BD;;GAEG;AACH,MAAM,WAAW,4BAA4B;IAC3C,iEAAiE;IACjE,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,uFAAuF;IACvF,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,8EAA8E;IAC9E,OAAO,CAAC,EAAE,OAAO,KAAK,CAAC;IACvB;;;;OAIG;IACH,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAsB,iCAAiC,CACrD,QAAQ,EAAE,MAAM,EAChB,OAAO,GAAE,4BAAiC,GACzC,OAAO,CAAC,yBAAyB,GAAG,IAAI,CAAC,CAiH3C;AAED;;;;;;;;;;;;GAYG;AACH,wBAAsB,kBAAkB,CACtC,QAAQ,EAAE,MAAM,EAChB,OAAO,GAAE;IAAE,cAAc,CAAC,EAAE,OAAO,CAAC;IAAC,SAAS,CAAC,EAAE,MAAM,CAAC;IAAC,OAAO,CAAC,EAAE,OAAO,KAAK,CAAA;CAAO,GACrF,OAAO,CAAC,wBAAwB,GAAG,IAAI,CAAC,CAI1C"}

package/dist/lib/auth/oauth/authorization-required.js

@@ -87,7 +87,7 @@ async function discoverAuthorizationRequirements(agentUrl, options = {}) {
   const allowPrivateIpForHop = (url) => allowPrivateIpOnAgent && agentOrigin !== void 0 && originOf(url) === agentOrigin;
   let challengeHeader = options.wwwAuthenticate;
   if (!challengeHeader) {
-    const probe = await probeAgent401(agentUrl, allowPrivateIpOnAgent, options.timeoutMs);
+    const probe = await probeAgent401(agentUrl, allowPrivateIpOnAgent, options.timeoutMs, options.fetchFn);
     if (probe.status !== 401) {
       return null;
     }
@@ -107,7 +107,8 @@ async function discoverAuthorizationRequirements(agentUrl, options = {}) {
     const prm = await fetchJson(
       challenge.resource_metadata,
       allowPrivateIpForHop(challenge.resource_metadata),
-      options.timeoutMs
+      options.timeoutMs,
+      options.fetchFn
     );
     if (prm && typeof prm === "object") {
       const resource = prm.resource;
@@ -127,7 +128,7 @@ async function discoverAuthorizationRequirements(agentUrl, options = {}) {
     let md;
     let source;
     if (asUrl) {
-      const res = await fetchJson(asUrl, allowPrivateIpForHop(asUrl), options.timeoutMs);
+      const res = await fetchJson(asUrl, allowPrivateIpForHop(asUrl), options.timeoutMs, options.fetchFn);
       if (res && typeof res === "object") {
         md = res;
         source = "rfc-8414";
@@ -136,7 +137,7 @@ async function discoverAuthorizationRequirements(agentUrl, options = {}) {
     if (!md) {
       const oidcUrl = buildOidcDiscoveryUrl(requirements.authorizationServer);
       if (oidcUrl) {
-        const res = await fetchJson(oidcUrl, allowPrivateIpForHop(oidcUrl), options.timeoutMs);
+        const res = await fetchJson(oidcUrl, allowPrivateIpForHop(oidcUrl), options.timeoutMs, options.fetchFn);
         if (res && typeof res === "object") {
           md = res;
           source = "openid-configuration";
@@ -167,11 +168,11 @@ async function discoverAuthorizationRequirements(agentUrl, options = {}) {
   return requirements;
 }
 async function probeAuthChallenge(agentUrl, options = {}) {
-  const probe = await probeAgent401(agentUrl, options.allowPrivateIp ?? false, options.timeoutMs);
+  const probe = await probeAgent401(agentUrl, options.allowPrivateIp ?? false, options.timeoutMs, options.fetchFn);
   if (probe.status !== 401) return null;
   return (0, import_diagnostics.parseWWWAuthenticate)(probe.wwwAuthenticate ?? null);
 }
-async function probeAgent401(agentUrl, allowPrivateIp, timeoutMs) {
+async function probeAgent401(agentUrl, allowPrivateIp, timeoutMs, fetchFn) {
   const body = JSON.stringify({ jsonrpc: "2.0", id: 1, method: "tools/list" });
   try {
     const res = await (0, import_net.ssrfSafeFetch)(agentUrl, {
@@ -182,7 +183,8 @@ async function probeAgent401(agentUrl, allowPrivateIp, timeoutMs) {
       },
       body,
       allowPrivateIp,
-      ...timeoutMs !== void 0 ? { timeoutMs } : {}
+      ...timeoutMs !== void 0 ? { timeoutMs } : {},
+      ...fetchFn ? { trustedFetchFn: fetchFn } : {}
     });
     return { status: res.status, wwwAuthenticate: res.headers["www-authenticate"] };
   } catch {
@@ -216,13 +218,14 @@ function buildOidcDiscoveryUrl(issuer) {
   const base = u.pathname.endsWith("/") ? `${u.origin}${u.pathname.slice(0, -1)}` : `${u.origin}${u.pathname}`;
   return `${base}/.well-known/openid-configuration`;
 }
-async function fetchJson(url, allowPrivateIp, timeoutMs) {
+async function fetchJson(url, allowPrivateIp, timeoutMs, fetchFn) {
   try {
     const res = await (0, import_net.ssrfSafeFetch)(url, {
       method: "GET",
       headers: { accept: "application/json" },
       allowPrivateIp,
-      ...timeoutMs !== void 0 ? { timeoutMs } : {}
+      ...timeoutMs !== void 0 ? { timeoutMs } : {},
+      ...fetchFn ? { trustedFetchFn: fetchFn } : {}
     });
     if (res.status !== 200) return void 0;
     return (0, import_net.decodeBodyAsJsonOrText)(res.body, res.headers["content-type"]);