Version Packages (beta)#5040
Conversation
![aao-release-bot[bot]](https://avatars.githubusercontent.com/u/221690821?s=60&v=4){kind=small}
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
4d4c47b to
a85f7f1
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
a85f7f1 to
7aec5d0
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
7aec5d0 to
414484d
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
414484d to
e4bdc22
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
e4bdc22 to
d8069c0
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
d8069c0 to
4901293
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
4901293 to
714e146
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
714e146 to
bd15c6b
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
bd15c6b to
47c6d1f
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
47c6d1f to
0b6e87b
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
73f2a8e to
f02f052
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
f02f052 to
aa745cc
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
aa745cc to
0823a32
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
0823a32 to
11a73b6
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
11a73b6 to
7d75ec7
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
7d75ec7 to
8903f91
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
8903f91 to
fa80b93
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
fa80b93 to
6c913a0
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
aao-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
6c913a0 to
e7937db
Compare
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
adcontextprotocol@3.1.0-beta.6
Minor Changes
f23cefc: Add
get_creative_features.audit_observations[]for non-blocking creative governance audit observations.The first standardized observation is
OVERSIGHT_DISCLOSURE_CARVEOUT_CLAIMED, emitted when provenance declareshuman_oversight: editedordirectedwhile also declaringdisclosure.required: false. This surfaces the editorial-responsibility carve-out claim for audit routing without treating it asPROVENANCE_CLAIM_CONTRADICTEDor a rejection reason by itself.Docs now define the seller and governance-agent handling pattern, and a media-buy conformance storyboard exercises the observable flow where a seller calls an on-list verifier and accepts the creative instead of treating the audit observation as a rejection.
Closes provenance: governance-agent flag rule for human_oversight ↔ disclosure.required inconsistency #4438.
057ddf6: compliance: require baseline
sync_governanceregistration in money-moving sales specialismsAdds a
sync_governanceregistration step to the 3.1 beta compliance flows that move or monitor spend:sales-social,sales-catalog-driven,sales-guaranteed,sales-non-guaranteed,sales-broadcast-tv, and the generative seller flow undercreative-generative. The step stops at account-level governance-agent registration and does not addcheck_governanceenforcement to these parent tracks.This remains a minor beta compliance fix under the conformance-suite policy in
docs/reference/versioning.mdx: the wire contract andsync_governancetask already exist, and this PR aligns the beta grader with that existing baseline rather than adding a new protocol surface. Existing beta sellers claiming these money-moving specialisms must now implementsync_governanceregistration and the one-governance-agent rejection rule to remain conformant in 3.1 grading.The
governance-aware-sellerspecialism remains the opt-in claim for the full governance-check loop (check_governance, denial propagation, conditions, and recovery) after baseline registration.8fcf7f9: Add published registry change-feed schemas for
/api/registry/feed.The new
core/registry-feed-response.jsonwrapper referencescore/registry-event.json, which now validates the current registry event vocabulary across property, agent, publisher, and authorization changes. Registry docs and specs now cite the schemas and align examples with the implemented cursor and filter contract.17a648c: Add account-level
notification_configs[]lifecycle and semantic rejection storyboards for 3.1, plus an exactlist_accounts.accountfilter so buyers can re-read one account by seller account ID or natural key. The training agent now supports the new account-level notification configuration contract and the release gates exercise both current 3.1 storyboards and 3.0 compatibility.a091c67: Add
media_buy.creative_approval_modetoget_adcp_capabilitiesso sellers can declare whether human review can block serving eligibility after creatives are assigned and automated validation passes.Sellers with any reachable manual-review workflow declare
require_human, which lets compliance runners skip auto-approval-dependent storyboards instead of reporting false failures. Omission is legacy-unspecified rather than an affirmativeauto_approveclaim; thepending_creatives_to_startstoryboard now runs only when sellers explicitly declareauto_approve.Patch Changes
1ccc37a: Expand the canonical-formats compliance storyboard track for Canonical-formats conformance storyboard track — gates 3.1 GA promotion rubric #4591 with seeded
producer coverage for v1-only, v2-only, custom v2-only, experimental, and
divergent dual-emission product declarations.
The training agent now preserves fixture-seeded
format_options-only productswithout inventing v1 fallbacks, and emits a producer advisory when a dual-emitted
product's
format_options[].v1_format_ref[]does not resolve to that product'sformat_ids[]. The v5 dispatcher and v6 sales adapter both preserve populatedsuccess payloads that carry non-fatal
errors[]advisories.The sales training-agent tenant also advertises the seller-level vendor-metric
optimization capability fields needed to exercise the new vendor-metric
storyboards instead of capability-skipping them.
Add Add vendor_metric discovery-precondition compliance coverage #4983 vendor-metric external-catalog precondition coverage as a separate 3.1
storyboard that accepts either compatibility acceptance or
TERMS_REJECTEDrejection when vendor-catalog membership is unproven by the current harness,
with the future 3.2 true catalog-miss cutover documented in the storyboard narrative.
0ce96be: Add deterministic vendor_metric measurement-catalog-miss coverage for 3.1 storyboards.
7e38ca2: Allow static admin API key callers to read registry compliance diagnostics and outbound monitoring data across seller agents, without granting mutating agent-owner operations.
c17be45: Accept HTTP Basic authentication in the universal
security_baselinecompliance storyboard. Basic credentials now have a dedicated valid/invalid probe path and can satisfyauth_mechanism_verifiedalongside Bearer API keys and OAuth discovery.a091c67: Update the brand-rights governance-denied storyboard to assert
rights_statuson the rejected response arm.d4b7e74: Add a shallow buyer-track canonical-format primer covering
format_options[],format_kind,asset_source, and buyer handling of canonical-formatFORMAT_*codes.9ee8082: Add canonical-format coverage to the S2 creative specialist curriculum, including a hands-on authoring lab, glossary entries, and stable success criteria for targeted recertification.
Foundations and buyer-track learning pages now mention 3.1
format_options[]at orientation depth and point learners to S2 for canonical-first validation details.Recertification trigger wiring is intentionally deferred to the follow-up issue referenced from the PR; this patch only adds stable criterion IDs and curriculum coverage.
Also clarifies that
creative_approval_modeis a discovery declaration for auto-approval-dependent behavior, not a notification or approval workflow.48af987: Add 3.1 creative lifecycle webhook storyboard coverage and training-agent support for account-level creative notification configs.
e30c0b6: Fix the training-agent
get_productshandler to reject non-stringbriefvalues with a structuredINVALID_REQUESTinstead of throwing ontoLowerCase().62af2cc: Allow the ads.txt
managerdomainfallback when a publisher's directadagents.jsonfetch returns an S3/CloudFront-style403AccessDeniedXML response as well as404, while preserving manager-side scoping checks.7390f7f: Prevent protocol tarball signature sidecars from being republished for old
versions, revalidate CDN sidecars, and verify the published tarball tuple with
retries in the release workflow.
a091c67: Gate schema-validation temporal checks with per-step
requires_tool: create_media_buyso agents that do not advertise media-buy creation skip those checks instead of false-failing.