Skip to content

schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) - #8854

Merged
bokelley merged 6 commits into
adcontextprotocol:mainfrom
KonstantinMirin:schemas/8501-entries-2-3-6-26
Nov 18, 2026
Merged

bokelley merged 6 commits into
adcontextprotocol:mainfrom
KonstantinMirin:schemas/8501-entries-2-3-6-26

Conversation

@KonstantinMirin

@KonstantinMirin KonstantinMirin commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

This PR does entries 6 and 26 of the disposition table on #8501. A 3.3 minor release shouldn't change what a signed term means, or remove an enum value 3.2 published (DR-0036). metric_id isn't in 3.2.8 or 3.2.9; it shipped only in 3.3 betas, so no stable release breaks.

Entries 2 and 3 (signing_profile on the notification configs) are no longer in this PR. The re-triage marked them moot once #8866 opened both schemas, and there was no signed-meaning or security reason to withdraw them. signing_profile stays on accounts[].notification_configs[] and the agent-level notification config, as on main. During 3.x it's how a buyer moves those registrations to web-bot-auth; without it, the seller signs with the deprecated adcp/webhook-signing/v1.

Part of #8501.

Entry Field What happens
6 metric_id on core/canonical-performance-standard.json, plus the two deprecated-task rows: core/performance-standard.json and required_performance_standards in core/product-offer-filters.json Withdrawn and added to the 4.0 list. It selects which vendor value decides a signed performance standard, so a 3.2 buyer would read the same standard differently. The canonical standard stays closed in #8866 with the rest of the commercial terms.
26 evaluator in core/x-entity-types.json Restored as a deprecated value, with its definition. The 3.2.8 versioning page says "Existing values are never removed or renamed." The evaluator_id removal (#8045) stands.

Changes

Entry 6. metric_id and its viewability/completion_rate guard leave all three schemas. canonical-performance-standard.json, performance-standard.json and the performance-standard-metric enum are byte-for-byte their 3.2.8 versions again; in product-offer-filters.json only the one line goes, and required_vendor_metrics[].metric_id, which 3.2 published, stays. The docs that #8436 added (pricing models, accountability, measurement taxonomy, the create_media_buy and get_products tables, the attention example in optimization reporting) go back to their 3.2 meaning. The field shipped in 3.3.0-beta.1 through 3.3.0-beta.5 (#8436).

The 4.0 compatibility registry gets performance_standard_metric_id_required_in_4_0 (issue #8394, observed_by: none), and the 4.0 page gets a matching section that keeps the design and points at commit 43447c15b, which has the schemas, the test and the judging rules.

Entry 26. evaluator is back in the enum and in x-entity-definitions, listed in x-deprecated-enum-values with a note that no 3.3 field carries it. No schema has x-entity: evaluator, and evaluator-spec.json still has no evaluator_id. The migration guide's evaluator section no longer says the value was removed.

Baseline. scripts/lint-additive-minor-baseline.json drops its last two rows, the metric_id and evaluator ones, so entries is empty. The $comment no longer says there is one current entry. Neither row needs a corrections-register entry: after this PR the schemas don't differ from 3.2.8 at these locations.

Docs. The migration guide, What's new, the release notes and the 3.3 beta page list metric_id under "Withdrawn from 3.3, planned for 4.0", and the beta page has a one-row "Withdrawn after beta.5" table. The release notes and the beta page say evaluator is back as a deprecated value.

Tests. tests/performance-standard-metric-id.test.cjs is replaced in test:schemas by tests/closed-schema-additions-withdrawn.test.cjs. It checks that metric_id is gone from the three schemas, that the closed canonical standard rejects it, that the registry has the 4.0 entry, and that evaluator is back and deprecated. 8 of its 10 cases fail on main; the other two check what must stay (required_vendor_metrics[].metric_id, and no schema carrying x-entity: evaluator). tests/x-added-in-3-3-sweep.test.cjs drops the three metric_id sites.

The training agent doesn't read either field, so it doesn't change.

Expected conflicts

Each is a short manual merge, and I'll rebase on whichever lands first.

Testing

Rebased on main at a2a7d20ff.

  • npm run build:schemas: pass.
  • npm run test:schemas: pass, including the new test.
  • node --test tests/lint-additive-minor.test.cjs and npm run test:additive-minor: pass. The lint reports 0 recorded changes and 0 new against 3.2.10.
  • node scripts/lint-v4-compatibility-registry.cjs and npm run test:v4-compatibility-registry: pass.
  • npm run test:wba-profile-vectors, tests/x-added-in-3-3-sweep, tests/schema-deprecation-metadata, tests/lint-storyboard-context-entity, tests/mcp-schema-projection, tests/mcp-schema-analysis: pass.
  • npm run build:compliance -- --check, test:docs-nav, test:release-docs-nav, check:owned-links, lint:schema-links, and node scripts/check-changeset-protocol-scope.cjs origin/main: pass.
  • I didn't run the storyboard matrix locally; CI's run is the one to read.

Merge timing

The #8501 consent window closes today, Fri 2026-11-13, so this can merge ahead of the 3.3 RC on Mon 2026-11-16.

@mintlify

mintlify Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit 3bf9353.

Approve preview

@bokelley

Copy link
Copy Markdown
Contributor

@KonstantinMirin, a check against the Nov 9 decision to open the 3.x schemas that were closed by accident (re-triage posted on #8501):

  • Entries 6 (metric_id) and 26 (evaluator restored as deprecated): these match the re-triage. metric_id stays withdrawn because it changes what a signed term means, and evaluator is restored.
  • Entries 2 and 3 (signing_profile on notification configs): the re-triage marks these moot. The withdrawal was there only because the parent schema was closed, and fix(schemas): open the 3.3 schemas that were meant to be open #8866 opens it. So signing_profile would stay in 3.3.

Was there a reason beyond closure for withdrawing signing_profile, such as a signed-meaning or security concern? If not, could this PR drop entries 2 and 3 and keep 6 and 26? The RC release docs (#8883) currently describe signing_profile as staying.

@KonstantinMirin

Copy link
Copy Markdown
Collaborator Author

Hi Brian, no, there was no signed-meaning or security concern. I'll drop entries 2 and 3 and keep 6 and 26.

The description's other point, that a per-registration profile matters only until 4.0 removes the RFC 9421 profile, is a reason to keep the field, not to withdraw it. During 3.x, signing_profile is how a buyer moves these registrations to web-bot-auth. Without it, the seller signs with the deprecated adcp/webhook-signing/v1.

I'll rebase on main now that #8866 has landed.

Entries 6 and 26 of the adcontextprotocol#8501 disposition table. Entries 2 and 3
(signing_profile on the notification configs) are moot now that adcontextprotocol#8866
opened those schemas, so signing_profile stays.

- performance standards: withdraw metric_id and restore the 3.2.8
  schemas. A 4.0 registry entry, performance_standard_metric_id_required_in_4_0,
  keeps the design for the major.
- x-entity-types: restore evaluator as a deprecated value, with its
  3.2.8 definition.
- lint-additive-minor-baseline: drop the metric_id and evaluator rows,
  the last two, so the baseline is empty.
@KonstantinMirin
KonstantinMirin force-pushed the schemas/8501-entries-2-3-6-26 branch from 70af985 to 7649573 Compare November 13, 2026 17:40
@KonstantinMirin KonstantinMirin changed the title schemas: withdraw signing_profile and metric_id, restore evaluator as deprecated (#8501 entries 2, 3, 6, 26) schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) Nov 13, 2026
@KonstantinMirin

Copy link
Copy Markdown
Collaborator Author

Rebased on main after #8866, with entries 2 and 3 dropped. The PR now does entries 6 and 26 only:

  • signing_profile stays on accounts[].notification_configs[] and the agent-level notification config, as on main. The schemas, the sweep test and the docs that mentioned withdrawing it are back to main.
  • metric_id leaves the three performance-standard schemas and goes on the 4.0 list, and evaluator is restored as deprecated, as before.
  • The additive-minor baseline drops its last two rows (metric_id, evaluator), so it's empty now. The lint reports 0 recorded and 0 new against 3.2.10.

I updated the description to match. Its release-page text overlaps #8883's rows that depend on this PR, and whichever lands second keeps both.

Analyzed and generated with the help of Claude, fully reviewed by me.

@aao-secretariat

Copy link
Copy Markdown
Contributor

Ladon cannot review this PR until merge conflicts are resolved.

@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: Request changes

Request changes — 1 blocking finding.

Blocking findings

  • docs/measurement/taxonomy.mdx:26 — Schema↔docs drift: after this PR the performance-standard shapes carry only vendor (metric_id removed), but taxonomy.mdx:26 still enumerates "performance standard" among the surfaces through which the (vendor, metric_id) key flows. The author cleaned the detailed bullets and all judging docs but missed this summary line, leaving docs asserting a wire shape the schema no longer encodes.

This is the mandatory schema↔docs coherence check: docs claiming a key shape the schema does not encode is high spec drift. The withdrawal itself is clean and symmetric (three shapes updated, guard removed, evaluator restored as deprecated, new test asserts exact key shape, minor changeset with DR-0036 rationale present), but the stray taxonomy summary line must be corrected before merge.

Note: gated_paths is true (static/schemas/source/**) with review_decision REVIEW_REQUIRED, so human/CODEOWNERS approval is also required independent of this finding.

Blocking findings

  • docs/measurement/taxonomy.mdx:26 — taxonomy.mdx still lists "performance standard" as a surface carrying the (vendor, metric_id) key, contradicting the schema which now carries only vendor (high spec drift)

…_id) surfaces

Performance standards no longer carry metric_id in 3.x, so the taxonomy
summary no longer lists them among the surfaces the key flows through.
bokelley added a commit that referenced this pull request Nov 15, 2026
#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>
@aao-secretariat
aao-secretariat Bot dismissed their stale review November 15, 2026 12:12

Superseded by a later Ladon review that rechecked and resolved its blocking findings.

@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 paths touched without required review approval.

This PR modifies protocol source of truth under static/schemas/source/** (canonical-performance-standard.json, performance-standard.json, product-offer-filters.json, x-entity-types.json, performance-standard-metric.json), which falls under a hard, deterministic approval gate. review_decision is REVIEW_REQUIRED, not APPROVED, so the gate is not satisfied (decision table row 2).

The prior blocking finding was resolved: docs/measurement/taxonomy.mdx:26 no longer lists "performance standard" among surfaces carrying the (vendor, metric_id) key, matching the schema that now carries only vendor. The metric_id withdrawal is clean and symmetric (three shapes + guard removed, evaluator restored as deprecated, minor changeset with DR-0036 rationale, new closed-schema-additions-withdrawn test, coherent migration/release-notes/whats-new). No new findings; no schema↔docs drift remains.

Despite the clean diff, the gated-paths change to the published wire surface requires explicit human/CODEOWNERS review before merge.

Escalation reasons

  • Modifies gated schema source files under static/schemas/source/** (performance-standard, canonical-performance-standard, product-offer-filters, x-entity-types, performance-standard-metric) while review_decision is REVIEW_REQUIRED — human/CODEOWNERS approval required.

Why human review

  • Gated paths under static/schemas/source/** modified while review_decision is REVIEW_REQUIRED (not APPROVED) — human/CODEOWNERS approval required before merge (decision rule row 2).
  • This PR touches a path under a hard, non-overridable approval gate (static/schemas/source/core/canonical-performance-standard.json (modified) matches static/schemas/source/**; static/schemas/source/core/performance-standard.json (modified) matches static/schemas/source/**; static/schemas/source/core/product-offer-filters.json (modified) matches static/schemas/source/**; static/schemas/source/core/x-entity-types.json (modified) matches static/schemas/source/**; static/schemas/source/enums/performance-standard-metric.json (modified) matches static/schemas/source/**) and the current GitHub review decision is 'REVIEW_REQUIRED', not APPROVED. This is a hard gate enforced in code — Ladon cannot auto-approve until a human/CODEOWNERS approval is recorded, regardless of how clean the diff is.

@aao-secretariat aao-secretariat Bot added the ladon/needs-human-review Ladon has escalated this PR for human review. label Nov 15, 2026
@aao-secretariat
aao-secretariat Bot requested a review from bokelley November 15, 2026 12:12
bokelley added a commit that referenced this pull request Nov 16, 2026
#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>
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>
…2-3-6-26

Conflicts (3 files):
- package.json (mechanical): test:schemas takes main's list, which adds
  reserved-word-enum-replacements, sync-plans-human-review and
  sync-plans-validation-annotations, with this branch's swap of the
  deleted performance-standard-metric-id test for
  closed-schema-additions-withdrawn. No duplicates. package-lock.json
  did not conflict.
- docs/reference/release-notes.mdx (semantic): main's installment
  selection bullet, which now names the rc.0 installment_refinement
  return (adcontextprotocol#8974), followed by this branch's metric_id bullet and the
  evaluator restoration line.
- docs/reference/whats-new-in-3-3.mdx (semantic): the smaller-additions
  line takes main's "withdrawn at rc.0" note on adcontextprotocol#8468 and drops the
  metric_id clause this branch withdraws; the withdrawn table takes
  main's installment row followed by this branch's metric_id row.

Auto-merged files both sides touched (optimization-reporting.mdx,
3-3-beta.mdx, 3-2-to-3-3.mdx, v4-compatibility.mdx,
v4-compatibility.yaml) were reviewed; this branch's additions apply
cleanly to main's text.
rc.0 is cut and still carries `metric_id`, so the field was published in
beta.1 through rc.0 and leaves after rc.0, not after beta.5. The
release-note, migration and prerelease pages that said this PR was in
review now say the withdrawal lands after rc.0.

@bokelley bokelley 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.

Matches the #8501 disposition and DR-0036: metric_id (beta-only) goes to the 4.0 list, and evaluator is restored as deprecated. Merges cleanly with the post-rc.0 docs, which already describe the withdrawal as after rc.0.

@bokelley
bokelley merged commit 3a3bf1e into adcontextprotocol:main Nov 18, 2026
62 checks passed
bokelley added a commit to aymeric45/adcp that referenced this pull request Nov 18, 2026
Pick up adcontextprotocol#8854 and adcontextprotocol#9070; resolve the test:schemas list conflict.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bokelley bokelley mentioned this pull request Nov 18, 2026
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.

2 participants