Skip to content

fix(schemas): open schemas that were closed by accident (3.2.x backport) - #8864

Merged
bokelley merged 12 commits into
3.2.xfrom
fix/open-closed-schemas-3-2-x
Nov 12, 2026
Merged

bokelley merged 12 commits into
3.2.xfrom
fix/open-closed-schemas-3-2-x

Conversation

@bokelley

@bokelley bokelley commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The 3.2.x backport of the working group decision of 2026-11-09: 3.x opens the schemas that were meant to be open. A 3.2 validator should not reject a newer 3.x payload just because a schema was closed.

Source of truth: #8866 (3.3, merged into main as 2dc672e316) owns the classification and the named rejections, including Konstantin Mirin's review of it. This PR mirrors #8866's final state node by node.

Approval: Brian approved the keep-closed (b) list as the 3.3 inventory had it on 2026-11-09, relayed by the release-planning agent. The review changes below were decided on #8866 and mirrored here.

Important

Ready for review. Brian merges (gated schema paths). No auto-merge. Hold the 3.2.11 Version Packages PR #8942 until this PR has merged and release.yml has regenerated #8942 to include this changeset.

Classification on 3.2.x

The tree was inventoried with the same inventory.py/classify.py as 3.3 and classified by the same rules.

Count
Closed locations on 3.2.x before this PR 775 in 342 files
Opened (class a) 674
Kept closed (class b) 101 in 48 files
Locations shared with #8866 (747 open / 112 closed) 772: every one has the same class
oneof_risk pairs on 3.2.x 4 (a2ui/bound-value 0/4 and 3/4, brand.json 1/3 and 2/4), all inside the kept-closed set

Kept closed, by reason:

Reason Locations Files
oneOf disjointness 9 a2ui/bound-value.json, brand.json
Join keys (metric qualifiers, forecast dimensions) 21 canonical-metric-qualifier, the qualifier objects, forecast-dimension-*
Signature envelope 1 response-payload-jws-envelope
Privacy boundary 20 TMP identity-match-request / context-match-request, catalog-item-reference-not-found-error, agent-permission-denied, billing-not-permitted-for-agent, get-principal-response (recognized, unconfigured, failed), sync-principal-response (failed), get-reporting-status-response (unavailable lookup)
Credential-free reporting destinations 10 agent-reporting-destination, reporting-write-destination, reporting-dataset-share-destination
No free text to agents 1 agent-reporting-destination-state setup
No key material or markup 8 placement-presentation
Maps keyed by identifier (patternProperties) 5 creative-asset, creative-manifest, creative-localization, creative-localization-readback, list-creatives-response
Held closed until 4.0 (commercial terms; a hold, not a structural reason) 26 commercial-terms, product-purchase, change-term, change-term-constraints, sla-window, canonical-measurement-terms, canonical-performance-standard, canonical-reporting-commitment, canonical-pricing-option, canonical-budget-allocation, bidding-policy, proposal-budget-constraint

Named rejections

Of #8866's 64 not clauses (unchanged through its merge as 2dc672e316), 46 apply on 3.2.x and are present at the same pointers with the same value. The other 18 target schemas or nodes that 3.2.x does not have: media-buy issues, reporting subscriptions, proposal webhooks, signal-delivery-method, canonical-installment, proposal holds, asset sizes, the merge assignment op, the vendor_metric goal, capabilities implementation, and timezone_cutovers. No rejection on 3.2.x is absent from #8866.

They cover only names the protocol defines elsewhere or forbids there. Following the #8866 review, step, gpc_honored, political, threshold_rate and per_ad_spend are not rejected, and list-application receipts reject auth_token alone. access_token on the delivery-ready webhook stays as a credential clamp.

Key-presence unions. Each branch rejects its sibling's keys by name:

  • account-ref and canonical-account-ref: account_id vs the natural key (brand, operator, operator_unit, currency, timezone, sandbox);
  • geo-region requirement and support countries: all_values vs values;
  • image bleed: uniform vs per-side;
  • postal-area: the deprecated fused-system form has no country;
  • sync_reporting_receipts results: receipt vs adjustment_receipt, and a failed result neither.

Descriptions. Every node or union with a named rejection says what it rejects and why. Two sentences are worded for 3.2.x:

  • the sync_creatives assignment one, because 3.2.x has no merge op;
  • the closed lookup_unavailable branch's statement of its clamp.

#8866's description cleanups are ported too, so opened schemas no longer claim to be closed.

sync_plans reserved names. The opened plan item rejects version, status, syncedAt, revisionHistory, committedBudget and committedByType. They are the governance agent's bookkeeping names, which the plan_hash profile strips from its preimage, so a buyer value under one of them would sit outside the hash. The list matches 3.2's closed "Excluded fields" list. This is ported from #8866 fa7aefacfe, with tests/sync-plans-reserved-names.test.cjs.

Principal results. The get_principal current branch and the sync_principal applied and validated branches open, as on #8866. The validated (dry-run) branch rejects destination_ref and configuration_version.

3.2.x-only deltas

Location On 3.2.x Why
media-buy/get-reporting-status-response.json /oneOf/1/oneOf/0 (unavailable lookup) stays closed Its caller-isolation text requires one identical lookup_unavailable shape for unknown and unauthorized identifiers. On 3.2.x the branch is closed with the envelope redeclared, because the envelope-composition backport was reverted in #8612. 3.3 enforces the same clamp differently: under #8547's envelope rule the branch is open there, with a closed adcp_error/errors[], a const message, and named rejections of ledger_snapshot_id, ledger_as_of and account_id.
media-buy/get-reporting-status-response.json /oneOf/1/oneOf/1 (operational failure) opens Not a privacy shape. The required failure_kind const keeps the two branches disjoint. Already open on main.
brand.json /definitions/identity_relying_party opens An inline object on 3.2.x. On main it is a $ref alias to core/identity-relying-party.json, which is class (a).
core/targeting-overlay-requirements.json description partial port Only the "request shape" → "request schema" wording is ported. The boolean-demographics deprecation (x-deprecated-in: 3.3.0) and the gender-targeting wording in #8866 are 3.3 content and stay out.
core/canonical-installment-ref.json, trust/v1/trust.json n/a Not present on 3.2.x. They are kept closed on 3.3.

