Backport the 3.2 governance scenario declarations (requires_capability, requires: [multi_agent], agent: governance) into 3.1.x so adcp-client#2960 applies to hosted 3.1 grading

[idemidenko]

Summary

adcp-client#2960 (fixes adcp-client#2945) stops a requires_capability-gated scenario from capping a bundle the agent never claimed the capability for, but only for bundles with adcp_version ≥ 3.2, because the 3.1.x copies of the scenarios carry none of the declarations the rule keys on. Its author states the remaining step explicitly:

Closing the legacy case needs the 3.2 declarations (requires_capability, requires: [multi_agent], agent: governance) backported into 3.1.x upstream.

This issue asks for that backport, on the 3.1 line that hosted grading currently pins (compliance_bundle_version: 3.1.20, grading policy hosted-compliance-v1).

Affected scenarios (3.1.20)

• protocols/media-buy/scenarios/governance_approved.yaml
• protocols/media-buy/scenarios/governance_conditions.yaml

Both declare sync_plans as a plain step against the seller under test. In a single-agent hosted run the seller cannot advertise sync_plans (it is a governance-agent task), the step is graded a seller failure, and the storyboard lands partial 4/5 with every seller-owned step passing. That keeps the media_buy bundle partial for a pure seller with nothing wrong, and every 3.1 seller on the dashboard sees "Seller creates buy when governance approves — review Create permissive governance plan" as an action item it cannot act on.

Ask

Backport into 3.1.x the three declarations the 3.2 copies already carry:

• storyboard-level requires_capability: adcp.governance_enforcement.tasks (or the 3.1 spelling of that predicate),
• requires: [multi_agent],
• agent: governance on the sync_plans step.

With those in place adcp-client#2960's rule can apply to 3.1 bundles as well (its version gate currently fails closed below 3.2 precisely because the declarations are absent), and a pure seller's media_buy bundle can reach passing on the line that is actually being graded. If the 3.1 storyboard schema lacks the "Applicability order" text, that paragraph would need to travel with the backport.

Evidence

• Hosted run d2c9f4d0 (2026-09-17, https://sales-agent.elementaltv.io/mcp): governance_approved and governance_conditions each partial 4/5, failing step governance_plan_setup with "Agent did not advertise tool sync_plans"; all four seller-side steps pass. Same in the local runner (14.0.0-rc.35, cache 3.1.20): the CLI grades the step missing_tool and the storyboard passing 4/4, so the CLI and hosted verdicts disagree on 3.1 too.
• adcp-client#2945 (the runner half) and adcp#7550 (the training-agent identity model) carry the rest of the context.

[bokelley]

Thanks for filing!

Triage

Classification: Conformance failure
Bucket(s): compliance suite, spec-adjacent enablement
Status: ready-to-implement
Milestone: P0 Bugs (#8)

What the experts said:

• ad-tech-protocol-expert: Omission vs. siblings confirmed; adcp.governance_enforcement.tasks is 3.2-only — use path: media_buy.governance_aware / equals: true for 3.1.x (see governance_denied.yaml in 3.1.20).
• code-reviewer: Supported in 3.1.23; only requires_capability missing. "Applicability order" text should travel.

My take: Accidental omission — siblings carry all three declarations — causing pure sellers to land partial on a fully-implemented bundle. Additive change on experimental surface; patch-eligible.

• Target: 3.1.x branch, governance_approved.yaml + governance_conditions.yaml in static/compliance/source/protocols/media-buy/scenarios/; do not cherry-pick from main.
• requires: [multi_agent] and agent: governance on sync_plans already present in both source files; only add requires_capability: path: media_buy.governance_aware / equals: true.
• Verify storyboard-schema.yaml on 3.1.x has "Applicability order"; backport in same patch if absent.

---

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

---

Generated by Claude Code