feat(schema): add DOOH structured selling-unit fields to placements

[garvitkaushik-123]

Summary

Implements #5537 — adds structured DOOH selling-unit metadata to placements so buyers can evaluate screen characteristics during product discovery.

• dooh_placement_attributes object on both placement.json and placement-definition.json with four optional fields:
  • slot_duration_seconds — duration of one ad slot
  • loop_duration_seconds — full loop rotation (canonical source, supersedes pricing-layer field)
  • screen_resolution — physical { width, height } in pixels
  • motion — full_motion, partial_motion, or static (new dooh-motion-type enum)
• identifiers[] array on both placement schemas — reuses the { type, value } pattern from property identifiers for DOOH venue_id, screen_id, openooh_venue_type, etc.
• dooh-motion-type.json enum — full_motion, partial_motion, static
• identifier-types.json title updated from "Property Identifier Types" to channel-neutral "Identifier Types"
• flat-rate-option.json loop_duration_seconds description updated with superseded note
• Docs — DOOH placement attributes section added to media-products.mdx

Design decisions

• Follows the existing channel-overlay pattern (video_placement_types, audio_distribution_types, etc.) — new fields sit alongside those in the same position
• additionalProperties: true on dooh_placement_attributes to allow future field additions without breaking changes
• identifiers[] is channel-neutral by design — reuses the same enum already used for property identifiers
• motion enum values align with industry conventions (OpenOOH/OAAA terminology)

Test plan

• All 4232 unit tests pass
• TypeScript typecheck passes
• Schema build (build:schemas) succeeds
• Verify DOOH placement example validates against updated schema

Closes #5537

[aao-release-bot]

⚠️ Argus review could not complete

The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.

View workflow run

_{This is an automated message from the Argus AI review workflow.}

[bokelley]

This contribution still appears directionally useful, but it has been idle since June and main plus the active 3.2 OOH work have moved substantially. Please confirm you want to continue and rebase/reconcile it with the current OOH contract. If there is no response by August 17, we will close it as stale; the work can be reopened when an implementer is ready to carry it.

[garvitkaushik-123]

Hey @bokelley — yep, still on this! Got sidetracked but I'm picking it back up now. I see main has moved quite a bit with the 3.2 OOH work and the static OOH draft (#6146) — will rebase and reconcile over the next few days. Should have it updated well before the 17th.

[garvitkaushik-123]

Rebased onto current main. No conflicts — the placement schema additions (identifiers[], dooh_placement_attributes) slot in after the social_placement_surfaces block that landed since June.

Reviewed the static OOH draft (#6146) — that work is architectural for classic/printed OOH and doesn't overlap with the DOOH selling-unit fields here. The dooh_placement_attributes pattern stays consistent with the existing channel-overlay approach (video_placement_types, audio_distribution_types, etc.).

No schema shape changes from the original — just a clean rebase. Ready for review whenever it makes sense in the 3.2 cycle.

[aao-secretariat]

Ladon verdict: Escalate to human review

Escalate — gated paths touched without required review approval.

This PR adds additive DOOH placement metadata: optional dooh_placement_attributes and identifiers[] on placement.json and placement-definition.json, a new closed dooh-motion-type enum, and a description-only supersession note on flat-rate-option.loop_duration_seconds. The reviewer classifies it as Normative/non-breaking with a correct minor changeset; schema/docs/tests cohere and identifier shapes match. No critical/high/medium findings were raised.

However, this PR modifies files under static/schemas/source/**, which are under a deterministic hard approval gate (gated_paths: true), and review_decision is REVIEW_REQUIRED — not APPROVED. Per decision table row 2, the gate is not satisfied and the outcome must be escalate. Human/CODEOWNERS review is required before merge.

Escalation reasons

• Touches gated schema-source files without required approval; human/CODEOWNERS review required.

Medium findings

• None.

Low (non-blocking)

• docs/media-buy/advanced-topics/pricing-models.mdx:469 — DOOH params not updated with supersession note (docs-coherence follow-up).

Why human review

• Modifies gated schema-source files (static/schemas/source/core/placement.json, placement-definition.json, enums/dooh-motion-type.json, enums/identifier-types.json, pricing-options/flat-rate-option.json) while review_decision is REVIEW_REQUIRED — human/CODEOWNERS approval required before merge.
• This PR touches a path under a hard, non-overridable approval gate (static/schemas/source/core/placement-definition.json (modified) matches static/schemas/source/**; static/schemas/source/core/placement.json (modified) matches static/schemas/source/**; static/schemas/source/enums/dooh-motion-type.json (added) matches static/schemas/source/**; static/schemas/source/enums/identifier-types.json (modified) matches static/schemas/source/**; static/schemas/source/pricing-options/flat-rate-option.json (modified) matches static/schemas/source/**) and the current GitHub review decision is 'REVIEW_REQUIRED', not APPROVED. This is a hard gate enforced in code — Ladon cannot auto-approve until a human/CODEOWNERS approval is recorded, regardless of how clean the diff is.

[bokelley]

Maintainer update pushed onto this branch.

Key changes:

• keeps effective format_options as the sole creative-acceptance authority; DOOH fields are inventory/scheduling facts
• defines publisher/product resolution, identifier union, and post-merge slot <= loop validation
• makes placement loop duration canonical and requires any legacy pricing copy to agree
• exposes the fields on the AdCP 3.2 canonical-placement / list_products path as well as the full placement schemas
• registers the motion enum and adds behavioral/schema coverage, including the exact canonical product path

Validation: schema build passed; placement catalog tests pass (20/20); expert protocol, implementation, and workflow reviews found no remaining blocker.