Other changes

  • MCP model-context projection. stripModelContextAnnotations now drops boolean additionalProperties, true as well as false. This is the projector change from f5c56db on main. It also omits a named rejection beside declared properties, as it omits bounds, which comes from fix(schemas): open the 3.3 schemas that were meant to be open #8866. Model-context budgets are unchanged. PARITY_COMPILE_LIMIT is also unchanged on 3.2.x; it does not trip.
  • training-agent. The product-discovery tools/list schemas omit additionalProperties: true inside bundled definitions (9c1c52d). Its sync_principal part does not apply, because the 3.2 training agent does not implement sync_principal.
  • Tests mirror fix(schemas): open the 3.3 schemas that were meant to be open #8866's edits for the test files 3.2.x has, citing DR-0009 because DR-0036 is not on 3.2.x:
    • generic unknown-key probes, including those for the dropped rejections, now expect the key to validate;
    • account-ref, canonical-account-ref and image-bleed tests are wired into test:schemas. They load the source schemas, as 3.2.x tests do, because scripts/built-schemas.cjs is not on 3.2.x;
    • the MCP legacy-graph check walks the parsed schema and skips not and descriptions;
    • product-discovery-schema-parity compares openness rather than the literal keyword.

Verification

Head 600458f51d, base 8558eef55d:

Docs. Two separate docs commits correct the closure statements:

  • the refine[] scope branches (refinement.mdx, with the error the opened schema actually gives) and governance policy entries (content-standards/index.mdx) are described as open;
  • the sync_plans plan item (governance/campaign/specification.mdx) is open, so the governance agent's bookkeeping fields are simply undeclared there;
  • the AccountRef variants (protocol/calling-an-agent.mdx) are told apart by named rejections rather than additionalProperties: false.

The wording matches #8866's.

🤖 Generated with Claude Code

bokelley added a commit that referenced this pull request Nov 10, 2026
…claims

3.2.10 shipped without the open-schemas backport, so the changeset and
the migration guide now say the next 3.2.x patch (#8864) opens 3.2's
locations, all but one.

Docs that still called opened objects closed now match the schemas:
the refine scope branches (a stray id fails on the missing product_id),
policy entries, sync_plans plan items, and the account-ref variants.
Where the reason was the commercial terms, the docs say they are held
closed until 4.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bokelley
bokelley force-pushed the fix/open-closed-schemas-3-2-x branch from 7d52566 to d00f0ad Compare November 10, 2026 16:28
bokelley added a commit that referenced this pull request Nov 12, 2026
* fix(schemas): fold in #8772's capability-block and container openings

Brings over the schema, test and doc changes of #8772 by Konstantin
Mirin: the daypart window, the overlay requirement and support
containers, spot reporting and canonical reporting capabilities open;
boolean demographics becomes the deprecated 3.2 shorthand for
{ age: true }, so only gender support satisfies a gender requirement.

The DR-0036 register entries and the named exception from #8772 are
left out: the next commits open these schemas under the WG decision of
2026-11-09, which needs neither.

Co-authored-by: Konstantin Mirin <konstantin.mirin@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): open the 3.3 schemas that were meant to be open

The WG decided on 2026-11-09 that 3.x opens the schemas that were meant
to be open: closing a schema only breaks hard-coded validators, so
opening one is not a protocol break. additionalProperties goes from
false to true at 784 of the 859 closed locations in the source tree.
Nothing else in those schemas changes.

75 locations stay closed for a structural reason: oneOf branches told
apart only by key presence (a2ui bound-value, brand.json), the signed
commercial terms that terms_digest binds, metric qualifiers and
forecast dimensions (join keys), the canonical installment identity,
the JWS response envelope, the TMP match requests and the not-found
error (privacy boundaries), the reporting-destination setup action,
and patternProperties maps keyed by IDs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep the privacy clamps closed; drop closure claims from opened schemas

The per-agent PERMISSION_DENIED details and the failed and unconfigured
get_principal results stay closed: their descriptions make the closed
shape the clamp against an existence or commercial-state oracle.

Descriptions of schemas that are now open no longer say they are
closed or reject unknown members. The metric qualifiers stay closed, so
their descriptions now say new keys ship in a major release, not in a
minor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(lint): flag additions only to schemas that stay closed

Under the WG decision of 2026-11-09 and the rewritten DR-0036, schemas
are open by default and a schema stays closed only for a structural
reason. The additive-minor lint now matches:

- property-added-to-closed fires only where the schema is closed in both
  the base and the candidate. Opening a schema, and adding to one the
  candidate opens, passes.
- The closed-anywhere-in-the-major rule goes: closedInEarlierReleases,
  the "(closed in X)" findings and the released exemption.
- Corrections only tighten a bound or require a name the published text
  already set. The 24 whole-schema reopen entries go; an entry that lets
  in a property is an error.
- Openings print one notice line with the count.
- Removals, renames, retypes, enum removals, bound tightening, new
  required names and closing an open schema still fail.

The baseline drops the 34 entries this resolves and keeps 4, each with
its resolution: metric_id and the two sla-window fields sit on schemas
that stay closed (signed commercial terms), and evaluator is restored.

Also ports the DR-0036 cross-check removal from #8858 (from Konstantin
Mirin's #8777): the corrections list names its decision record, which
no longer lists entries.

Co-authored-by: Konstantin Mirin <konstantin.mirin@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(lint): cover the open-by-default additive-minor rule

Drops the tests of the earlier-release closure, the released exemption
and the reopen and property corrections, moves the correction checks
onto bound fixtures, and adds cases for additions to schemas closed on
both sides, opened, or open, for closing an open schema, and for a
correction that lets in a property.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep the reporting-status and billing-permission clamps closed

The 3.2.10 backport found two more privacy clamps:

- get_reporting_status's Unavailable lookup failure is closed in every
  3.2 release; #8547 opened it during the 3.3 betas. Its caller
  isolation text requires unknown and unauthorized identifiers to use
  one identical lookup_unavailable shape, so it closes again with the
  envelope fields redeclared as 3.2.8 does. The Operational failure
  branch stays open; its failure_kind const keeps the two apart.
- BILLING_NOT_PERMITTED_FOR_AGENT details stay closed, as
  PERMISSION_DENIED's per-agent details do: their description calls
  extra keys commercial-state oracles.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: say schemas are open by default; restate the closed ones' reasons

The 3.2 to 3.3 migration guide's "Closed schemas stay closed within a
major" section becomes "Schemas are open by default": what opened, the
structural reasons the rest stay closed, and what it means for
validators, generated types and 3.2 peers. The 3.3 beta page, What's
new, the release notes and the 4.0 compatibility guide follow.

Pending changesets that cited "a minor never changes a closed schema"
or a lettered DR-0036 correction now cite the structural reason
(commercial_terms is signed) or DR-0024. Adds the changeset for the
opening.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep trust.json and placement-presentation closed

Both are security-sensitive documents whose closure keeps out an
open-ended class of content that no list of names could cover:

