Repository navigation
feat(media-buy): choose installments through refine_proposals without opening commercial_terms (#8967) - #8974
Conversation
…docs #8967's PR is #8974: installment_changes (include or omit) on 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>
There was a problem hiding this comment.
Ladon verdict: Escalate to human review
Escalate — gated paths touched without required approval.
This PR modifies the published protocol surface under static/schemas/source/** (7 gated files: installment-change-set.json, installment-change.json, proposal-refinement-reason.json, index.json, proposal-refinement.json, refine-proposals-response.json, get-adcp-capabilities-response.json). Those paths are under a hard, deterministic approval gate (gated_paths: true), and review_decision is REVIEW_REQUIRED — not APPROVED. Per decision-table row 2, a gated-path PR cannot auto-approve until a human/CODEOWNERS approval lands.
Escalation reasons
- Gated schema source files changed; human/CODEOWNERS review required before merge. Files: static/schemas/source/core/installment-change-set.json, static/schemas/source/core/installment-change.json, static/schemas/source/enums/proposal-refinement-reason.json, static/schemas/source/index.json, static/schemas/source/media-buy/proposal-refinement.json, static/schemas/source/media-buy/refine-proposals-response.json, static/schemas/source/protocol/get-adcp-capabilities-response.json.
The reviewer found no Critical/High/Medium findings: the change is additive (new feature id media_buy.installment_refinement), every new node is x-status: experimental / x-added-in: 3.3.0, carries a correct minor changeset, preserves schema↔docs coherence across all 7 doc pages, introduces no undiscriminated oneOf, breaks no released-artifact immutability, and leaves signed terms untouched. It is not breaking-class. Once a human approval satisfies the gate, this falls through to approve on the clean diff.
Why human review
- Gated paths touched (static/schemas/source/**) and review_decision is REVIEW_REQUIRED, not APPROVED — human/CODEOWNERS approval required before merge. Files: installment-change-set.json, installment-change.json, proposal-refinement-reason.json, index.json, proposal-refinement.json, refine-proposals-response.json, get-adcp-capabilities-response.json.
- This PR touches a path under a hard, non-overridable approval gate (static/schemas/source/core/installment-change-set.json (added) matches
static/schemas/source/**; static/schemas/source/core/installment-change.json (added) matchesstatic/schemas/source/**; static/schemas/source/enums/proposal-refinement-reason.json (modified) matchesstatic/schemas/source/**; static/schemas/source/index.json (modified) matchesstatic/schemas/source/**; static/schemas/source/media-buy/proposal-refinement.json (modified) matchesstatic/schemas/source/**; static/schemas/source/media-buy/refine-proposals-response.json (modified) matchesstatic/schemas/source/**; static/schemas/source/protocol/get-adcp-capabilities-response.json (modified) matchesstatic/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.
…docs #8967's PR is #8974: installment_changes (include or omit) on 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>
… opening commercial_terms (#8967) A buyer can ask for specific installments of a product during negotiation (experimental, media_buy.installment_refinement). installment_changes returns on proposal-refinement.json with the #8246 shape: a list of {product_id, installment_ref, action}, unique by (product_id, installment_ref), with installment_ref the closed core/canonical-installment-ref.json. The seller answers with a draft that buys, for each named product, one product whose installments are exactly the selected set (the product's installments with omits removed and includes added), often one it derives for the selection. Buying that product buys its complete installment set, so terms_digest binds the choice through the product_id and nothing in commercial_terms changes. unsatisfied_installment_changes on the refine_proposals result row repeats each unmet entry with a reason, on a partial or unable result with constraint_unsatisfiable. installment_changes joins proposal_refinement.supported_dimensions, and listing it requires media_buy.installment_refinement in experimental_features. The rules are normative in the schemas, refine_proposals.mdx and collections-and-installments.mdx: an offered product's installments never change, the buyer rejects a mismatched answer, and the seller checks product membership before it resolves any reference. New core/installment-change.json and core/installment-change-set.json, every new field experimental and added in 3.3.0. The MCP analysis pins (714 instances, 195 unique) and the capabilities worst case (99,101,140 bytes, on top of #8458's 99,101,090) are re-measured. The 4.0 page, registry entry, known limitations and experimental status say what 3.3 offers before 4.0 binds the slots in the signed terms. Training-agent support is out of scope. Refs #8967, #8501 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
d912d2d to
6657af7
Compare
There was a problem hiding this comment.
Ladon verdict: Escalate to human review
Escalate — gated schema paths require human/CODEOWNERS approval, and this PR introduces a new experimental protocol surface.
No blocking findings. Reviewer reports a clean pass: schema↔docs coherence verified across refine_proposals.mdx, collections-and-installments.mdx, experimental-status.mdx, v4-compatibility.mdx, and the capabilities doc; the minor changeset is protocol-scoped and correct (additive experimental fields); the response-shape not.anyOf/then.anyOf forbidding extensions match the new contract test; no new undiscriminated oneOf; withdrawn media_buy.installment_selection stays withdrawn. No Critical/High/Medium findings.
Why escalate (not approve): This PR touches files under the hard, deterministic approval gate (static/schemas/source/**) and review_decision is REVIEW_REQUIRED, not APPROVED. Decision-table row 2 forces escalate until a human/CODEOWNERS approval is recorded — a clean diff cannot lift this gate. Additionally, re-introducing the experimental media_buy.installment_refinement protocol surface is a governance/ratification matter that is a human act, reinforcing escalation.
Escalation reasons:
- Gated paths touched (
static/schemas/source/**) withreview_decision: REVIEW_REQUIRED— human/CODEOWNERS approval required before merge. Files: installment-change-set.json, installment-change.json, proposal-refinement-reason.json, index.json, proposal-refinement.json, refine-proposals-response.json, get-adcp-capabilities-response.json. - New experimental protocol surface (installment_refinement) added — ratification is a human act.
This continues the prior escalate decision: the gate condition still holds (review_decision unchanged), so the escalation stands pending human sign-off. No code changes are requested.
Why human review
- Gated paths touched (static/schemas/source/**) and review_decision is REVIEW_REQUIRED, not APPROVED — human/CODEOWNERS approval required before merge. Files: installment-change-set.json, installment-change.json, proposal-refinement-reason.json, index.json, proposal-refinement.json, refine-proposals-response.json, get-adcp-capabilities-response.json.
- Re-introduces the experimental media_buy.installment_refinement protocol surface — ratification of a new protocol addition is a human act, not auto-approvable.
- This PR touches a path under a hard, non-overridable approval gate (static/schemas/source/core/installment-change-set.json (added) matches
static/schemas/source/**; static/schemas/source/core/installment-change.json (added) matchesstatic/schemas/source/**; static/schemas/source/enums/proposal-refinement-reason.json (modified) matchesstatic/schemas/source/**; static/schemas/source/index.json (modified) matchesstatic/schemas/source/**; static/schemas/source/media-buy/proposal-refinement.json (modified) matchesstatic/schemas/source/**; static/schemas/source/media-buy/refine-proposals-response.json (modified) matchesstatic/schemas/source/**; static/schemas/source/protocol/get-adcp-capabilities-response.json (modified) matchesstatic/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.
…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>
With #8967 (#8974) on main, the installments a package bought are the selected set when the buyer chose installments through refine_proposals. Link the new section from the creatives-per-installment paragraph. Committed with HUSKY=0: a one-sentence docs change; staging docs/ runs the full server unit suite, which exceeds its budget at current host load. Refs #8968 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>
… (experimental) (#8972) * feat(schema): assign a creative to specific installments of a package (#8968) Add experimental installment_refs (media_buy.installment_creative_assignment) to the sync_creatives assign and replace operations: an array of core/canonical-installment-ref.json, unique, 1 to 500 (a canonical product's installments cap). Present, the assignment applies only to those installments of the package; absent, to every installment, as before. - Within one installment, weight, rotation and placement routing work unchanged; placement routing and installment scope intersect, and an installment no assignment applies to gets no other installment's creative. - Each ref names an installment in the purchased product's installments, else VALIDATION_ERROR. A change to an installment past its change_cutoff is refused with CREATIVE_DEADLINE_EXCEEDED, never accepted silently. No new error codes. - A supplied list replaces the scope; omission on an assign upsert keeps it. replace transfers the scope unless it supplies one, merge moves it, and unassign and merge reject installment_refs by name. - Readback on get_media_buys packages[].creative_approvals[] and list_creatives assignments.assigned_packages[], omitted for an assignment on every installment. - Buyers send it only to sellers listing the feature (versioning rule 4); others reject it with UNSUPPORTED_FEATURE. New experimental-status row. Not on core/creative-assignment.json, the deprecated create_media_buy and update_media_buy rows, or the deprecated sync_creatives assignments[] row: 3.3 adds nothing to deprecated tasks (#8501, #8767). Docs: sync_creatives section with a two-post creator example, a creator-brief section in collections-and-installments, readback rows. Tests: tests/installment-creative-assignment.test.cjs in test:schemas. Committed with HUSKY=0: precommit:server-unit hit its 1500s budget at host load ~110-140. Its timed-out files pass alone; the other hook steps were run by hand and pass. No server file is touched. Refs #8968 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(sync_creatives): validate the installment example in its test, not via $schema (#8968) check-schema-links rejects /schemas/latest/ for a schema already released in v3, and sync-creatives-request.json is released in 3.2.10, which lacks installment_refs. Follow the assignment-trackers example: drop $schema from the creator example and have tests/installment-creative-assignment.test.cjs extract the block from the doc and validate it against the source schema. Committed with HUSKY=0 for the same reason as the previous commit; this commit touches one doc example and one root test file, both run locally. Refs #8968 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(collections): tie installment_refs to chosen installments (#8968) With #8967 (#8974) on main, the installments a package bought are the selected set when the buyer chose installments through refine_proposals. Link the new section from the creatives-per-installment paragraph. Committed with HUSKY=0: a one-sentence docs change; staging docs/ runs the full server unit suite, which exceeds its budget at current host load. Refs #8968 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Brings the branch to a7af517 (#8974). package.json test:schemas keeps both tests/installment-refinement.test.cjs and tests/reporting-report-definition-vectors.test.cjs. Pins re-measured: controller parity 1_330_906 bytes (bound 1_388_000); capabilities and model-context bounds pass. 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>
#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>
…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>
#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>
…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>
#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>
…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>
#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>
…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>
#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>
…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>
#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>
…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>
#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>
…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>
#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>
* 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.
Implements the RFC in #8967. Refs #8501, #8230, #8246, #8537.
For the 3.3 RC (Mon 2026-11-16).
static/schemas/source/**is Ladon-gated, so a human merges this.Summary
A buyer can now choose specific installments of a product during negotiation, without adding anything to
commercial_terms. It's experimental, under the new feature idmedia_buy.installment_refinement. The adopter is Availnet, a creator marketplace, through Apostra.installment_changesreturns onmedia-buy/proposal-refinement.json, which fix(schemas): open the 3.3 schemas that were meant to be open #8866 opened. Each entry is{ product_id, installment_ref, action }, and the entries are unique by(product_id, installment_ref).installment_refis the closedcore/canonical-installment-ref.json, andactionisincludeoromit. It counts as a revise dimension, andfinalizeandextend_holdforbid it. The new files arecore/installment-change.json(one entry) andcore/installment-change-set.json(the list, with the uniqueness rule).installments[]with everyomitremoved and everyincludeadded. A satisfying draft buys one product whoseinstallments[]is exactly the selected set: the product itself, or one the seller offers for the selection in its place, such ascreator_juniper_vale__2026-12-03. Under today's rule, buying a product buys its complete installment set, soterms_digestbinds the choice through theproduct_id.unsatisfied_installment_changeson therefine_proposalsresult row repeats each unmet request entry and adds a requiredreason, on apartialorunableresult withreason_code: "constraint_unsatisfiable". Thepartialinvariant covers it: every draft satisfies every entry the list leaves out.installment_changesjoinsmedia_buy.proposal_refinement.supported_dimensions. The capabilities schema requiresmedia_buy.installment_refinementinexperimental_featureswhenever a seller lists that dimension. Buyers sendinstallment_changesonly to such a seller, and any other seller rejects the omitted dimension withUNSUPPORTED_FEATUREunder the existingsupported_dimensionsrule.media_buy.installment_selectionisn't reused, because that id meant the signed field.Normative rules
These are in the schema descriptions, in
refine_proposals.mdx"Choose installments (experimental)" and incollections-and-installments.mdx"Choosing installments (experimental)".product_id. The digest binds theproduct_id, not the slots, so this rule keeps an accepted selection fixed.installments[]and rejects a mismatch. After finalize,holds[]reads back the slots the hold covers.product_idis bought by the source proposal, or added byproduct_changesin the same request, before it resolves any reference, as feat(media-buy): add installments to the canonical product and let a proposal buy named slots #8246 required. The ordered checks are feat(media-buy): add installments to the canonical product and let a proposal buy named slots #8246's:UNSUPPORTED_FEATUREfor an undeclared dimension;INVALID_REQUESTfor a duplicate or contradictory entry, or a product outside the proposal or omitted byproduct_changes;REFERENCE_NOT_FOUNDfor an unresolvable reference;constraint_unsatisfiablewith the entry listed.Nothing in
commercial_terms.product-purchase.jsonstill carries noinstallments. Every new field isx-status: experimentalandx-added-in: 3.3.0. 4.0 keeps the signed design (installment_selection_required_in_4_0), and the 4.0 page and registry now say what 3.3 offers in the meantime.For reviewers
installments[]equalling the selected set, so there's no new field on the canonical product or inside the signed terms. feat(media-buy): add installments to the canonical product and let a proposal buy named slots #8246's rule that anincludenames one of the product's own declared installments is widened to "an installment of a collection the product'scollectionsname". Without that, a buyer couldn't add a slot back to a derived product that dropped it.reasonis free text. The result row'sreason_codealready saysconstraint_unsatisfiable. A per-entry code can be added later on the open item if adopters want one.tests/mcp-schema-analysis.test.cjsgo from 711 to 714 definition instances and from 192 to 195 unique definitions: the two new files pluscanonical-installment-ref, now reached from therefine_proposalsinput.mainafter feat(schema): add media_buy.supported_delivery_types to capabilities #8458 (99,101,090) it measures 99,101,140, which is pinned in the test and insecurity.mdx.tools/listbudget (162 KiB) and the projection bounds hold unchanged.TYPED_DIMENSIONSdoesn't listinstallment_changes, so it never advertises the dimension, and no storyboard sends it.installments[]is the selection. The only shared file iscollections-and-installments.mdx, where the two PRs edit adjacent sections.Testing
Rebased onto
main38a83d1d44(after #8793 and #8458) as6657af7001, with the worst case re-measured at 99,101,140 / 190 open positions. On the rebased tree these pass:lint:additive-minor,capabilities-structural-bounds,mcp-schema-analysis(714/195),test:mcp-schema-projection,product-discovery-schema-parity, the installment, withdrawn and canonical-installments tests,build:compliance -- --check, the hook guards,typecheckand the image check.The full run below was on
maina2a7d20fffplus this commit, run sequentially:npm run build:schemas: pass.npm run test:schemas: 1197/1197, plus premium-display 10/10 and geo-region 6/6. The newtests/installment-refinement.test.cjshas 9 tests:installment_changesalone is a valid revise, including a swap. Rejected are a missingaction,action: "swap", an extra member inside the closedinstallment_ref, an empty list, an exact duplicate, andinstallment_changesonfinalizeorextend_hold. The change set declaresunique_by.partialresult whose only unsatisfied list isunsatisfied_installment_changessatisfiesconstraint_unsatisfiable. An entry withoutreasonis rejected, and so is the list on arevisedorfinalizedresult.installment_changesdimension withoutmedia_buy.installment_refinementis rejected, and with it, accepted.experimentaland3.3.0.product-purchase.jsonhas noinstallments, and only the refinement id has an experimental-status row.withdrawn-to-4-0.test.cjskeeps the signedpurchases[].installmentswithdrawn and its 4.0 check, and stops asserting that the request-side pieces are absent.canonical-installments.test.cjsnow checks thatmedia_buy.installment_selectionhas no registry row, and allows the new row's prose to name it.npm run test:mcp-schema-projection(pins re-measured as above),npm run test:examplesandnpm run test:contracts506/506 pass.capabilities-structural-boundspasses, andproduct-discovery-schema-paritypasses 4/4.npm run lint:additive-minor(2 recorded, 0 new),test:additive-minor, the 4.0 registry lint and test,audit-oneof --check, andbuild:compliance -- --check(1889 references, after regenerating the links for the newrefine_proposalssection). JSON-schema validation of the 7 changed docs pages and the changeset scope check pass too.ADCP_SKIP_STORYBOARD_MATRIX=1for host load, as the playbook allows; this PR's only compliance-path change is registry text inv4-compatibility.yaml. CI'straining-agent-storyboardsis the gate.Local hook
Committed with
HUSKY=0under the release coordinator's standing approval for #8501-line PRs that touch no server file. The hook's server-unit stage times out at this host's load, so it was skipped. CI is the gate. I ran the other hook steps by hand:npm run typecheckand the image check pass.npm run test:unitpassed 1281/1284. The 3 misses were 10s load timeouts inaddie/compliance-validate-input-gatesandbilling/stripe-client, which this PR doesn't touch, and those files pass 69/69 on their own.🤖 Generated with Claude Code