feat(reporting): extend reporting-frequency for measured channels; surface print guide in nav

[bokelley]

Summary

Two small, additive changes that measured/physical channels (OOH, radio, print) sit on, converged in review on #6138 and #6140:

• reporting-frequency gains weekly, quarterly, post_campaign. These are the publication cadences of audience-currency channels: weekly OOH/radio increments (Geopath, RAJAR), quarterly measurement-cycle updates (Geopath DEC), and flights only reconcilable in arrears. The enum description and optimization-reporting docs now state the eligibility principle from the [Scoping] Radio & static OOH: bring channel measurement + delivery to linear-TV parity #6138 thread: a product's declared cadence gates mid-flight optimization — nothing should optimize against data that arrives quarterly.
• docs/creative/channels/print is added to navigation (plus the matching snapshot redirect). The page has shipped since the collection/installment work (feat: collection/installment model, deadlines, and print channel support #1642) but has never been reachable from docs.json nav.

Doc value lists (update_media_buy, get_media_buy_delivery, optimization-reporting) updated to match the enum. Changeset included (minor).

Notes

• Purely additive; no existing value or behavior changes.
• The MUST-level normative sentence proposed on [Scoping] Radio & static OOH: bring channel measurement + delivery to linear-TV parity #6138 (cadence as optimization-eligibility gate) is expressed here as guidance prose; promoting it to a normative statement can ride the WG review of the static-OOH channel work (Static OOH: measurement shape + proof-of-posting (the no-play-event channel) #6140, spec draft in docs(specs): static OOH draft proposal #6146).

Refs #6138, #6140

🤖 Generated with Claude Code

[aao-secretariat]

Ladon verdict: Escalate to human review

Escalate — gated path requires human/CODEOWNERS review.

This PR extends the shared reporting-frequency enum with weekly, quarterly, and post_campaign, updates the three normative docs listings coherently, and ships a correct minor changeset. The reviewer found the schema↔docs coherence intact (all three consuming schemas $ref the shared enum), no released dist/** artifacts touched, and no blocking findings.

However, static/schemas/source/enums/reporting-frequency.json matches the deterministic gated-path glob static/schemas/source/** (gated_paths: true), and review_decision is REVIEW_REQUIRED — not APPROVED. Per decision-table row 2, this PR cannot be auto-approved and must go to human/CODEOWNERS review.

Escalation reasons

• static/schemas/source/enums/reporting-frequency.json is under the hard approval gate (static/schemas/source/**) and review_decision is REVIEW_REQUIRED; a real human/CODEOWNERS approval is required before merge.

No blocking findings exist; the diff is clean and additive. Once a CODEOWNERS approval lands, this can fall through to approve.

Why human review

• static/schemas/source/enums/reporting-frequency.json is under the hard approval gate (static/schemas/source/**) and 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/enums/reporting-frequency.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.