- trust.json sits on the signature-verification fetch path, and signing
  keys are published only in the key directory, so its records,
  agents, grants and acknowledgements carry no key material (jwks_uri,
  key pins, signing profiles) and no undeclared authority.
- placement-presentation is a declarative, non-executable frame that
  consumers render, so it carries no markup or script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: count the 100 locations that stay closed

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep principal results, reporting destinations and hard budget bounds closed

- get_principal and sync_principal results keep their closed branches:
  no branch may become an oracle for another principal's existence or
  state, and a dry run issues no durable identifier.
- Reporting destinations are credential-free by contract, and closure
  rejects credentials under any name.
- proposal-budget-constraint is the strict peer of budget-range: a
  seller that ignored an unknown member of a hard constraint would
  violate a constraint it never read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: count the 116 locations that stay closed

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep the reporting-status lookup_unavailable branch open

Every response root and status branch accepts every envelope field
(#8547), so the Unavailable lookup branch can't close without
redeclaring the envelope, which the composition rule forbids. main's
shape already carries the caller-isolation clamp: the error objects
stay closed, the message is a const, and the ledger and account fields
are rejected by name. The branch goes back to that shape; only its
nested error objects stay closed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(security): count the capability blocks 3.3 opens as open positions

The worst-case capabilities document is unchanged at 99,100,981 bytes;
its open positions go from 108 to 190.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): name the fields closure used to reject in opened schemas

Where a closed schema also rejected a specific field the protocol
defines elsewhere, or one its text forbids there, the opened schema now
rejects it by name in a not/anyOf/required clause, as #8531 did for
canonical-product. Examples: trackers, landing_page_url and weight stay
off unassign, replace and merge; hold entries carry no expires_at; a
reporting revision carries no destination_ref; delivery-ready webhooks
carry no access_token; SDK metadata carries no self-asserted approval;
an attestation presentation carries no evaluator decision; requirement
branches reject seller maxima.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: expect opened schemas to accept unknown keys

Tests that asserted generic closure (an undeclared key is rejected, or
additionalProperties is false) now assert the opened behaviour. Tests
that reject a named field are unchanged and pass through the schema's
named rejection.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): keep key-presence anyOf unions apart by name

Opening the branches of an anyOf that was told apart only by which keys
are present lets one payload carry both forms. Each branch now rejects
the other's keys by name:

- canonical-account-ref: the account_id form rejects brand and
  operator, and the natural-key form rejects account_id;
- geo-region requirement and support: all_values and values exclude
  each other per country;
- the deprecated fused-system postal area rejects country;
- a sync_reporting_receipts result carries a receipt or an adjustment
  receipt, not both.

Also names step on frequency-cap impression constraints and mode on
list application receipts, matching the 3.2.10 backport.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: finish the open-schema test fallout

- mcp-schema-projection: PARITY_COMPILE_LIMIT 1,384,000 -> 1,385,000,
  measured (the named rejections add 395 bytes to the
  comply-test-controller closure); the list_products legacy-graph check
  strips the new format_ids and v1_format_ref prohibitions as it strips
  canonical-product's.
- Unknown-key cases that are now accepted: entries_total on list
  receipts, an unknown geo_countries support key, response_due_at and
  completion_due_at on issue receipts, the bucket_completness typo, and
  an unexpected publisher targeting key-value config key.
- New canonical-account-ref test: account_id and the natural key
  exclude each other, and an unknown key is accepted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(training-agent): keep tools/list within budget and ignore unknown declarations

- tools/list discovery schemas omit `additionalProperties: true` inside
  bundled definitions. It is JSON Schema's default and carries no
  information, and dropping it keeps the four-tool surface under its
  162 KiB budget once the named rejections land. The root keeps the
  keyword, which the parity test compares with the source.
- The parity test compares openness instead of the literal keyword.
- sync_principal keeps only the declaration axes the seller reads, so an
  unknown declarations member is ignored rather than stored and read
  back. An unknown section is still refused (UNSUPPORTED_FEATURE).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): address review on named rejections and key-presence guards

From Konstantin Mirin's review of #8866:

- Key-presence guards on two more unions: account-ref's account_id and
  natural-key forms exclude each other (as canonical-account-ref does),
  and image bleed's uniform and per-side forms exclude each other.
  canonical-account-ref's account_id form also rejects operator_unit,
  currency, timezone and sandbox, and a failed receipt result carries
  no receipt. A rescan of every oneOf and anyOf finds no other
  key-presence union.
- Named rejections now cover only names the protocol defines elsewhere
  or forbids there. Dropped: step, covered (two nodes), gpc_honored,
  political, threshold_rate, per_ad_spend, verified (two nodes) and
  mode on list receipts. access_token on the delivery-ready webhook
  stays as a credential clamp.
- Every node or union with a named rejection says in its description
  what it rejects and why, since generated types can't express not.
- The get_principal current branch and the sync_principal applied and
  validated branches open: they return the caller's own configuration
  and are dispatched by kind. The validated branch rejects
  destination_ref and configuration_version, because a dry run issues
  no durable identifier. recognized, unconfigured and failed stay closed.
- The reporting-status lookup_unavailable branch states its clamp.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: call the commercial terms a hold until 4.0; carry #8772's doc hunks

From Konstantin Mirin's review of #8866:

- The commercial terms and proposal-budget-constraint are held closed
  until 4.0, not closed for a structural reason. terms_digest covers
  every member at every depth, open ones included, so the docs no longer
  claim that closure stops a 3.2 buyer accepting a term it ignored.
- The boolean demographics deprecation reaches the 3.2 to 3.3 summary
  and Deprecations list, and the 4.0 guide's removal count and
  seller-emitted list, as #8772 had them.
- target_audiences sits beside audience_evidence_requirements because
  one names which audience and the other the evidence quality, not
  because the requirements object was closed.
- 3.2.10 opens all but one of 3.2's locations: it keeps the
  lookup_unavailable branch closed. The get_principal current and
  sync_principal applied and validated results open, so 747 locations
  open and 112 stay closed.
- The lint hint points to the corrections register again and says a
  correction sets a bound or a required name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: flip probes for dropped rejections; add account-ref and bleed guards

From Konstantin Mirin's review of #8866:

- Probes for names the protocol never defines (step, mode on receipts,
  covered, gpc_honored, political, threshold_rate, per_ad_spend,
  verified) now expect the opened schema to accept them.
- New tests: account-ref and image bleed key-presence guards, and the
  extended canonical-account-ref guard.
- The list_products legacy-graph check skips not subtrees and
  descriptions structurally, instead of matching serialized strings.
- The model-context projection omits named rejections beside declared
  properties, as it omits bounds: they are validation, and the
  descriptions carry them. A bare not branch of a union stays. The
  media-buy budget is unchanged; PARITY_COMPILE_LIMIT is 1,386,000,
  measured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(lint): prune the additive-minor baseline to base 3.2.9

