[ukimsanov]

What

Turns on Mintlify's built-in PostHog integration for the docs, using the Hyperframes PostHog project (the same public key hyperframes.dev uses in demo-next/src/lib/posthogConfig.ts). Session recording is off.

Why

We can't see how people reach the docs or where they go next:

• The landing page (hyperframes.heygen.com/) reports to HeyGen Prod: 253,791 pageviews in the last 28 days, 356 of them referred by AI chats (Perplexity 255, ChatGPT 42, Gemini/Copilot 41, Claude 18).
• The docs pages report nowhere: 0 docs pageviews in any PostHog project. Mintlify's own analytics has views, visitors, searches and assistant questions, but no referrers.
• So we can't measure AI-chat referrals to docs pages, the main AEO number. Nor can we measure docs → Studio download: studio_download_started already lives in the Hyperframes project, so the docs pageviews belong there too.

Volume: about 190k docs pageviews a week, against about 21M cli_command events a week already in this project (under 1% more).

No visible change

Analytics only.

Test plan

• mint validate
• After deploy: $pageview events with $host = hyperframes.heygen.com and a docs path appear in the Hyperframes project

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Oct 21, 2026, 11:28 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[jrusso1020]

docs/docs.json:1290–1296 uses Mintlify’s supported integrations.posthog configuration, matches the existing public HyperFrames project key, and explicitly sets sessionRecording: false. The public capture key is not a private API credential. Configuration semantics checked against Mintlify’s official documentation.

Isolated exact-source controls checked the key and replay setting; no deployed pageview, PostHog delivery or Mintlify build was exercised. The change does not establish a broader guarantee that standard pageview URL properties contain no user-supplied data.

Verdict: COMMENT
Reasoning: No code blocker found in this configuration change. GitHub approval needs James’s go or a trusted stamper’s request.
— hf-review

[jrusso1020]

Approval at exact head 4a60a2ef302bce7e4d1a246ae3e535c73074f18a, unchanged since my code review. James directly authorized approval in the originating Slack thread; no new code findings were added in the refreshed review/comment history.

Mintlify PostHog configuration uses the expected public capture key and explicitly disables session recording. Official configuration semantics were checked.

Validation and limits: Exact configuration controls; no deployed analytics delivery or Mintlify build. Standard pageview URL collection is outside this setting change.

Verdict: APPROVE
Reasoning: The reviewed code remains clear under the stated scope and collection contract; earlier blocking findings are resolved where applicable. No merge, deployment or publication performed by me.
— hf-review