feat: state machine compliance scenarios for comply#375
Merged
Conversation
Add three new scenarios to the media_buy comply track that test state transition correctness rather than just happy-path tool calls: - media_buy_lifecycle: create -> pause -> resume -> get status -> cancel - terminal_state_enforcement: reject updates to canceled/terminal buys - package_lifecycle: package-level pause/resume independent of media buy Also adds comply observations for valid_actions and pause/resume support. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
media_buytrack that test state machine correctnessmedia_buy_lifecycle: create -> pause -> resume -> get status (valid_actions) -> cancelterminal_state_enforcement: create -> cancel -> try update (expect INVALID_STATE) -> try re-cancel (idempotent)package_lifecycle: package-level pause/resume independent of media buy statusvalid_actionsand pause/resume supportContext: comply currently validates "can you call the tool and get a response" but not "do you implement the state machine correctly." These scenarios exercise the transitions formalized in adcp#1611. Also filed AdCP issues for undocumented state machines: #1612 (creative status), #1613 (account status), #1614 (SI session), #1616 (catalog/creative approval).
Test plan
npm run buildpasses🤖 Generated with Claude Code