fix(compliance): gate creative-library storyboards and backport 3.0/3.1 packs

[bokelley]

Problem

The published 3.0 and 3.1 compliance packs still select creative-dependent seller scenarios for agents that explicitly advertise:

creative:
  has_creative_library: false

Those agents cannot support the sync_creatives setup used by the scenarios, so the harness reports a compliance failure for behavior that is outside the agent's declared scope.

This was isolated while resolving adcontextprotocol/adcp-client#2401. The remaining fix belongs in the upstream compliance source and generated packs, not in the SDK runner.

Affected scenarios include:

• media_buy_seller/pending_creatives_to_start (3.0 and 3.1)
• media_buy_seller/creative_fate_after_cancellation (3.0 and 3.1)
• media_buy_seller/dependency_impairment (3.1)
• media_buy_seller/dependency_impairment_cardinality (3.1)

The dependency-impairment scenarios declare has_creative_library in required_features, but that is not currently sufficient to prevent selection when tools are auto-registered. The selection path needs an authoritative capability gate.

Proposed fix

Add a source-level scenario or setup-phase gate equivalent to:

requires_capability:
  path: creative.has_creative_library
  equals: true

Apply it consistently to every scenario whose setup or assertions require a creative library. Ensure tool availability or auto-registration cannot override an explicit has_creative_library: false.

Backport requirement

Please implement this in the current compliance source, then backport and regenerate the active AdCP 3.0 and 3.1 packs wherever each scenario exists. At minimum, the currently consumed 3.0.24 and 3.1.15 pack lines need corrected published artifacts and indexes.

This must not be fixed only on the newest protocol line: SDK users testing 3.0 and 3.1 sellers need the corrected storyboard selection behavior.

Acceptance criteria

• An agent declaring creative.has_creative_library: false skips these scenarios rather than failing them.
• An agent declaring creative.has_creative_library: true still runs them.
• Tool auto-registration does not bypass the capability gate.
• Source storyboards and generated/published 3.0 and 3.1 packs are updated where applicable.
• Pack/index regeneration preserves correct badge and completeness calculations.

Client-side tracking: adcontextprotocol/adcp-client#2401

[bokelley]

Triage

Classification: Conformance coverage gap — agents without creative.has_creative_library run creative-library storyboards they should skip
Bucket(s): compliance-suite, schema
Status: ready-to-implement (split: one patch + one minor)
Milestone: next 3.1.x patch (patch-eligible item); 3.2.0 (minor item)

Experts consulted:

• ad-tech-protocol-expert: Gate semantics are correct (requires_capability: path: creative.has_creative_library, equals: true). Phase-level gating is insufficient — a skipped phase doesn't cascade not_applicable to the whole storyboard; stateful downstream steps instead emit prerequisite_failed, leaving a partial failure rather than a clean skip. Three of the four storyboards already carry a storyboard-level requires_capability for an unrelated capability (propagation_surfaces or creative_approval_mode), so adding a second gate requires a compound AND-gate; YAML silently overrides duplicate keys. A requires_all_capabilities list extension is the clean path. 3.0.x is not an active maintenance line.
• code-reviewer: Confirmed via cascade_rules.sole_stateful_step_exemption in runner-output-contract.yaml (lines 1343–1388) that phase-level skip produces partial failures, not a clean storyboard-level not_applicable. Confirmed that requires_all_capabilities is a schema keyword addition and therefore minor-eligible, not patch-eligible, under the stable-schemas rule in playbook.md. Flagged: badge and completeness-score calculations are denominated by runnable-scenario count; gating these storyboards will shift scores for has_creative_library: false agents, so the changeset must document the expected delta explicitly.

My take: The bug is real and the fix path is clear, but the scope splits across two release lines. One storyboard (creative_fate_after_cancellation.yaml) has no existing scenario-level gate and takes a clean single-field patch to 3.1.x. The other three already occupy the single storyboard-level requires_capability slot with a different predicate, so they need a requires_all_capabilities compound AND-gate — a schema keyword addition that must ride the 3.2.0 minor with coordinated runner support. The 3.0.x backport in the issue title is not feasible; 3.0.x is not an active maintenance line.

---

Work item 1 — Patch to 3.1.x (land on main, cherry-pick)

• static/compliance/source/protocols/media-buy/scenarios/creative_fate_after_cancellation.yaml: add a storyboard-level requires_capability block:

  requires_capability:
    path: creative.has_creative_library
    equals: true

• Regenerate compliance indexes via npm run build:compliance; ship as a new 3.1.x patch semver. No existing dist/compliance/<semver>/ artifacts may be modified.
• Changeset must note the badge/completeness-score shift for has_creative_library: false agents (this scenario moves from their runnable surface to not_applicable).

Work item 2 — Minor (3.2.0)

• Extend static/compliance/source/universal/storyboard-schema.yaml: add an optional requires_all_capabilities list field at storyboard level. AND semantics — every entry must pass for the storyboard to be selected. Each entry has the same shape as the existing requires_capability object (path, equals, contains, not_contains, present).
• Coordinate a minimum @adcp/sdk runner version that parses and enforces requires_all_capabilities before the minor ships. Older runners that silently ignore unknown fields would continue presenting these storyboards to library-less agents, leaving the bug unfixed.
• Apply compound gates to the three remaining storyboards:
  • dependency_impairment.yaml: keep propagation_surfaces contains snapshot; add creative.has_creative_library equals true.
  • dependency_impairment_cardinality.yaml: same compound gate.
  • pending_creatives_to_start.yaml: keep creative_approval_mode equals auto_approve; add creative.has_creative_library equals true.
• Regenerate indexes; ship as 3.2.0. Changeset documents the badge-score delta for all three affected storyboards.

Work item 3 — 3.0.x backport

Not feasible. 3.0.x is not an active maintenance line. Recommend acknowledging the gap in 3.1.x and 3.2.0 release notes rather than a post-GA 3.0.x patch.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_bffc6abe-3084-5200-83cc-bbb7d53d9b62

---

Generated by Claude Code

[mvanhorn]

Implemented in #6713.

[bokelley]

Triage

Status update: PR #6713 (by @mvanhorn) implements Work Item 1 from the prior triage brief — storyboard-level requires_capability gate on creative_fate_after_cancellation.yaml, shipping as a patch to 3.1.x. Good coverage of the independently-mergeable piece.

Linkage flag: The PR currently uses Closes #6701. Since Work Item 2 is not covered — the requires_all_capabilities compound-gate minor for dependency_impairment, dependency_impairment_cardinality, and pending_creatives_to_start (3.2.0) — merging as-is will auto-close this issue and drop its tracking surface. Recommend changing to Refs #6701 so this issue stays open as the tracker for the minor.

Shipped in #6713: creative_fate_after_cancellation capability gate (Work Item 1 / patch).
Remaining in this issue: requires_all_capabilities schema extension + compound gates for three storyboards (Work Item 2 / 3.2.0 minor).

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01L66fB59WNnRfbbpjWDXAnd

---

Generated by Claude Code