Fix for #6725 (compliance_testing.scenarios closed-enum check) ships only on adcp-client 14.x, but graded compliance cache 3.1.20 ships only on 13.x — no release carries both

[idemidenko]

Follow-up to #6725

#6725 (compliance runner validating compliance_testing.scenarios against a closed 6-value TS union despite the schema declaring an open string type) is closed, but still reproduces on the line actually graded against hosted agents.

Reproduction

Against https://sales-agent.elementaltv.io/mcp, cache 3.1.20, @adcp/sdk@13.0.2: 9 of 14 declared scenarios log must be one of: force_creative_status, force_account_status, force_media_buy_status, force_session_status, simulate_delivery, simulate_budget_spend on every get_adcp_capabilities call.

Root cause: packaging split, not an unfixed bug

The fix landed in adcp-client#2663, but:

• 14.0.0-rc.33 (which carries the fix) ships only compliance cache 3.1.18
• The cache actually graded against hosted agents, 3.1.20, ships only on the 13.x line, which does not carry the fix

There is currently no published release that carries both the #6725 fix and the compliance cache being graded. Implementers are forced to choose between a correct runner and the cache that hosted grading actually uses.

Impact

Any seller advertising more than the 6 hardcoded scenario values gets spurious advisory failures on every capabilities probe, and there is no available upgrade path to resolve it without losing conformance against the currently-graded cache.

Ask

The packaging split itself is the more urgent fix here — either backport the #6725 fix to whatever line ships 3.1.20, or promote a 3.1.20-carrying line that includes it. Same shape of problem as #6730 (fix exists upstream, not reachable through what's actually graded).

[bokelley]

Triage

Classification: Conformance failure (Bug)
Bucket(s): compliance-suite
Status: ready-for-human

What the experts said:

• ad-tech-protocol-expert: Schema is already correct — compliance_testing.scenarios.items is {"type": "string"} with no enum constraint and the description explicitly states values MAY include implementation-specific scenarios. No protocol repo action needed. Backport of adcp-client#2663 to the 13.x line is the minimum fix; P0 given precedent from Fix for #6459 (rate-limit not_applicable grading) shipped in 3.1.15 but not promoted to published_versions — hosted grading unaffected #6730 (same pattern: fix exists, not reachable through graded artifacts).
• code-reviewer: Confirmed via static/schemas/source/compliance/comply-test-controller-request.json — "Runners and sellers MUST accept unknown scenario strings." No defensible shim exists in this repo; the schema is not the bug. published-versions.json already lists 3.1.20 in published_versions, so no change is needed here. Backport to 13.x + cut a patch is the clean path.

My take: The packaging split leaves no published release that carries both the validation fix and the graded compliance cache — sellers with more than 6 scenarios get spurious advisory failures with no available upgrade path. This repo's schema is correct; the fix lives entirely in adcp-client.

@bokelley, your call: (A) backport adcp-client#2663 to the 13.x line and cut a patch that bundles compliance cache 3.1.20 (preferred — smaller delta, leaves hosted grading undisturbed), or (B) cut a new 14.x release that bundles 3.1.20 alongside the existing fix.

Sibling-repo-fix-needed: adcontextprotocol/adcp-client — backport of PR #2663 to the 13.x stable line, then cut a patch release bundling compliance cache 3.1.20. Same shape as #6730.

---

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

---

Generated by Claude Code

[bokelley]

Human triage decision: proceed with option A — backport adcp-client#2663 to the 13.x stable line and cut a patch release that bundles compliance cache 3.1.20. This keeps the hosted grading target unchanged and minimizes release delta.