Storyboard runner may not auto-skip measurement_terms_accepted step when capability not declared

[annamedvedieva-teqblaze]

Storyboard: media-buy — Media buy seller agent, step propose_seller_compatible_measurement_terms (create_media_buy)

Observed: Step fails with TERMS_REJECTED: Proposed measurement_terms are outside the supported envelope... measurement_window 'c7' is not a window this seller guarantees instead of being graded not_applicable.

Reporter's claim: Their agent does not declare media_buy.measurement_terms_acceptance: true in get_adcp_capabilities (media_buy block only has features, content_standards, execution, portfolio), so per the storyboard-troubleshooting doc's "Capability-vector mismatch" section, this step should be skipped by requires_capability gating rather than dispatched and graded as a failure. Reporter also notes similar false failures earlier in the same session (si_send_message, parallel_dispatch_runner).

Not yet independently verified:

• Whether media_buy.measurement_terms_acceptance is the correct/documented capability key path in the schema (vs. the agent declaring it at a wrong key).
• The exact content of the measurement_terms_rejected.yaml scenario file referenced by the reporter.

Per the troubleshooting doc, this class of failure has two possible root causes: (a) the capability is declared at the wrong key by the agent, or (b) the runner is missing the auto-skip path for this gate. This issue is filed to have someone with schema/runner access confirm which applies here, given the reporter says this is the third such false-failure pattern observed in one session.

Ask: Confirm the correct key path for measurement-terms-acceptance capability gating, and check whether the runner's requires_capability auto-skip is actually wired up for the measurement_terms_accepted scenario in the media-buy storyboard.

[bokelley]

Triage

Thanks for filing!

Classification: Conformance failure
Bucket(s): compliance-suite, spec-adjacent enablement
Status: ready-to-implement
Milestone: Spec Backlog

What the experts said:

• ad-tech-protocol-expert: Key path media_buy.measurement_terms_acceptance is correct everywhere — root cause A (wrong key) is ruled out because a wrong key would give not_applicable, but TERMS_REJECTED means the runner dispatched the step, confirming the requires_capability gate is not firing on the live path.
• code-reviewer: sdk-runner-capability-gates.test.cjs uses _profile.raw_capabilities injection rather than a mock get_adcp_capabilities response, leaving two gaps: (1) the absent-key case is never tested (only explicit false), and (2) the production capability-fetch code path is never exercised. The three-scenario false-failure pattern across measurement_terms_accepted, si_send_message, and parallel_dispatch_runner is inconsistent with a one-off YAML error and strongly consistent with systematic divergence in the live path.

My take: The storyboard YAML and schema are correct; the bug is in the runner's live get_adcp_capabilities-driven capability resolution diverging from the injected-profile path that the tests cover.

Implementation scope:

• tests/sdk-runner-capability-gates.test.cjs: (1) Add absent-key test (raw_capabilities: {media_buy: {}}) asserting capability_unsupported. (2) Add a test wiring a mock _client that returns a get_adcp_capabilities response without measurement_terms_acceptance, exercising the production fetch path rather than profile injection.
• Sibling-repo fix needed — adcp-client: Audit whether requires_capability gate evaluation on the live get_adcp_capabilities response shares the same field-traversal logic as profile injection. The three-scenario pattern confirms this is the load-bearing fix.
• No changeset needed (test-only change here; YAML and schema are correct and unchanged).

---

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

---

Generated by Claude Code