docs: document creative format discovery deprecation

[gagliathebuilder]

Summary

• Documents the AdCP 3.2 deprecation posture for list_creative_formats as a new-discovery surface
• Redirects sales agents to get_products.format_options[] and creative agents to get_adcp_capabilities.creative.supported_formats
• Clarifies list_creatives remains the creative-library query task and is not deprecated
• Preserves v1 format_id / format_ids[] support through 4.x
• Relaxes conformance/compliance so migrated 3.2 agents are not failed for omitting list_creative_formats when equivalent canonical discovery is declared
• Adds patch changeset for adcontextprotocol

Closes #5779

Test plan

• Consistency search: no unconditional MUST for list_creative_formats; no list_creatives deprecation; no hard required_tools forcing the tool for migrated agents (pagination storyboard exception intentional)
• Validation:
  • npm run test:storyboard-scoping
  • npm run test:storyboard-check-enum
  • npm run test:storyboard-contradictions
  • npm run test:compliance-source-authority
  • npm run test:docs-nav
  • npm run check:seo (passed with pre-existing description-length warnings only)
  • npm run test:storyboard-sample-request-schema
  • npm run test:pagination-invariant
• Review MDX + compliance YAML + changeset together for atomic posture

Made with Cursor

[aao-secretariat]

Argus is not auto-reviewing this PR because it modifies protected paths that require human review (.changeset/creative-format-discovery-deprecation-posture.md). A human reviewer should review and merge this PR; Argus will resume on subsequent PRs once these changes land on main.

[gagliathebuilder]

Thanks — this should be ready for human review.

Argus skipped auto-review because this touches the changeset path, so I’d appreciate a look at the MDX, compliance YAML, and changeset together.

The main thing I’m trying to make sure is consistent across the PR:

• list_creative_formats is deprecated as the new-discovery path in 3.2+
• sales agents should use get_products.format_options[]
• creative agents should use get_adcp_capabilities.creative.supported_formats
• list_creatives remains the creative-library query task and is not deprecated
• v1 format_id / format_ids[] support remains through 4.x
• migrated 3.2 agents shouldn’t fail conformance for omitting list_creative_formats when they declare equivalent canonical discovery

Happy to adjust wording if there’s a better way to phrase the posture.

[bokelley]

Reviewed MDX + compliance YAML + changeset together. All 6 claims are consistent across the PR:

Claim	Coverage
list_creative_formats deprecated for new discovery in 3.2+	Warning block in list_creative_formats.mdx, specification.mdx conformance §, release-notes.mdx 3.2 section, changeset body
Sales agents → get_products.format_options[]	implementing-creative-agents.mdx tables, specification.mdx conformance item 2, warning block, release notes
Creative agents → get_adcp_capabilities.creative.supported_formats	Same — all three surfaces call out both roles correctly
list_creatives not deprecated	Explicitly repeated in specification.mdx (×2), implementing-creative-agents.mdx checklist, list_creative_formats.mdx warning, release notes "Not deprecated" block
v1 format_id / format_ids[] through 4.x	specification.mdx trailing note, list_creative_formats.mdx warning, release notes, changeset body, canonical-formats-migration.mdx calendar
Migrated 3.2 agents grade not_applicable, not fail	requires_tool: list_creative_formats added to every list_creative_formats step across 13 storyboard files; required_tools emptied on creative/index.yaml and creative-generative/generative-seller.yaml

One nit — specification.mdx line ~455, consumer conformance item 5 reads:

A conformant Creative Protocol consumer MUST: … 5. MUST NOT assume list_creative_formats is present …

The capitalized MUST NOT inside a MUST: list is a double modal. Suggest either:

-5. MUST NOT assume `list_creative_formats` is present on 3.2+ agents when equivalent …
+5. Not assume `list_creative_formats` is present on 3.2+ agents when equivalent …

or pull it out as a standalone normative paragraph. Up to you — minor wording only, not a blocker.

Everything else is internally consistent. The changeset as patch is appropriate — requires_tool on existing steps is a permissive conformance softening (not a new step kind or schema bump), and the "Version 3.2.0 / Status: In development" framing in release notes is correctly qualified.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_01CeevtBhDTNpS1HzG6fk3fo

---

Generated by Claude Code

[aao-secretariat]

Argus is not auto-reviewing this PR because it modifies protected paths that require human review (.changeset/creative-format-discovery-deprecation-posture.md). A human reviewer should review and merge this PR; Argus will resume on subsequent PRs once these changes land on main.

[gagliathebuilder]

Thanks — appreciate the review. I made the small double-modal wording fix in specification.mdx and left the rest unchanged.