Summary
The beta.7 compliance runner fails to compile its own response-validation schema bundle: core/async-response-data.json (a 24-branch anyOf union) references media-buy/get-products-async-response-working.json, and that reference fails to resolve at runtime. Because the broken schema poisons the entire validator instance, every step that requires response validation fails before the agent under test is ever called — cascading into 50+ step failures/skips across deterministic testing, controller seeding, product/delivery seeding, provenance, and pagination storyboards.
Error
can't resolve reference /schemas/3.1.0-beta.7/media-buy/get-products-async-response-working.json
from id /schemas/3.1.0-beta.7/core/async-response-data.json
Likely cause
This is not a missing-file issue in the published package — get-products-async-response-working.json (and its -input-required / -submitted siblings) exist in @adcp/sdk@8.1.0-beta.16's schemas-data/3.1.0-beta.7/media-buy/, each with a matching $id. So the failure is in how the AAO engine loads/resolves its schema bundle at runtime — either the deployed engine runs an SDK build where the file is genuinely absent, or the validator's schema store doesn't register the *-async-response-* files before compiling async-response-data.json. Either way it's runner-side, not a published-package gap.
Blast radius
async-response-data.json is an anyOf over 24 response schemas spanning 6 task families — get_products, create_media_buy, update_media_buy, build_creative, sync_creatives, sync_catalogs (sync + async variants of each). When this one schema fails to compile, it poisons the whole validator instance, so response validation fails for any step that touches it — not just controller seeding.
This is why storyboards whose own response schemas are clean still fail. For example, media-buy/get-products-response.json and signals/get-signals-response.json carry zero async references, yet schema_validation/schema_compliance and signal_owned/discovery fail — because the validator instance never compiled, not because those responses are wrong. Fixing the single broken reference should clear a disproportionately large set of "failures" that are not real agent-implementation issues.
Affected storyboards
Every storyboard with a __controller_seeding__ phase, plus any step performing response validation. Observed:
deterministic_testing/controller_validationdeterministic_testing/deterministic_accountdeterministic_testing/deterministic_media_buydeterministic_testing/deterministic_creativedeterministic_testing/deterministic_deliverydeterministic_testing/deterministic_budgetget_media_buys_pagination_integrity/__controller_seeding__pagination_integrity/__controller_seeding__pagination_integrity_creative_formats/seed_formatsmedia_buy_seller/__controller_seeding__media_buy_seller/available_actions/__controller_seeding__media_buy_seller/create_media_buy_async/__controller_seeding__media_buy_seller/provenance_enforcement/__controller_seeding__media_buy_seller/provenance_truth_of_claim/__controller_seeding__media_buy_seller/provenance_audit_observation/__controller_seeding__media_buy_seller/delivery_reporting/__controller_seeding__media_buy_seller/measurement_accountability/__controller_seeding__media_buy_seller/vendor_metric_accountability/__controller_seeding__media_buy_seller/canonical_formats/__controller_seeding__stale_response_advisory/stale_response_forcing
Likely also impacting response-validation steps whose own schemas are clean (e.g. schema_validation/schema_compliance, signal_owned/discovery, error_compliance) — these fail on the poisoned validator instance, not on the response content.
Impact
Approximately 50+ steps fail or skip as a cascade. The agent under test is never called for these steps — the error occurs in the runner's schema-validation layer before any outbound request is made. This makes it impossible to get an accurate compliance score on beta.7.
Reproducer
Run any storyboard with a __controller_seeding__ phase against any agent on the 3.1-beta compliance target:
npx @adcp/client@latest storyboard run <agent> media_buy_seller --compliance-target 3.1-beta
The error appears on the first seeding step regardless of agent behavior.
Runner version
3.1.0-beta.7
Note
This is a runner-side bug — not an agent implementation issue.
Summary
The beta.7 compliance runner fails to compile its own response-validation schema bundle:
core/async-response-data.json(a 24-branchanyOfunion) referencesmedia-buy/get-products-async-response-working.json, and that reference fails to resolve at runtime. Because the broken schema poisons the entire validator instance, every step that requires response validation fails before the agent under test is ever called — cascading into 50+ step failures/skips across deterministic testing, controller seeding, product/delivery seeding, provenance, and pagination storyboards.Error
Likely cause
This is not a missing-file issue in the published package —
get-products-async-response-working.json(and its-input-required/-submittedsiblings) exist in@adcp/sdk@8.1.0-beta.16'sschemas-data/3.1.0-beta.7/media-buy/, each with a matching$id. So the failure is in how the AAO engine loads/resolves its schema bundle at runtime — either the deployed engine runs an SDK build where the file is genuinely absent, or the validator's schema store doesn't register the*-async-response-*files before compilingasync-response-data.json. Either way it's runner-side, not a published-package gap.Blast radius
async-response-data.jsonis ananyOfover 24 response schemas spanning 6 task families —get_products,create_media_buy,update_media_buy,build_creative,sync_creatives,sync_catalogs(sync + async variants of each). When this one schema fails to compile, it poisons the whole validator instance, so response validation fails for any step that touches it — not just controller seeding.This is why storyboards whose own response schemas are clean still fail. For example,
media-buy/get-products-response.jsonandsignals/get-signals-response.jsoncarry zero async references, yetschema_validation/schema_complianceandsignal_owned/discoveryfail — because the validator instance never compiled, not because those responses are wrong. Fixing the single broken reference should clear a disproportionately large set of "failures" that are not real agent-implementation issues.Affected storyboards
Every storyboard with a
__controller_seeding__phase, plus any step performing response validation. Observed:deterministic_testing/controller_validationdeterministic_testing/deterministic_accountdeterministic_testing/deterministic_media_buydeterministic_testing/deterministic_creativedeterministic_testing/deterministic_deliverydeterministic_testing/deterministic_budgetget_media_buys_pagination_integrity/__controller_seeding__pagination_integrity/__controller_seeding__pagination_integrity_creative_formats/seed_formatsmedia_buy_seller/__controller_seeding__media_buy_seller/available_actions/__controller_seeding__media_buy_seller/create_media_buy_async/__controller_seeding__media_buy_seller/provenance_enforcement/__controller_seeding__media_buy_seller/provenance_truth_of_claim/__controller_seeding__media_buy_seller/provenance_audit_observation/__controller_seeding__media_buy_seller/delivery_reporting/__controller_seeding__media_buy_seller/measurement_accountability/__controller_seeding__media_buy_seller/vendor_metric_accountability/__controller_seeding__media_buy_seller/canonical_formats/__controller_seeding__stale_response_advisory/stale_response_forcingLikely also impacting response-validation steps whose own schemas are clean (e.g.
schema_validation/schema_compliance,signal_owned/discovery,error_compliance) — these fail on the poisoned validator instance, not on the response content.Impact
Approximately 50+ steps fail or skip as a cascade. The agent under test is never called for these steps — the error occurs in the runner's schema-validation layer before any outbound request is made. This makes it impossible to get an accurate compliance score on beta.7.
Reproducer
Run any storyboard with a
__controller_seeding__phase against any agent on the3.1-betacompliance target:The error appears on the first seeding step regardless of agent behavior.
Runner version
3.1.0-beta.7
Note
This is a runner-side bug — not an agent implementation issue.