The 3.2.9 forward-merge makes 3.2.9 the default base. The 4 recorded
entries are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: point the backport to the next 3.2.x patch; drop stale closure claims

3.2.10 shipped without the open-schemas backport, so the changeset and
the migration guide now say the next 3.2.x patch (#8864) opens 3.2's
locations, all but one.

Docs that still called opened objects closed now match the schemas:
the refine scope branches (a stray id fails on the missing product_id),
policy entries, sync_plans plan items, and the account-ref variants.
Where the reason was the commercial terms, the docs say they are held
closed until 4.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: regenerate compliance symbol links on get_products

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: describe the account-ref guard errors, not additionalProperties

Merged variants now fail on the named rejection (not) or a missing
required name, and a budget object fails on type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(schemas): reserve the plan_hash bookkeeping names on sync_plans plans

The opened sync_plans plan item accepted the governance agent's
bookkeeping names: version, status, syncedAt, revisionHistory,
committedBudget and committedByType. The plan_hash profile strips
exactly those names from its preimage, so a buyer value under one of
them would sit outside the hash and could collide with state the agent
manages. The plan item now rejects them by name, and its description
says they are reserved and a buyer MUST NOT send them. The list matches
the profile's closed "Excluded fields" list. No storyboard, fixture or
request example sends them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(3.3): say the commercial terms are held closed until 4.0

whats-new and the release notes no longer give the signed commercial_terms
as the example of a structural reason: the rest stay closed where closure
enforces something, and commercial_terms is held closed until 4.0.
experimental-status no longer calls the buy_products purchase input and
the list_products offer_filters closed; both are open in 3.3 and gain
target_audiences in 4.0, with the accepted product-purchase snapshot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(lint): describe the commercial terms as held closed until 4.0

The withdrawn-to-4-0 test comment, the additive-minor baseline $comment
and the lint header drop the structural-reason framing for the commercial
terms. All four baseline entries sit in commercial-terms schemas.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(refinement): match the troubleshooting heading to the error it shows

The heading quoted "must NOT have additional properties" while the body
shows the missing product_id error. The body no longer says every scope
branch requires its own identifier: the request scope requires ask.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Konstantin Mirin <konstantin.mirin@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
bokelley and others added 12 commits November 12, 2026 15:11
The WG decided on 2026-11-09 that 3.x opens the schemas that were meant
to be open, so a 3.2 validator does not reject a newer 3.x payload just
because a schema was closed. This is the 3.2.10 backport of the 3.3
opening. additionalProperties goes from false to true at 671 of the 775
closed locations in the 3.2 source tree.

104 locations stay closed, by the keep-closed list approved for 3.3;
every file/pointer the two lines share has the same class: oneOf
branches told apart only by key presence, the signed commercial terms
and the must-understand proposal budget constraint, metric qualifiers
and forecast dimensions (join keys), the JWS response envelope, privacy
boundaries (TMP match requests, the not-found error, permission-denied
and billing-not-permitted details, get_principal and sync_principal
results, the get_reporting_status unavailable lookup), the
credential-free reporting destinations and their setup action,
placement-presentation (no key material or markup), and
patternProperties maps keyed by IDs.

The get_reporting_status unavailable-lookup branch stays closed on 3.2.x
with the envelope redeclared; 3.3 opens it under #8547's envelope rule
and enforces the same clamp with named rejections.

The MCP model-context projection drops boolean additionalProperties,
true as well as false (ported from f5c56db on main), so the opening
does not inflate the prompt view. Tests that pinned closure now assert
the opened behavior or compare against the source schema.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hemas

Ports #8866's named rejections to 3.2.x for every node that exists
there: where closure was the only thing rejecting a specific field the
protocol defines elsewhere or forbids, the opened schema rejects it by
name in `not`, next to additionalProperties: true. 31 of #8866's 51
named rejections apply on 3.2.x; the rest target schemas or nodes that
3.2.x does not have.

Also ports #8866's description cleanups: opened schemas no longer say
they are closed, and the metric-qualifier descriptions say new keys
ship in a major release. The 3.3-only boolean-demographics deprecation
and gender-targeting wording are not ported.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ports #8866's test edits for the test files 3.2.x has: generic
unknown-key assertions now expect the key to validate, citing DR-0009
(DR-0036 is not on 3.2.x), and the training agent test shows an unknown
hard overlay requirement still matches no product.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ports #8866's 9bda16d and 32768d4 to 3.2.x. Opening exposed
anyOf unions whose branches were told apart only by which keys are
present; each branch now rejects its sibling's keys by name: geo-region
requirement and support countries (all_values vs values), the canonical
account ref (account_id vs brand + operator), the deprecated
fused-system postal area (no country), and sync_reporting_receipts
results (receipt vs adjustment_receipt). Also names `step` on frequency
cap impression constraints and `mode` on list-application receipts.

Tests: adds canonical-account-ref.test.cjs (loading source schemas, as
3.2.x tests do), strips the format-key prohibitions from the MCP
legacy-graph check, and flips the generic unknown-key vectors, citing
DR-0009. PARITY_COMPILE_LIMIT is unchanged on 3.2.x; it does not trip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…finitions on 3.2.x

Ports the tools/list and parity-test parts of 9c1c52d (#8866):
bundled definitions in the product-discovery tools/list schemas omit
`additionalProperties: true`, which is JSON Schema's default and carries
no information. The root keeps the keyword. The parity test compares
openness rather than the literal keyword.

The sync_principal part of 9c1c52d does not apply: the 3.2 training
agent does not implement sync_principal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ports cd8bc76 (Konstantin Mirin's review of #8866) for every node
3.2.x shares:

- Key-presence guards: account-ref's account_id and natural-key forms
  exclude each other, as canonical-account-ref's now do for all six
  natural-key fields; image bleed is uniform or per-side; a failed
  reporting-receipt result carries no receipt.
- Named rejections only for names the protocol defines elsewhere or
  forbids: step, gpc_honored, political, threshold_rate and
  per_ad_spend are dropped, and list-application receipts reject
  auth_token alone. access_token on the delivery-ready webhook stays as
  a credential clamp.
- Each node or union with a named rejection says in its description
  what it rejects and why. The sync_creatives sentence omits the merge
  op 3.2.x does not have, and the closed lookup_unavailable branch
  states its clamp in 3.2.x terms.
- The get_principal current branch and the sync_principal applied and
  validated branches open; the validated branch rejects destination_ref
  and configuration_version.

The changeset calls the commercial terms a hold until 4.0 rather than
a structural reason. 674 of 775 locations open; 101 stay closed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uards

Ports c01b095 (#8866) for the test files 3.2.x has: probes for the
dropped rejections expect acceptance (DR-0009); account-ref.test.cjs
and image-bleed.test.cjs are new (loading source schemas, as 3.2.x
tests do) and wired into test:schemas; canonical-account-ref covers
the extended guard. The MCP legacy-graph check walks the parsed schema
and skips `not` and descriptions, and the model-context projection
omits named rejections beside declared properties, as it omits bounds.
PARITY_COMPILE_LIMIT is unchanged on 3.2.x; it does not trip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The refine[] scope branches and governance policy entries are open on
3.2.x now. A pre-rename refine entry still fails validation, because its
generic `id` doesn't supply the `product_id` or `proposal_id` its scope
requires; the troubleshooting section shows the error the opened schema
gives. A policy-entry field outside the table has no defined meaning, so
receivers ignore it; partner metadata still belongs under `ext`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ents

The sync_plans plan item is open on 3.2.x, so the governance agent's
bookkeeping fields are simply not declared there, rather than excluded
by closure. The two AccountRef variants are told apart by named
rejections: the account_id variant rejects the natural-key fields and
the natural-key variant rejects account_id, so {account_id, brand}
still fails both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Aligns the refine troubleshooting, policy-entry, sync_plans and
AccountRef passages with #8866 (6c689cc), including the two
calling-an-agent error-table rows that named additionalProperties.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lans

Ports fa7aefa (#8866). The opened sync_plans plan item accepted the
governance agent's bookkeeping names: version, status, syncedAt,
revisionHistory, committedBudget and committedByType. The plan_hash
profile strips exactly those names from its preimage, so a buyer value
under one of them would sit outside the hash and could collide with
state the agent manages. The plan item now rejects them by name, and its
description says they are reserved and a buyer MUST NOT send them. The
list matches 3.2's closed "Excluded fields" list. No storyboard, fixture
or request example sends them. The test loads source schemas, as 3.2.x
tests do, and cites DR-0009.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hows

Ports 7d4dd1b (#8866): the heading names the error the opened refine
branches give, and the text says which identifier each scope requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bokelley
bokelley force-pushed the fix/open-closed-schemas-3-2-x branch from e1199d3 to 600458f Compare November 12, 2026 15:15
@bokelley
bokelley marked this pull request as ready for review November 12, 2026 15:15

@aao-secretariat aao-secretariat Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ladon verdict: Escalate to human review

Escalate — gated schema paths require human/CODEOWNERS review.

This PR is a 332-file 3.2.x backport mirroring #8866's open-closed-schema decision (ratified WG 2026-11-09), opening additionalProperties: false→true in 674 of 775 locations while keeping 101 closed. The reviewer verified the load-bearing cases hold (fail-closed privacy clamps, not-based oneOf disjointness, schema↔docs coherence, changeset present, no dist/** mutation) and surfaced no Critical/High/Medium findings.

However, the PR touches hundreds of files under static/schemas/source/**, which are under a hard, deterministic approval gate (gated_paths: true), and review_decision is unknown/none — not APPROVED. Per decision-table row 2, a gated-paths PR cannot be approved until a real human/CODEOWNERS approval satisfies the gate. Additionally, the repo's constitution treats this protocol-surface wire-shape change as a governance/ratification call (patch-eligibility and Breaking-class classification are human acts), reinforcing that a human must sign off.

No blocking code defects were found, so this is not request-changes — it is a clean diff awaiting the required human review on gated protocol-surface files.

Why human review

  • Gated paths touched (static/schemas/source/** — 332 protocol-surface schema files) and review_decision is not APPROVED; human/CODEOWNERS approval required before merge (decision-table row 2).
  • Protocol wire-shape change (open-closed-schema backport) is a governance/ratification call per the constitution's Breaking-class hard gate — ratification is a human act.
  • This PR touches a path under a hard, non-overridable approval gate (static/schemas/source/aao/agent-publishers.json (modified) matches static/schemas/source/**; static/schemas/source/account/sync-governance-request.json (modified) matches static/schemas/source/**; static/schemas/source/account/sync-governance-response.json (modified) matches static/schemas/source/**; static/schemas/source/brand.json (modified) matches static/schemas/source/**; static/schemas/source/collection/base-collection-source.json (modified) matches static/schemas/source/**; static/schemas/source/collection/collection-list-changed-webhook.json (modified) matches static/schemas/source/**; static/schemas/source/collection/collection-list-filters.json (modified) matches static/schemas/source/**; static/schemas/source/collection/collection-list.json (modified) matches static/schemas/source/**; static/schemas/source/collection/get-collection-list-request.json (modified) matches static/schemas/source/**; static/schemas/source/collection/get-collection-list-response.json (modified) matches static/schemas/source/**; static/schemas/source/compliance/comply-test-controller-request.json (modified) matches static/schemas/source/**; static/schemas/source/compliance/comply-test-controller-response.json (modified) matches static/schemas/source/**; static/schemas/source/content-standards/get-media-buy-artifacts-request.json (modified) matches static/schemas/source/**; static/schemas/source/core/account-change-recorded-webhook.json (modified) matches static/schemas/source/**; static/schemas/source/core/account-identity-change-preview.json (modified) matches static/schemas/source/**; static/schemas/source/core/account-identity-change.json (modified) matches static/schemas/source/**; static/schemas/source/core/account-ref.json (modified) matches static/schemas/source/**; static/schemas/source/core/account-status-changed-webhook.json (modified) matches static/schemas/source/**; static/schemas/source/core/account-timezone-capability.json (modified) matches static/schemas/source/**; static/schemas/source/core/account.json (modified) matches static/schemas/source/**; static/schemas/source/core/agent-encryption-key.json (modified) matches static/schemas/source/**; static/schemas/source/core/agent-notification-

…(truncated)…

@aao-secretariat aao-secretariat Bot added the ladon/needs-human-review Ladon has escalated this PR for human review. label Nov 12, 2026
@bokelley
bokelley merged commit a07826a into 3.2.x Nov 12, 2026
51 checks passed
@bokelley
bokelley deleted the fix/open-closed-schemas-3-2-x branch November 12, 2026 16:00
bokelley added a commit that referenced this pull request Nov 12, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 12, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 12, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 12, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 12, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 13, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
KonstantinMirin pushed a commit to KonstantinMirin/adcp that referenced this pull request Nov 13, 2026
Forward-merges the published 3.2.11 release (3.2.x = v3.2.11 =
9df1dd7, the adcontextprotocol#8942 Version Packages merge) and the 3.2.x commits since
v3.2.10: adcontextprotocol#8873, adcontextprotocol#8938, adcontextprotocol#8864, adcontextprotocol#8959 and adcontextprotocol#8961.

Release records:
- dist/compliance/3.2.11, dist/schemas/3.2.11 and the signed
  dist/protocol/3.2.11.tgz tuple are taken from v3.2.11 unchanged.
- dist/schemas/index.json and latest.json are regenerated
  (forward-merge-release-records.cjs schema-discovery).
- CHANGELOG.md is main's file plus the 3.2.11 block
  (forward-merge-release-records.cjs changelog).
- package.json, package-lock.json, static/schemas/source/index.json: main's.
- static/compliance/published-versions.json: main's. 3.2.x's only extra
  entry is 3.2.11, which is registered in a separate commit after
  qualification.

adcontextprotocol#8961's 3.1.33 records already equal main's (same tree hashes). adcontextprotocol#8959 and
the adcontextprotocol#8889 half of adcontextprotocol#8938 are cherry-picks of main commits and auto-merged
to main's bytes.

Content conflicts, all resolved to main's file. Each 3.2.x side is a 3.2
backport or 3.2-only adaptation of work main carries in its 3.3 form:
- 33 schema sources under static/schemas/source and 14 test files, from
  adcontextprotocol#8864 (the 3.2 backport of main's schema opening and adcontextprotocol#8866's named
  rejections). Main's copies are the 3.3 opening: no location 3.2.11
  opens is closed on main, and the tests cite DR-0036.
- tests/policy-backed-rejections-storyboard.test.cjs, from the adcontextprotocol#8850 half
  of adcontextprotocol#8938: main tests its capability-gated storyboard (adcontextprotocol#8857).
- docs/media-buy/media-buys/lifecycle.mdx, from adcontextprotocol#8873: the 3.2
  pending_creatives prose. Main's prose matches main's 3.3 enum.
- server/tests/unit/storyboards.test.ts, from adcontextprotocol#8961: 3.2.x's floors and
  pins. Main keeps its own.

Auto-merge reverted: the non-conflicting adcontextprotocol#8850 hunk in
creative/policy_backed_rejections.yaml. It adds the 3.2-only
enforced_policies skip_if gate on top of main's
creative.supports_registry_policy_enforcement capability gate, and its
own narrative says the 3.3 line uses the capability instead.

Outside dist/ and CHANGELOG.md the merged tree equals main's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 14, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 15, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 15, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 15, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 16, 2026
…lease docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 16, 2026
…se docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 16, 2026
3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bokelley added a commit that referenced this pull request Nov 16, 2026
* docs(reference): bring the 3.3 release docs to 3.3.0-rc.0

Bring the release notes, What's new, the 3.2 to 3.3 migration guide, the
prerelease program page, Versions, and the 3.3 rows of Choose your SDK to
the first release candidate. The prerelease page keeps its 3-3-beta URL
and is retitled, as the 3.2 page was at its RC. rc.0 joins the checkpoint
and wire-pin tables with the 3.3-rc documentation selector.

Cover the 2026-11-09 decision to open the schemas that were closed by
accident, and the #8501 triage that followed it: which beta fields stay in
3.3, which leave because they sit on deprecated tasks or would change a
signed term, and which move. The migration guide lists every field; the
other pages summarize it. Record boolean overlay demographics as
deprecated.

Leave the lines that #8866 rewrites alone, and fix the "closed schemas
stay closed" wording it does not touch: the Send-only-to-3.3-peers intro
and proposal-flow correction in the 3.2 to 3.3 guide, the 3.1 to 3.2
guide, optimization reporting, and the daily-budget spec.

Describe deprecated 3.3 features as expected to be removed in 4.0, with
3.3 supported for a window after 4.0 GA, instead of the six-month notice
promise. Record @adcp/sdk 17.0.0-beta.22 and Python adcp 10.0.0b15 on
beta.5, Python adcp 9.6.2 with the A2A input fix on the 3.2 line, no SDK
on rc.0 yet, and no Go or Java support for 3.3.

Content that depends on unmerged PRs or on the rc.0 cut carries a
{/* depends on ... */} marker (HTML comment in the spec markdown) so it
can be re-checked before the cut.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): state the 12-month 3.3 support window after 4.0 GA

Replace "length to be confirmed" in the 3.2 to 3.3 Deprecations intro
with the decided window: 3.3 stays supported for at least 12 months after
4.0 GA. Point the marker at #8858, which carries the policy change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): describe the commercial terms as held closed until 4.0

Konstantin's review of #8866 rejects signed commercial terms as a
structural reason to keep a schema closed: terms_digest covers open
members at every depth, including ext. Describe the nodes inside
commercial_terms, and proposal-budget-constraint, as held closed until
4.0 in the triage tables and summaries, the release notes, What's new,
Versions, and the daily-budget spec, and drop the claim that the digest
stops a 3.2 buyer from accepting a term it ignored. The triage reason is
renamed from signed meaning to held closed until 4.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): prerelease pins, unpinned discovery, and anonymous capabilities

A 3.3 beta reader pinned get_adcp_capabilities to 3.3-beta.5 against a
3.0-only seller, got VERSION_UNSUPPORTED, and never retried. State how
each side avoids that (approved by Brian for the 3.3 RC docs):

- Versioning, pre-release pins: a buyer MUST send a prerelease
  adcp_version only to a peer whose supported_versions lists that exact
  value, SHOULD discover unpinned, and SHOULD retry unpinned or at a
  listed version on VERSION_UNSUPPORTED, matching the existing retry
  SHOULD and the error code's recovery hint. Mirrored on the 3.3
  prerelease page.
- Authentication: a seller SHOULD serve get_adcp_capabilities without
  credentials; a SHOULD in 3.3 and a MUST in 4.0.
- MCP guide: a gateway that allow-lists JSON-RPC methods SHOULD let
  server/discover, initialize, and tools/list through without
  credentials.
- Release docs: a migration-guide section with buyer and seller
  checklist rows, a What's new and release-notes bullet, and the 4.0
  item in v4-compatibility's not-yet-checked list.

Docs only; no schema changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): follow #8866 and the other rc.0 merges in the 3.3 release docs

After rebasing onto main with #8866 merged:

- Take #8866's wording for the boolean form of demographics in the
  migration guide's Deprecations section, and align the release notes and
  What's new with it (#8778 tracks the 4.0 removal).
- 3.2.10 shipped without the schema opening, so say "the next 3.2.x patch
  (#8864)" and "3.2.10 and earlier", including in #8866's
  Schemas-are-open-by-default bullet.
- Drop the dependency markers #8866 satisfied, and retarget the rest.
- Cover the other changes merged for rc.0: origin-only authorized_agents
  URLs (#8939), declared-option creative conformance (#8941), TMP cache
  isolation (#7446), creative.supports_registry_policy_enforcement
  (#8857), 3gp/mpeg/m4v containers (#8668), carousel card_image_sizes
  (#8937), and the loosened URL patterns (#8792).
- Refresh the in-review table against the 3.3.0 milestone on 2026-11-12,
  and remove the stray duplicate table header it carried.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(sdk): keep the SDK matrix on the installed @adcp/sdk prerelease

tests/sdk-runtime-compat.test.cjs requires Choose your SDK to name the
@adcp/sdk prerelease this repository installs (17.0.0-beta.21), and no
other 17.0.0 prerelease. Revert the TypeScript row and install command to
beta.21 and drop the npm beta dist-tag label, which now points at beta.22.
The release pages keep recording that beta.22 also bundles beta.5.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8858 and #8864 markers in the 3.3 release docs

- #8858 merged: drop its markers on the 3.3 support window and the
  daily-budget spec.
- #8864 merged into 3.2.x, so the schema opening ships in 3.2.11: say
  "3.2.11 (#8864)" instead of "the next 3.2.x patch", with one marker per
  page on the 3.2.11 release itself (Version Packages #8942).
- target_audiences on list_products offer_filters is decided: it stays as
  it is in 3.3, and any change is 4.x, so media_buy.audience_evidence_targets
  has no 3.3 surface once the get_products and create_media_buy copies leave.
- The available_installment_statuses move is a 3.3 RC item; its markers
  now point at c4777ebd's PR, and the release-notes installment_lifecycle
  row carries a marker to move to the canonical location when it lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): point the available_installment_statuses markers at #8957

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8762 and #8957 markers in the 3.3 release docs

#8762 (sla-window back to its 3.2 shape, business time on the creative
review SLA) and #8957 (available_installment_statuses on the canonical
reporting capabilities) merged; #8762's own release-doc lines arrive with
the rebase. Drop both from the dependency markers, name the canonical
product's reporting_capabilities in the release-notes
media_buy.installment_lifecycle row, and refresh the #8501 row of the
in-review table.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8758 markers in the 3.3 release docs

#8758 merged: the get_products and sync_creatives assignments[]
withdrawals and the execution_readiness move to list_products are in
main. Drop it from the dependency markers, remove the #7659 note's
marker, move it to merged in the in-review table, and say that the
deprecated assignments[] row rejects trackers and landing_page_url by
name, so a stale sender is rejected there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8767 markers and describe the withdrawn surfaces

#8758 and #8767 merged and handed their release-doc text to #8883. Drop
#8767 from the dependency markers, and bring the lines that still
described withdrawn surfaces as current in line with main:

- media_buy.price_adjustments and media_buy.audience_evidence_targets are
  withdrawn at rc.0 and no longer registered (experimental table, feature
  index, What's new, migration guide).
- execution_readiness is on list_products; lineage is on buy_products and
  accept_proposal; collection cards leave get_products; the creative start
  gate is set through control_media_buy; counting_mechanisms leaves
  measurement_terms; assignment trackers and landing pages stay only on
  sync_creatives assign operations.
- Point the price-adjustment and target-audience links at the withdrawn
  sections; refresh the #8501 row of the in-review table.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): add the rc.0 installment experiments, with dependency markers

Two experimental, capability-gated rc.0 items are in progress: installment
selection through refine_proposals (media_buy.installment_refinement,
(media_buy.installment_creative_assignment, #8968). Add them to the
feature index, the experimental surfaces table, What's new, and the
migration guide, each behind a marker until its PR merges. Note on every
"installment selection withdrawn to 4.0" passage that 3.3 now covers the
request side, while the signed purchases[].installments[] stays a 4.0
item.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): cover #8884's signed-terms acceptance rule in the rc.0 docs

#8884 states that accepting signed commercial terms binds every member
terms_digest covers, with UNRECOGNIZED_TERMS and the unrecognized_terms
decline reason. Add it to the rc.0 checkpoint and feature index, the
behavior changes, What's new, and the migration guide (a required-behavior
section, checklist row 52, and its storyboard).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): describe #8972, per-installment creative assignment, in the rc.0 docs

#8968's PR is #8972: installment_refs on sync_creatives assign and replace
operations, read back on get_media_buys and list_creatives, rejected by
name on unassign and merge, VALIDATION_ERROR for a ref outside the bought
installments and CREATIVE_DEADLINE_EXCEEDED past change_cutoff. Correct
the RFC-based placeholder and point its markers at #8972.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): describe #8974, installment refinement, in the rc.0 docs

refine_proposals, unsatisfied_installment_changes with a reason, the
installment_changes value in proposal_refinement.supported_dimensions, and
a seller answer that buys a product whose installments are the chosen set.
Correct the RFC-based placeholder, link the new anchors, and point its
markers at #8974. Drop the sentence in the 4.0 page's What stays in 3.3,
which #8974 rewrites itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): cover #8793 and #8458 in the rc.0 docs

#8793: Reliable Reporting managed delivery holds no buyer secret, row push
is reporting_webhook, and the experimental https_put file_transfer
transport. #8458: media_buy.supported_delivery_types. Add both to the rc.0
checkpoint and feature index, the behavior changes and the
reporting_delivery experimental row, What's new, and the migration guide
(an experimental notice and checklist rows 53 and 54), and mark #8149 as
shipped in the in-review table. #8458's own optional-declaration lines
are kept.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the 3.2.11 markers

3.2.11 published on 2026-11-13 with the 3.2 schema opening (#8864), so
the release pages' 3.2.11 statements no longer wait on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8974 markers

#8974 merged as a7af517. Drop its markers, and narrow the shared
installment markers to #8972. The migration guide no longer says
core/installment-change-set.json and the installment_changes dimension
are gone: they leave after beta.1 and return in rc.0 under
media_buy.installment_refinement.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): describe #8983, report definitions at contract_version 1.2, in the rc.0 docs

#8983 (#8971) adds Reliable Reporting report-definition contract_version
1.2: a definition whose dimensions include media_buy_id must include
package_id, account-level definitions are exempt, and callers pinned below
3.3 get 1.0 or 1.1 offerings. Add it to the release notes (checkpoint
row, feature index, behavior change, experimental table), What's new, and
the migration guide (checklist row 55 and a section), with markers until
it merges. The checkpoint row also gains #8974 and #8972, which it was
missing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8972 markers

#8972 merged as e903ee6. Drop its markers and narrow the shared ones
to #8983. The migration guide adds #8972's capability rule: buyers send
installment_refs only to a seller that lists the feature id, and a seller
without it rejects the field with UNSUPPORTED_FEATURE.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8983 markers

#8983 merged as 39334ab. Drop its seven markers, and state the
serving rule as a MUST everywhere it appears: a seller serves callers
pinned below 3.3 only 1.0 or 1.1 report-definition offerings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): add 3.3.0-beta.6 ahead of rc.0

beta.6 is cut on main today for SDK testing over the weekend, and rc.0
stays on Monday. Add beta.6 to the checkpoint, SDK-posture and
version-string tables and to Versions, say rc.0 follows seven betas,
and note that everything in "New in rc.0" first shipped in beta.6 except
the prerelease-pin and anonymous-discovery guidance. beta.6's date
carries a marker until it publishes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): describe #8966, display labels for geo targeting codes, in the beta.6 and rc.0 docs

#8966 merged as aa94f36 and ships in beta.6. Add it to the beta.6
checkpoint row and the beta.6 and rc.0 feature index, to What's new
(smaller additions), and to the migration guide: checklist row 56, a
send-only-to-3.3-peers row for geo_value_labels, and a section under
Adopt by capability. Labels never resolve or apply targeting, sellers
never reject a request because they are present, and equality and
readback compare codes only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the beta.6 date markers

3.3.0-beta.6 published on 2026-11-13 (tag v3.3.0-beta.6 at bf4aa6d,
from Version Packages #8801). The pages already give that date, so drop
the four markers that held it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): describe #8995, social distribution identifier types, in the rc.0 docs

#8995 (#8992) adds eight distribution-identifier-type values for
Instagram, Facebook, Snapchat and X: a canonical ID and a handle alias
for each, with handles compared as @ plus the lowercased name. It lands
after beta.6, so add it to the rc.0 checkpoint rows, the feature index,
What's new, and the migration guide's send-only enum values, with
markers until it merges.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the #8995 markers and fold #8997 into the rc.0 docs

#8995 merged as 15b0c46, identical to the version these pages
describe, so its seven markers go.

#8997 (declared sync_creatives assignment operations) merged after
beta.6 with its own release-doc lines. The rebase kept this branch's
side of the overlapping hunks, so restore #8997's text: its migration
checklist row (now row 57, after this PR's rows 45 to 56), the
release-notes Creative bullet, and the What's new adopter rows. Its
migration and What's new sections and its behavior-change bullet came
through unchanged. As post-beta.6 content, it joins the rc.0 rows and
the "new in rc.0" notes.

#8986 (training agent refuses installment_refs) is server-only with no
changeset, so the rc.0 rows don't list it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): add #8970 and the other post-beta.6 merges to the rc.0 docs

#8970 (merged as 145ba50) asks get_media_buy_delivery sellers to
return at least one by_package row, one per package, and to omit a buy
they can't report rather than return an empty by_package. by_package: []
stays valid in 3.x, and minItems: 1 is proposed for 4.0 in #8973. Add a
behavior-change bullet, a What's new sentence, migration checklist row
58, and #8973 under v4-compatibility "Changes not checked yet".

#8996, #9001 and #8934 also merged after beta.6. #8996 and #9001 wrote
their own release-doc text, which came through the rebase unchanged.
Add all four to the rc.0 rows and the "new in rc.0" notes, and split
the release-notes feature index into a beta.6 bullet and an rc.0
bullet. Refresh the in-review table to 2026-11-14: #8149, #8107 and
#8856 (merged as #8934) closed, #8943 has #9011, and #9014 and #8998
(#9013) are new.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): write #8854 up as in review, not in rc.0

#8854 (withdraw metric_id, restore evaluator as a deprecated x-entity
value; #8501 entries 6 and 26) has not merged by Sunday 2026-11-15, with
changes requested. Per the Sunday rule, describe it as in review and not
in rc.0, and drop its eight markers. rc.0's schemas still carry metric_id
on the canonical and legacy performance standards and on
required_performance_standards, and still lack evaluator. The triage
decision stands, so metric_id stays listed as leaving 3.3, with a note
that the withdrawal is in review, and evaluator leaves the "stays in
3.3" lists. signing_profile is no longer part of #8854 and stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): take #9018's beta.6 SDKs and test-agent preview, and add #9011 and #9017

#9018 (6c34d90) bumped @adcp/sdk to 17.0.0-beta.26 and moved the
public test agent's preview to 3.3-beta.6. The rebase kept this
branch's side of the overlapping lines, so apply its facts here:
17.0.0-beta.21 to beta.23 and Python adcp 10.0.0b13 to 10.0.0b16
support beta.5, 17.0.0-beta.24 and later and 10.0.0b17 and later
support beta.6, Choose your SDK names beta.26 and 10.0.0b17, the test
agent serves 3.3-beta.6, and SDK-backed testing stays on beta.6 until
an SDK bundles rc.0.

#9011 and #9017 merged after beta.6 with their migration-guide text.
When several authorized_agents entries match one agent, its scope is
the union, and a signing_keys pin holds only if every matching entry
pins. Add them to the rc.0 rows, the rc.0 feature index and What's new.
The in-review table moves to 2026-11-15: #8943 and #9016 closed, and
#9013 is out of draft.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): fold #8989, #9007 and the last post-beta.6 changesets into the rc.0 docs

#8989 renames three experimental values to their counterparts'
spelling, with no alias: input_required to input-required
(execution_readiness), click_through to clickthrough (live_updates),
underdelivery to under_delivery (delivery_projection). Add a migration
section with the old and new spellings, checklist row 59, a release-
notes behavior change, a What's new bullet, and a "Renamed in rc.0" row
on the prerelease page, and fix the two input_required spellings that
the rebase kept from this branch.

#9007 lets campaign governance accept a sync_plans plan that omits
human_review_required, and states two sync_plans rules: checklist row
60, a release-notes bullet, and a What's new sentence.

Every changeset pending for rc.0 is now in the rc.0 rows and notes,
including the compliance gates #9013 and #9005 and #9018's beta.6
test-agent preview. Choose your SDK takes main's @adcp/sdk
17.0.0-beta.28. The in-review table moves to 2026-11-16: #8998 closed
(#9013), and #8987 is new.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(reference): resolve the rc.0-cut markers

rc.0 is cut today, 2026-11-16, and the pages already give that date, so
drop the five date markers. Write the three post-cut markers forward:
SDK prereleases that adopt 3.3.0-rc.0 follow within days of the cut,
Choose your SDK gains their rows when they publish, and the test-agent
preview moves to rc.0 once an @adcp/sdk prerelease negotiates it. A
follow-up PR on main adds the real versions after rc.0 publishes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ladon/needs-human-review Ladon has escalated this PR for human review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant