ops(growth): run a measured non-video distribution pilot for the research report

## Context

The first original research asset is published through #5668/#5721: the Strait of Hormuz transit report has a stable URL, downloadable CSV/JSON, per-figure provenance, citation guidance, and a distribution brief. The remaining opportunity is distribution into places where researchers, journalists, practitioners, and agents already discover source-backed data.

This ticket is a small manual pilot. It does not send messages, publish posts, or create accounts automatically. Every external distribution action requires separate explicit approval from the repository owner.

## What to prepare

- Use the existing report and its distribution brief as the only source of claims.
- Prepare at most three target-specific drafts: one upstream or research courtesy note, one specialist trade or policy audience note, and one data or practitioner community post.
- Keep every draft anchored to the canonical report URL and the downloadable data, with the AIS undercount limitation stated plainly.
- Define bounded attribution for each approved channel using the existing content attribution contract. Preserve inbound UTM parameters and do not use the affiliate ref parameter for internal tracking.
- Record approval status, target audience, canonical URL, proposed tracking fields, and the eventual public URL/date if an action is approved.
- Feed discovery, citation, download, dashboard, methodology, API, MCP, and pricing outcomes into the next scorecard cycle.

## Acceptance criteria

- [ ] Three or fewer distribution drafts exist, each with a specific audience, one useful report claim, source attribution, limitation language, and a clear reason the report is relevant.
- [ ] No draft promises ranking, citation, traffic, or conversion outcomes and no draft uses paid links, link exchanges, mass outreach, or follower-growth language.
- [ ] No external message or post is sent without explicit approval; unapproved targets remain visibly pending.
- [ ] Approved actions, if any, are recorded with target, canonical URL, publication date, bounded attribution fields, and a public link.
- [ ] The measurement plan distinguishes report discovery, direct citations, qualified downloads, and product handoffs from undifferentiated pageviews or social reach.
- [ ] A 30-day review records what happened and recommends iterate, stop, or one follow-up report based on demand, indexation health, useful engagement, and credible product handoff.
- [ ] No video production or video distribution work is included in this ticket.

## References

- Published report: https://www.worldmonitor.app/research/strait-of-hormuz-transit-report-2026-07/
- Distribution brief: docs/research/reports/strait-of-hormuz-transit-report-2026-07/distribution-brief.md
- Review plan: docs/research/reports/strait-of-hormuz-transit-report-2026-07/30-day-review-plan.md
- Attribution contract: shared/content-attribution.ts

Start by reading docs/research/reports/strait-of-hormuz-transit-report-2026-07/distribution-brief.md and 30-day-review-plan.md, then review shared/content-attribution.ts. Prepare no more than three audience-specific drafts and a measurement record covering approval status, attribution, canonical URLs, and outcomes; done includes the bounded 30-day review and no unapproved external action.

Written by the indexing model from the issue text.