[bokelley]

PR #8703 grouped an optional protocol capability with conformance harness fixes in one minor changeset. Split the capability into its own minor changeset and classify the harness fixes as patch, so maintenance releases can select harness changes without adding a stable schema field.

Add a short applicability note to the provenance enforcement narrative: creative.supports_provenance starts in AdCP 3.3, a creative library alone does not establish support, and responses on earlier releases cannot advertise this declaration. Runtime behavior and wire schemas are unchanged by this PR.

Validation:

• Changeset protocol scope check and release status pass; the combined main release remains minor.
• 107 focused source/contract tests pass.
• Normal pre-commit checks pass, including root and server tests.

This PR is a prerequisite for a selective 3.1 harness backport. It does not promote a candidate release, publish artifacts, or alter historical release files.

---

Open workspace in Conductor

[aao-secretariat]

Ladon verdict: Approve

Approve — clean release-bookkeeping PR, no blocking or medium findings.

Checked:

• Changeset scope/type: Splits the wire-adding creative.supports_provenance capability out of PR #8703's combined changeset into its own minor changeset; harness-only fixes reclassified as patch. Net main-line bump stays minor, so the schema field in get-adcp-capabilities-response.json remains covered — no untracked wire change.
• Schema↔docs coherence: No schema source modified (no oneOf/docs-coherence exposure). The provenance_enforcement.yaml narrative note ("introduced in AdCP 3.3") is accurate against the field's schema presence and the repo's 3.3.0-beta.3 version.
• Release line: Base is main, not 3.1.x; no breaking change, no artifact immutability concern.

No findings. high_risk false; gated_paths false. review_decision is REVIEW_REQUIRED, but gated_paths is false so row 2 does not fire. No author team gate. Falls through to row 9.