Repository navigation
docs(reference): bring the 3.3 release docs to 3.3.0-rc.0 - #8883
Conversation
576e1a2 to
9b8e001
Compare
…ves assignments (#8501) 3.3 adds no field that exists only on a deprecated task. Withdraw from get_products: refine[].package (and package-forecast-input.json), refinement_applied[] result_product_id / resolved_start_time / resolved_end_time, filters.target_audiences, include_collections and collections, and experimental price_adjustments on pricing options (with price-adjustments.json, the mismatch error details, and the vectors). Move include_execution_readiness / execution_readiness to list_products. Withdraw landing_page_url and trackers from the deprecated sync_creatives assignments[] row; the assign operation keeps them. #8866 opened the assignments[] row and the refine[] product entry, so both now reject the withdrawn request fields by name (not: required), with a description sentence: the row rejects trackers and landing_page_url, and every refine[] scope rejects package. The schema and the training agent's INVALID_REQUEST agree. The response-side refinement_applied fields are just undefined. Updates the training agent, the execution readiness storyboard, the v4 registry (canonical_price_adjustments_required_in_4_0), the oneOf discriminator baseline, docs, and tests. #8866 already removed the additive-minor baseline rows, and the 3.3 release pages are left to #8883. counting_mechanisms is left to the create/update_media_buy PR, which removes it from the shared measurement-terms.json. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nd update_media_buy (#8501) create_media_buy and update_media_buy are deprecated compatibility tasks, so 3.3 adds nothing to them. Six fields the 3.3 betas added to them are removed; the live tasks keep every one they also carry. - predecessor_media_buy_id, lineage_reason: off create_media_buy; stay on buy_products, accept_proposal and get_media_buys. - artifact_webhook.signing_profile: off create_media_buy; no live task has artifact_webhook, so it is signed with adcp/webhook-signing/v1. - start_requires_all_creatives_approved: off package-request, package-update and core/package.json; stays on control_media_buy and get_media_buys. - target_audiences: off package-request; with #8758 withdrawing the get_products copy, no 3.3 wire form remains. - trackers, landing_page_url: off core/creative-assignment.json; stay on sync_creatives assign, list_creatives and get_media_buys. - billing_measurement.counting_mechanisms: off core/measurement-terms.json (create, update and get_products); the canonical terms gain it in 4.0. The training agent ignores the withdrawn fields on create/update, as the versioning rules require for unknown fields, and no longer echoes them in create/update responses; get_media_buys still reads back what assign set. The 4.0 registry and the task references say where each field lives; the 3.3 release pages are left to #8883. Text that called the purchase, offer-filter or canonical measurement schemas closed now says what #8866 left: the first two are open but don't define the field, and the canonical terms are held closed with the commercial terms until 4.0. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rm remains (#8501) With filters.target_audiences withdrawn from get_products (#8758) and the package copy withdrawn from create_media_buy and update_media_buy, the experimental media_buy.audience_evidence_targets has no 3.3 wire form. - Delete core/audience-evidence-target.json and enums/audience-evidence-relationship.json and their index.json entries. The stable inline relationship enums on audience evidence stay. - Drop the feature from the changeset. Its experimental-status row went with the previous commit, and the 3.3 release pages are left to #8883. - Move the target-matching rules from get_products.mdx into the preserved 4.0 design under purchase_target_audiences_required_in_4_0, keeping a short withdrawal notice at the old anchor; the check keeps its id and its detection no longer keys off the retired feature id. - Retire tests/audience-evidence-targets.test.cjs (preserved at d9b5417) and stop reading the deleted package-forecast-input.json in tests/creative-start-policy.test.cjs. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ddb729b to
a862b14
Compare
…nd update_media_buy (#8501) create_media_buy and update_media_buy are deprecated compatibility tasks, so 3.3 adds nothing to them. Six fields the 3.3 betas added to them are removed; the live tasks keep every one they also carry. - predecessor_media_buy_id, lineage_reason: off create_media_buy; stay on buy_products, accept_proposal and get_media_buys. - artifact_webhook.signing_profile: off create_media_buy; no live task has artifact_webhook, so it is signed with adcp/webhook-signing/v1. - start_requires_all_creatives_approved: off package-request, package-update and core/package.json; stays on control_media_buy and get_media_buys. - target_audiences: off package-request; with #8758 withdrawing the get_products copy, no 3.3 wire form remains. - trackers, landing_page_url: off core/creative-assignment.json; stay on sync_creatives assign, list_creatives and get_media_buys. - billing_measurement.counting_mechanisms: off core/measurement-terms.json (create, update and get_products); the canonical terms gain it in 4.0. The training agent ignores the withdrawn fields on create/update, as the versioning rules require for unknown fields, and no longer echoes them in create/update responses; get_media_buys still reads back what assign set. The 4.0 registry and the task references say where each field lives; the 3.3 release pages are left to #8883. Text that called the purchase, offer-filter or canonical measurement schemas closed now says what #8866 left: the first two are open but don't define the field, and the canonical terms are held closed with the commercial terms until 4.0. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rm remains (#8501) With filters.target_audiences withdrawn from get_products (#8758) and the package copy withdrawn from create_media_buy and update_media_buy, the experimental media_buy.audience_evidence_targets has no 3.3 wire form. - Delete core/audience-evidence-target.json and enums/audience-evidence-relationship.json and their index.json entries. The stable inline relationship enums on audience evidence stay. - Drop the feature from the changeset. Its experimental-status row went with the previous commit, and the 3.3 release pages are left to #8883. - Move the target-matching rules from get_products.mdx into the preserved 4.0 design under purchase_target_audiences_required_in_4_0, keeping a short withdrawal notice at the old anchor; the check keeps its id and its detection no longer keys off the retired feature id. - Retire tests/audience-evidence-targets.test.cjs (preserved at d9b5417) and stop reading the deleted package-forecast-input.json in tests/creative-start-policy.test.cjs. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
a862b14 to
aa14b65
Compare
…ves assignments (#8501) 3.3 adds no field that exists only on a deprecated task. Withdraw from get_products: refine[].package (and package-forecast-input.json), refinement_applied[] result_product_id / resolved_start_time / resolved_end_time, filters.target_audiences, include_collections and collections, and experimental price_adjustments on pricing options (with price-adjustments.json, the mismatch error details, and the vectors). Move include_execution_readiness / execution_readiness to list_products. Withdraw landing_page_url and trackers from the deprecated sync_creatives assignments[] row; the assign operation keeps them. #8866 opened the assignments[] row and the refine[] product entry, so both now reject the withdrawn request fields by name (not: required), with a description sentence: the row rejects trackers and landing_page_url, and every refine[] scope rejects package. The schema and the training agent's INVALID_REQUEST agree. The response-side refinement_applied fields are just undefined. Updates the training agent, the execution readiness storyboard, the v4 registry (canonical_price_adjustments_required_in_4_0), the oneOf discriminator baseline, docs, and tests. #8866 already removed the additive-minor baseline rows, and the 3.3 release pages are left to #8883. counting_mechanisms is left to the create/update_media_buy PR, which removes it from the shared measurement-terms.json. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nd update_media_buy (#8501) create_media_buy and update_media_buy are deprecated compatibility tasks, so 3.3 adds nothing to them. Six fields the 3.3 betas added to them are removed; the live tasks keep every one they also carry. - predecessor_media_buy_id, lineage_reason: off create_media_buy; stay on buy_products, accept_proposal and get_media_buys. - artifact_webhook.signing_profile: off create_media_buy; no live task has artifact_webhook, so it is signed with adcp/webhook-signing/v1. - start_requires_all_creatives_approved: off package-request, package-update and core/package.json; stays on control_media_buy and get_media_buys. - target_audiences: off package-request; with #8758 withdrawing the get_products copy, no 3.3 wire form remains. - trackers, landing_page_url: off core/creative-assignment.json; stay on sync_creatives assign, list_creatives and get_media_buys. - billing_measurement.counting_mechanisms: off core/measurement-terms.json (create, update and get_products); the canonical terms gain it in 4.0. The training agent ignores the withdrawn fields on create/update, as the versioning rules require for unknown fields, and no longer echoes them in create/update responses; get_media_buys still reads back what assign set. The 4.0 registry and the task references say where each field lives; the 3.3 release pages are left to #8883. Text that called the purchase, offer-filter or canonical measurement schemas closed now says what #8866 left: the first two are open but don't define the field, and the canonical terms are held closed with the commercial terms until 4.0. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rm remains (#8501) With filters.target_audiences withdrawn from get_products (#8758) and the package copy withdrawn from create_media_buy and update_media_buy, the experimental media_buy.audience_evidence_targets has no 3.3 wire form. - Delete core/audience-evidence-target.json and enums/audience-evidence-relationship.json and their index.json entries. The stable inline relationship enums on audience evidence stay. - Drop the feature from the changeset. Its experimental-status row went with the previous commit, and the 3.3 release pages are left to #8883. - Move the target-matching rules from get_products.mdx into the preserved 4.0 design under purchase_target_audiences_required_in_4_0, keeping a short withdrawal notice at the old anchor; the check keeps its id and its detection no longer keys off the retired feature id. - Retire tests/audience-evidence-targets.test.cjs (preserved at d9b5417) and stop reading the deleted package-forecast-input.json in tests/creative-start-policy.test.cjs. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ves assignments (#8501) (#8758) * fix(schema): withdraw 3.3 additions from get_products and sync_creatives assignments (#8501) 3.3 adds no field that exists only on a deprecated task. Withdraw from get_products: refine[].package (and package-forecast-input.json), refinement_applied[] result_product_id / resolved_start_time / resolved_end_time, filters.target_audiences, include_collections and collections, and experimental price_adjustments on pricing options (with price-adjustments.json, the mismatch error details, and the vectors). Move include_execution_readiness / execution_readiness to list_products. Withdraw landing_page_url and trackers from the deprecated sync_creatives assignments[] row; the assign operation keeps them. #8866 opened the assignments[] row and the refine[] product entry, so both now reject the withdrawn request fields by name (not: required), with a description sentence: the row rejects trackers and landing_page_url, and every refine[] scope rejects package. The schema and the training agent's INVALID_REQUEST agree. The response-side refinement_applied fields are just undefined. Updates the training agent, the execution readiness storyboard, the v4 registry (canonical_price_adjustments_required_in_4_0), the oneOf discriminator baseline, docs, and tests. #8866 already removed the additive-minor baseline rows, and the 3.3 release pages are left to #8883. counting_mechanisms is left to the create/update_media_buy PR, which removes it from the shared measurement-terms.json. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(schema): readiness binds to buy_products purchases, not legacy packages (#8501) execution_readiness moved to list_products, whose next step is buy_products, but binding_field examples still taught the legacy create_media_buy paths, including packages[].catalogs[], which a purchase does not define. Teach purchases[].optimization_goals[].event_sources[].event_source_id and purchases[].catalog_ids[] in the spec, list_products docs, the readiness and requirement schemas, and the readiness fixtures; label the remaining packages[] paths as legacy. The readiness text no longer claims buy_products rejects unmet purchases: only create_media_buy's rule is specified, and the purchase-side rule stays with adcp#7763. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(v4): price_adjustments shipped through beta.5 (#8501) The canonical_price_adjustments_required_in_4_0 section of the 4.0 page still said the table shipped in 3.3.0-beta.1 through beta.4 and that the beta.1 to beta.4 bundles keep the schemas. beta.5 shipped with it too, and the changeset, the registry entry and pricing-models.mdx already say so. The section now also says canonical-pricing-option.json is held closed with the commercial terms until 4.0, matching the registry entry, rather than "closed in 3.x". Found by the Ladon review. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…nd update_media_buy (#8501) create_media_buy and update_media_buy are deprecated compatibility tasks, so 3.3 adds nothing to them. Six fields the 3.3 betas added to them are removed; the live tasks keep every one they also carry. - predecessor_media_buy_id, lineage_reason: off create_media_buy; stay on buy_products, accept_proposal and get_media_buys. - artifact_webhook.signing_profile: off create_media_buy; no live task has artifact_webhook, so it is signed with adcp/webhook-signing/v1. - start_requires_all_creatives_approved: off package-request, package-update and core/package.json; stays on control_media_buy and get_media_buys. - target_audiences: off package-request; with #8758 withdrawing the get_products copy, no 3.3 wire form remains. - trackers, landing_page_url: off core/creative-assignment.json; stay on sync_creatives assign, list_creatives and get_media_buys. - billing_measurement.counting_mechanisms: off core/measurement-terms.json (create, update and get_products); the canonical terms gain it in 4.0. The training agent ignores the withdrawn fields on create/update, as the versioning rules require for unknown fields, and no longer echoes them in create/update responses; get_media_buys still reads back what assign set. The 4.0 registry and the task references say where each field lives; the 3.3 release pages are left to #8883. Text that called the purchase, offer-filter or canonical measurement schemas closed now says what #8866 left: the first two are open but don't define the field, and the canonical terms are held closed with the commercial terms until 4.0. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rm remains (#8501) With filters.target_audiences withdrawn from get_products (#8758) and the package copy withdrawn from create_media_buy and update_media_buy, the experimental media_buy.audience_evidence_targets has no 3.3 wire form. - Delete core/audience-evidence-target.json and enums/audience-evidence-relationship.json and their index.json entries. The stable inline relationship enums on audience evidence stay. - Drop the feature from the changeset. Its experimental-status row went with the previous commit, and the 3.3 release pages are left to #8883. - Move the target-matching rules from get_products.mdx into the preserved 4.0 design under purchase_target_audiences_required_in_4_0, keeping a short withdrawal notice at the old anchor; the check keeps its id and its detection no longer keys off the retired feature id. - Retire tests/audience-evidence-targets.test.cjs (preserved at d9b5417) and stop reading the deleted package-forecast-input.json in tests/creative-start-policy.test.cjs. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
aa14b65 to
3243273
Compare
…nd update_media_buy (#8501) (#8767) * fix(schema): keep 3.3 additions off the deprecated create_media_buy and update_media_buy (#8501) create_media_buy and update_media_buy are deprecated compatibility tasks, so 3.3 adds nothing to them. Six fields the 3.3 betas added to them are removed; the live tasks keep every one they also carry. - predecessor_media_buy_id, lineage_reason: off create_media_buy; stay on buy_products, accept_proposal and get_media_buys. - artifact_webhook.signing_profile: off create_media_buy; no live task has artifact_webhook, so it is signed with adcp/webhook-signing/v1. - start_requires_all_creatives_approved: off package-request, package-update and core/package.json; stays on control_media_buy and get_media_buys. - target_audiences: off package-request; with #8758 withdrawing the get_products copy, no 3.3 wire form remains. - trackers, landing_page_url: off core/creative-assignment.json; stay on sync_creatives assign, list_creatives and get_media_buys. - billing_measurement.counting_mechanisms: off core/measurement-terms.json (create, update and get_products); the canonical terms gain it in 4.0. The training agent ignores the withdrawn fields on create/update, as the versioning rules require for unknown fields, and no longer echoes them in create/update responses; get_media_buys still reads back what assign set. The 4.0 registry and the task references say where each field lives; the 3.3 release pages are left to #8883. Text that called the purchase, offer-filter or canonical measurement schemas closed now says what #8866 left: the first two are open but don't define the field, and the canonical terms are held closed with the commercial terms until 4.0. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(schema): retire audience evidence targets now that no 3.3 wire form remains (#8501) With filters.target_audiences withdrawn from get_products (#8758) and the package copy withdrawn from create_media_buy and update_media_buy, the experimental media_buy.audience_evidence_targets has no 3.3 wire form. - Delete core/audience-evidence-target.json and enums/audience-evidence-relationship.json and their index.json entries. The stable inline relationship enums on audience evidence stay. - Drop the feature from the changeset. Its experimental-status row went with the previous commit, and the 3.3 release pages are left to #8883. - Move the target-matching rules from get_products.mdx into the preserved 4.0 design under purchase_target_audiences_required_in_4_0, keeping a short withdrawal notice at the old anchor; the check keeps its id and its detection no longer keys off the retired feature id. - Retire tests/audience-evidence-targets.test.cjs (preserved at d9b5417) and stop reading the deleted package-forecast-input.json in tests/creative-start-policy.test.cjs. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(schema): leave the 3.3 release pages to #8883 The release notes, What's new, the 3.2 to 3.3 migration guide and the 3.3 beta page belong to #8883. This PR no longer edits them, so its test stops asserting their "Withdrawn from the deprecated tasks" heading. Refs #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
ebf7851 to
f40f974
Compare
…y 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>
….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>
… 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 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>
#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>
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>
#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>
…on 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>
#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>
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>
…es, 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>
…, 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>
….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>
….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>
#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>
… 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>
…s 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>
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>
31d032a to
bd832f0
Compare
| | Implementing or testing 3.3 before SDK support | After publication, use **3.3 beta.0** artifacts with raw-wire or code-generation workflows. Follow the [3.3 beta program](/docs/reference/3-3-beta). | | ||
| | Running an SDK-backed 3.3 integration test | Use only the exact beta named by the SDK support matrix. Beta.1 is SDK-backed only after its post-publication SDK refresh completes. | | ||
| | Implementing or testing 3.3 before SDK support | Use the signed **3.3 rc.0** artifacts with raw-wire or code-generation workflows, and the exact pin `"3.3-rc.0"`. Follow the [3.3 prerelease program](/docs/reference/3-3-beta). | | ||
| | Running an SDK-backed 3.3 integration test | Use only the exact prerelease named by the [SDK support matrix](/docs/building/by-layer/L4/choose-your-sdk). Until an SDK bundles rc.0, that is beta.5 with `@adcp/sdk` 17.0.0-beta.22 or Python `adcp` 10.0.0b15. | |
There was a problem hiding this comment.
Medium: This names beta.5 (@adcp/sdk 17.0.0-beta.22 / adcp 10.0.0b15) as the SDK-backed test target "until an SDK bundles rc.0." The two sibling docs this PR also updates both say beta.6: choose-your-sdk.mdx ("keep SDK-backed testing on beta.6", table listing 17.0.0-beta.28 / 10.0.0b17 bundling 3.3.0-beta.6) and 3-3-beta.mdx ("keep SDK-backed testing on beta.6", and "17.0.0-beta.24 and later and Python adcp 10.0.0b17 and later support beta.6"). This line sends an adopter to beta.5 while the SDK matrix it points at sends them to beta.6. Reconcile — bump to beta.6, or state why versions.mdx stops at beta.5.
|
|
||
| **Correction: proposal-flow schemas reopened.** 3.2 published the `list_products`, `request_proposals`, `refine_proposals`, `buy_products`, `accept_proposal`, `decline_proposals`, and `control_media_buy` request and response roots closed. It also closed `canonical-proposal`, `canonical-product`, `product-discovery-criteria`, `proposal-refinement`, `package-control`, and `opportunity-context`. [DR-0019](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0019-closed-row-schemas-deliberate-class.md) keeps roots and containers open. So 3.3 and a 3.2.x patch reopen them, as a correction recorded in [DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md). Every payload that was valid stays valid, and the rejections closure provided are kept by name. A field that only the legacy Product defines, such as `format_ids`, `is_custom`, or `product_card`, is still rejected on a canonical product. A root `feed_version` or `pricing_version` on a `request_proposals` response, and `warnings` on an error or submitted `buy_products`, `accept_proposal`, or `control_media_buy` response, are also still rejected. A strict validator on an earlier 3.2 patch still rejects new fields on them, so the rule above applies. `commercial_terms` and the purchases inside it stay closed. | ||
| New enum values (`nmo`, `videoamp`, `mxf`, `mpeg2`, `avc_intra`, `xavc`, `3gp`, `mpeg`, and `m4v` in video `containers`, `print_metrics` in `available-metric`, `operator_fee` in `adjustment-kind`, and the eight Instagram, Facebook, Snapchat and X values in `distribution-identifier-type` ([#8995](https://github.com/adcontextprotocol/adcp/pull/8995))) fall under the 3.x rule that clients tolerate unknown values, but a strict 3.2 validator still rejects them; send them only to 3.3 peers too. | ||
| **Correction: the proposal flow and the other accidentally closed schemas are open.** 3.2 published the `list_products`, `request_proposals`, `refine_proposals`, `buy_products`, `accept_proposal`, `decline_proposals`, and `control_media_buy` request and response roots closed, along with `canonical-proposal`, `canonical-product`, `product-discovery-criteria`, `proposal-refinement`, `package-control`, and `opportunity-context`. 3.2.8 reopened them first. Under the 2026-11-09 decision, 3.3 opens every schema that was closed without a structural reason, and 3.2.11 ([#8864](https://github.com/adcontextprotocol/adcp/pull/8864)) does the same for 3.2 ([Schemas are open by default](#schemas-are-open-by-default)). Opening a schema is a correction under [DR-0036](https://github.com/adcontextprotocol/adcp/blob/main/governance/decisions/DR-0036-closed-schemas-stay-closed-within-a-major.md), not a protocol break. Every payload that was valid stays valid, and the rejections closure provided are kept by name. A field that only the legacy Product defines, such as `format_ids`, `is_custom`, or `product_card`, is still rejected on a canonical product. A root `feed_version` or `pricing_version` on a `request_proposals` response, and `warnings` on an error or submitted `buy_products`, `accept_proposal`, or `control_media_buy` response, are also still rejected. A strict validator built from an earlier 3.2 patch still rejects new fields on these schemas, so the rule above applies. `commercial_terms` and the purchases inside it are held closed until 4.0. |
There was a problem hiding this comment.
(non-blocking) The blank line between the "New enum values…" paragraph (L669) and this **Correction:** paragraph was dropped, so in MDX the two render as one paragraph and the "Correction" lead-in folds inline. Same trailing-space-instead-of-blank-line merge appears at whats-new-in-3-3.mdx (New-in-rc.0 → "Schemas are open by default", and "…policy-ID uniqueness" → "Conformance") and release-notes.mdx (the - **rc.0:** bullet → ### Behavior changes to review). Restore the blank separators.
There was a problem hiding this comment.
Ladon verdict: Approve
Approve — docs-only refresh moving AdCP 3.3 release docs from beta.5 to rc.0; no static/schemas/source/**, no wire/spec-drift surface touched. Two patch changesets present and correctly scoped (normative docs under docs/reference/**, no schema change).
Medium findings
- docs/reference/versions.mdx:119 — SDK-backed test target disagrees across the three updated version docs (beta.5 vs beta.6); likely partial refresh giving adopters conflicting guidance.
Notes
- One non-blocking Low (dropped blank lines merging bold lead-ins in 3-2-to-3-3.mdx:670 and three other MDX files) — omitted from gate consideration.
high_riskis true only via(modified)matches ondocs/reference/**; no deletions, no critical/high findings. Row 5 requires both a modified high-risk file AND a medium finding — the single medium is on versions.mdx (adocs/reference/**match), so row 5 technically fires.
Re-evaluating: versions.mdx:119 is itself a modified high-risk-path file with a medium finding, so row 5 applies → escalate, not approve.
Medium findings
- docs/reference/versions.mdx:119 — SDK-backed test target disagrees across the three updated version docs (beta.5 vs beta.6)
… preview to 3.3-rc.0 (#9072) @adcp/sdk 17.0.0-beta.29 pins AdCP 3.3.0-rc.0, and Python adcp 10.0.0b20 adopts the same bundle. tests/sdk-runtime-compat ties Choose your SDK and the training agent to the installed SDK, so bump it, and move TRAINING_AGENT_HOSTED_PREVIEW to { wireVersion: '3.3-rc.0', bundle: '3.3.0-rc.0' }, the prerelease beta.29 negotiates. The preview-version and tenant-smoke tests follow, with 3.3-beta.6 as the previous preview. Docs, replacing the forward-looking rc.0 text from #8883: - Choose your SDK names 17.0.0-beta.29 and 10.0.0b20, both on 3.3.0-rc.0. - The prerelease page: 17.0.0-beta.24 to beta.28 and 10.0.0b17 to b19 support beta.6 (b19's wheel bundles 3.3.0-beta.6), beta.29 and b20 support rc.0, and the test-agent preview serves 3.3-rc.0. It also says what the agent refuses: installment_refs (#8986), and the assignment operations each route lists (#8997). - The release notes, Versions, the quickstart, and the creative33 sandbox note name the new versions and pin. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Release-docs pass for
3.3.0-rc.0(cut planned for Mon 2026-11-16). "Release docs are current" is GA criterion 5 in #8600. Ready for the rc.0 cut. Every dependency marker is resolved.The docs snapshot archives
docs/at the release tag, so this needs to merge before the rc.0 Version Packages PR. The pages describe rc.0 as published on 2026-11-16.What changes
RC framing. The release notes, What's new, the 3.2→3.3 migration guide, Versions, and the 3.3 rows of Choose your SDK move from beta.5 to rc.0. The prerelease page keeps its
/docs/reference/3-3-betaURL and is retitled "3.3 prerelease program", as the 3.2 page was at its RC (#7288). rc.0 is added to the checkpoint and wire-pin tables ("3.3-rc.0", selector3.3-rc), and the GA target is restated from #8600. The in-review table reflects the 3.3.0 milestone as of 2026-11-12.Schemas open by default (WG decision, 2026-11-09). #8866 rewrites most of the old "closed stays closed" lines itself. This PR leaves those lines alone and fixes the ones #8866 doesn't touch:
3-1-to-3-2.mdx(old line 337);optimization-reporting.mdx(old line 427);specs/daily-budget-constraints.md(old line 25).It also adds:
extra, Zod).The 3.2 line opened in 3.2.11 (#8864, published 2026-11-13), and the docs name that release.
Closed-schema triage (#8501 re-triage, 2026-11-09). A new section in the migration guide lists every field: what stays in 3.3, what leaves (deprecated surface, or extending the commercial terms held closed until 4.0), and what moves. The release notes, What's new, and the prerelease page summarize it. The withdrawn-surface lines match
experimental-status.mdxas #8758, #8767, #8762 and #8957 merged it.Deprecations. Boolean overlay
demographicsis added (from #8866). The six-month-notice promises are replaced: deprecated 3.3 features are expected to be removed in 4.0, and 3.3 stays supported for at least 12 months after 4.0 GA (decided 2026-11-10; the policy change is in #8858).versioning.mdxand the policy pages are untouched, apart from the prerelease-pin paragraph below.Other rc.0 changes. Covered as each merged:
authorized_agentsURLs;creative.supports_registry_policy_enforcement;card_image_sizes;UNRECOGNIZED_TERMS;https_put;supported_delivery_types;contract_version1.2requirepackage_idwithmedia_buy_id, and a seller MUST serve callers pinned below 3.31.0or1.1offerings;geo_value_labels, geo-entryvalue_labels). They never change what is targeted, and buyers sendgeo_value_labelsonly to 3.3 peers.beta.6.
3.3.0-beta.6published on 2026-11-13 (tagv3.3.0-beta.6atbf4aa6dbb3, Version Packages #8801), for SDK testing over the weekend ahead of rc.0 on Monday. Per #8801's changelog, it carries every item above. Changes:The beta.6 docs snapshot carries the beta.5-era pages, which is acceptable for a beta; this PR merges before the rc.0 Version Packages PR.
After beta.6. Merged after beta.6, so described as rc.0-only in the rc.0 checkpoint rows, the feature index, and the "new in rc.0" notes:
distribution-identifier-typevalues. It also appears in What's new and in the migration guide's send-only enum values.sync_creativesassignment operations they accept increative.assignment_operations. feat(schema): declare the sync_creatives assignment operations a seller accepts #8997 brought its own release-doc text. See Merge interactions.audience_targetingsay "no member push" now thatsupported_activation_methodsexists, and say that discovery comes withaudience_include#8936):media_buy.audience_targetingno longer promises inline member push. feat(schema): audience targeting without inline member push #8996 wrote its own release-doc text.cta_valuesfor the per-cardcta#8960):image_carouselcta_values. feat(schema): image_carousel declares cta_values for each card's cta #9001 wrote its own What's new section.submittedbranches match their published async status files.get_media_buy_deliverysellers SHOULD return at least oneby_packagerow, one per package.by_package: []stays valid in 3.x, andminItems: 1is proposed for 4.0 in 4.0: require at least one by_package row in get_media_buy_delivery #8973. It gets a behavior-change bullet, a What's new sentence, migration checklist row 58, and av4-compatibility.mdx"not checked yet" entry for 4.0: require at least one by_package row in get_media_buy_delivery #8973.The release-notes feature index now has a beta.6 bullet and an rc.0 bullet. The in-review table is refreshed to 2026-11-14: #8149, #8107 and #8856 closed, #8943 has #9011, and #9014 and #8998 (#9013) are new.
#8986 (the training agent refuses
installment_refs) is server-only with no changeset, so the rc.0 rows don't list it. The post-cut follow-up describes it in the test-agent section once the preview moves to rc.0.Each item has a release-notes entry and a What's new bullet. Where an adopter has something to do, the migration guide also gets a section or a checklist row (rows 50 to 60).
SDKs.
@adcp/sdk17.0.0-beta.22 (verified on npm; it bundles 3.3.0-beta.5, 3.2.8, 3.1.31 and 3.0.25) and Pythonadcp10.0.0b15. Choose your SDK still names 17.0.0-beta.21, becausetests/sdk-runtime-compat.test.cjsrequires it to match the@adcp/sdkthis repository installs.adcp9.6.2, which reads the A2A profile'sinputmember.@adcp/sdk17.0.0-beta.24 and later (this repository installs beta.28) and Pythonadcp10.0.0b17 and later.Prerelease pins, unpinned discovery, and anonymous capabilities (approved by Brian, separate commit). These came from a field report: a 3.3-beta reader pinned
get_adcp_capabilitiesto3.3-beta.5against a 3.0-only seller and never retried.versioning.mdx(pre-release pins) and the 3.3 prerelease page: a buyer MUST send a prereleaseadcp_versiononly to a peer that advertises that exact value. It SHOULD discover unpinned, and SHOULD retry unpinned or at a listed version onVERSION_UNSUPPORTED. This matches the existing retry SHOULD and the error code's recovery hint; the schema is unchanged.authentication.mdx: a seller SHOULD serveget_adcp_capabilitieswithout credentials. It is a SHOULD in 3.3 and a MUST in 4.0.mcp-guide.mdx: a gateway that allow-lists JSON-RPC methods SHOULD letserver/discover,initializeandtools/listthrough without credentials.v4-compatibility.mdxunder "Changes not checked yet". That page had no anonymous-discovery item, and a graded check would need a registry and storyboard entry.Dependency markers
All resolved. On the cut day, 2026-11-16, the rc.0 date markers were confirmed and dropped. The SDK-prerelease and test-agent markers became forward-looking text: SDK prereleases that adopt
3.3.0-rc.0follow within days. A follow-up PR onmainfills in the real TypeScript and Python versions and moves the test-agent preview after rc.0 publishes. That PR needs@adcp/sdkbumped to the rc.0 prerelease first, becausetests/sdk-runtime-compat.test.cjsties Choose your SDK and the training agent to the installed SDK. #8854 is written up as in review, not in rc.0.Merge interactions
Rebased onto
mainatad3bab2addon the cut day. The rc.0 rows and notes now cover every changeset pending for rc.0. Additions:input_required→input-required,click_through→clickthrough,underdelivery→under_delivery. It gets a migration section with old and new spellings, checklist row 59, a behavior change, a What's new bullet, and a "Renamed in rc.0" row.human_review_requiredis accepted, and twosync_plansrules are stated. Checklist row 60, a release-notes bullet, and a What's new sentence.Choose your SDK takes main's
@adcp/sdk17.0.0-beta.28. The in-review table moves to 2026-11-16: compliance: gate audience_buy_flow's member push on the seller accepting inline pushes (follow-up to #8936) #8998 closed, and Reliable Reporting subscriptions: do structural dimensions (date, media_buy_id, account_id) count as unmapped_dimensions? #8987 is new.schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) #8854 is in review, not in rc.0 (Sunday rule, 2026-11-15). schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) #8854 withdraws
metric_idand restoresevaluatoras a deprecatedx-entity-typesvalue. It had changes requested and had not merged by Sunday, so its eight markers are gone. The pages say it is in review: rc.0's schemas still carrymetric_id, which the triage still lists as leaving 3.3, and still lackevaluator, which is out of the "stays in 3.3" lists.signing_profileis no longer part of schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) #8854 and stays.Rebased onto
mainat8d235c3adb, after fix(registry): origin-only authorized_agents matching in the validator and registry #9011, fix(registry): signing_keys pinned only if every matching authorized_agents entry pins #9017, chore(deps): bump @adcp/sdk to 17.0.0-beta.26 for hosted grading #9018 and test(schema): keep the catalog's distribution identifier types in step with the schema enum #9010 merged. chore(deps): bump @adcp/sdk to 17.0.0-beta.26 for hosted grading #9018 moved the test-agent preview to3.3-beta.6and bumped@adcp/sdkto 17.0.0-beta.26. The rebase kept this branch's side of the overlapping lines, and a follow-up commit applies chore(deps): bump @adcp/sdk to 17.0.0-beta.26 for hosted grading #9018's facts:fix(registry): origin-only authorized_agents matching in the validator and registry #9011 and fix(registry): signing_keys pinned only if every matching authorized_agents entry pins #9017 (multiple matching
authorized_agentsentries: scopes combine as a union, and asigning_keyspin holds only if every matching entry pins) join the rc.0 rows. Their migration text came through unchanged. The in-review table moves to 2026-11-15.Rebased onto
mainat145ba504db, after feat(schema): audience targeting without inline member push #8996, feat(schema): image_carousel declares cta_values for each card's cta #9001, fix(schemas): align inline submitted branches with their published async status files #8934 and docs(schemas): guide sellers to return at least one by_package row in get_media_buy_delivery #8970 merged. feat(schema): audience targeting without inline member push #8996 and feat(schema): image_carousel declares cta_values for each card's cta #9001 edited the release docs onmain; the rebase was clean and kept their text.Rebased onto
mainat01abd1920e, after feat(schema): add Instagram, Facebook, Snapchat and X distribution identifier types #8995, fix(training-agent): refuse installment_refs with UNSUPPORTED_FEATURE #8986 and feat(schema): declare the sync_creatives assignment operations a seller accepts #8997 merged. The feat(schema): add Instagram, Facebook, Snapchat and X distribution identifier types #8995 markers are resolved. feat(schema): declare the sync_creatives assignment operations a seller accepts #8997 edited the release docs onmain. The rebase kept this branch's side of the overlapping hunks, and a follow-up commit restores feat(schema): declare the sync_creatives assignment operations a seller accepts #8997's text:feat(schema): declare the sync_creatives assignment operations a seller accepts #8997's migration and What's new sections and its behavior-change bullet came through unchanged, and none of the text it replaced survived.
Rebased onto
mainatbf4aa6dbb3, the beta.6 release. The beta.6 date markers are resolved. beta.6 consumed fix(schema): withdraw 3.3 additions from get_products and sync_creatives assignments (#8501) #8758's changeset and moved it to.changeset/pre/, so this PR no longer edits it: the earlier one-line fix is dropped, because the beta.6 changelog is already generated. The released beta.6 changelog still names the section "Withdrawn from the deprecated tasks"; the migration guide calls it "Closed-schema triage: what stays in 3.3".Rebased onto
mainataa94f361d7, after feat(schema): display labels for geo targeting codes #8966 merged. feat(schema): display labels for geo targeting codes #8966 ships in beta.6. It is added to the beta.6 checkpoint row, the feature index, What's new, migration checklist row 56, the send-only-to-3.3-peers table, and a section under Adopt by capability.Rebased onto
mainat39334ab747, after spec(reporting): report definitions at contract_version 1.2 require a package_id dimension (#8971) #8983 merged. The spec(reporting): report definitions at contract_version 1.2 require a package_id dimension (#8971) #8983 markers are resolved, and the serving rule reads as a MUST everywhere it appears. The range also brings the 3.2.11 forward-merge (fix(compliance): register the published and qualified 3.2.11 hosted bundle #8985), which touches no page this PR edits.Rebased onto
mainate903ee6320, after feat(schema): assign a creative to specific installments of a package (experimental) #8972 merged. The feat(schema): assign a creative to specific installments of a package (experimental) #8972 markers are resolved, and the migration guide adds feat(schema): assign a creative to specific installments of a package (experimental) #8972's capability rule: a buyer sendsinstallment_refsonly to a seller that lists the feature id, and a seller without it rejects the field withUNSUPPORTED_FEATURE.Rebased onto
mainata7af5176c1, after feat(media-buy): choose installments through refine_proposals without opening commercial_terms (#8967) #8974 merged. The feat(media-buy): choose installments through refine_proposals without opening commercial_terms (#8967) #8974 markers are resolved.v4-compatibility.mdxtakes feat(media-buy): choose installments through refine_proposals without opening commercial_terms (#8967) #8974's installment paragraph unchanged, so this PR's only change on that page is the anonymous-discovery bullet. The migration guide now says the beta.1core/installment-change-set.jsonandinstallment_changesdimension return in rc.0 undermedia_buy.installment_refinement.Earlier rebases. Each kept the merged PR's wording where it overlaps:
demographicsdeprecation and the Schemas-are-open bullet;Held closed until 4.0. The nodes inside
commercial_termsandproposal-budget-constraintare described as "held closed until 4.0". Nothing here says the digest stops a 3.2 buyer from accepting a term it ignored.Open PRs. Trial merges against schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) #8854 conflict only where schemas: withdraw metric_id and restore evaluator as deprecated (#8501 entries 6, 26) #8854 already conflicts with
main.Checks run
npm run lint:schema-linksnpm run test:docs-navnpm run check:owned-linksnpm run test:v4-compatibility-registrynode scripts/build-compliance.cjs --checkchangeset statusPre-commit hook. The #8995 and #8997 commit ran the full pre-commit hook at low load, and all four server-unit shards passed. Thirteen other commits skipped it. The commits that resolve the #8974, #8972, #8983 and beta.6-date markers, add #8983, add beta.6, add #8966, and add #8995 were made with
HUSKY=0, with approval from Release Planning (standing for docs-only commits on this PR through the RC).precommit:server-unittimed out at host load 150–170. Unrelated server suites hit spawnETIMEDOUTand 10–30 s timeouts, and failed the same way when rerun on their own under that load. These commits touch only docs, with noserver/,tests/,scripts/,static/or package files. The other hook steps were run by hand and passed:test:unit, apart from 10 s timeouts under load (up to 232) instripe-client,compliance-validate-input-gates,compliance-authored-tool-gates,compliance-sdk-rc-transport,ipr-check-and-recordandadagents-builder-xss. Each passed when run alone on the same non-docs tree;typecheck.CI is the gate. Rebased pushes skip the pre-push storyboard matrix (
ADCP_SKIP_STORYBOARD_MATRIX=1), and CI runs the storyboards. On the latest push, run at low load, the matrix passed/signals(57 clean against a floor of 45). It was stopped partway through/salesafter 40 minutes.Not changed
specification-lifecycle.mdx, schemas, and governance records.versioning.mdxgets only the buyer prerelease-pin paragraph above. Also out of scope:docs.jsonbanner, which flips at the cut with the rc.0 snapshot PR;versions.mdx(3.2.1, 3.1.24, 3.0.26).🤖 Generated with Claude Code