Mintlify commit backfills

[harryyiump]

Summary

Backfills 40 commits from the old Nextra docs repo (May 28 - June 18, 2026) into the Mintlify docs repo, preserving original authors and chronological order.

Changes

This PR brings the Mintlify repo up to date with recent documentation changes from the Nextra repo, including:

• New Mixpanel AI features (agent, MCP, headless mode)
• Audit log enhancements (NDJSON export, reference page reorganization)
• SDK documentation updates (Flutter, React Native, Session Replay)
• Feature flag and experiment improvements
• Various bug fixes and content updates

Migration Adaptations

All commits were adapted for Mintlify's framework:

• Converted Nextra components → Mintlify / components
• Translated navigation from _meta.tsx → docs.json entries
• Updated file paths (pages/docs/ → docs/)
• Fixed internal links and icon references for Mintlify structure
• Adapted component syntax where needed

Applied: 40 commits (30 cherry-pick, 10 manual)
Skipped: 6 commits (Nextra-only files: .npmrc, middleware.ts)

Review Notes

Key areas to spot-check:

• Mixpanel AI section pages (syntax conversions)
• Audit log pages (link updates)
• Experiments/feature flags pages (callout conversions)
• Navigation structure in docs.json

[greptile-apps]

Confidence Score: 4/5

Safe to merge with the RudderStack snippet fix — the double-prefix bug would propagate incorrect identity data to any user following that integration guide.

The RudderStack integration snippet in javascript-replay.mdx introduces a code bug: on every page load after the first, rudderAnonymousId holds the already-prefixed ID, causing $device_id and $distinct_id to be registered with incorrect values. All other changes are documentation content additions that look correct.

docs/tracking-methods/sdks/javascript/javascript-replay.mdx (RudderStack identity snippet)

Important Files Changed

Filename	Overview
docs/tracking-methods/sdks/javascript/javascript-replay.mdx	Adds Data Residency section and updates the RudderStack integration snippet, but the idempotency guard introduces a double-prefix bug on repeat page loads.
docs/mcp.mdx	Adds comprehensive Service Account authentication section alongside the existing OAuth flows; content looks correct and well-structured.
openapi/feature-flags.openapi.yaml	Refactored to reference external $ref files under openapi/common/ which do not exist in the repo; also adds ServiceAccount auth and ProjectId parameter — previously flagged in review.
docs.json	Adds audit-log-reference to nav, headless guide to Empower Your Team, a new top-level MIXPANEL AI group, and a spark→mixpanel-agent redirect — previously flagged duplicate nav entries remain.
docs/access-security/audit-log-reference.mdx	New reference page cataloguing all audit log event types; content is well-organized and no issues found.
docs/mixpanel-agent.mdx	Removes beta notice and cleans up security/privacy section; FAQ numbering skips from 3 to 5.
guides/guides-by-use-case/empower-your-team/headless.mdx	New guide for Mixpanel Headless SDK; content is clear and correctly uses Mintlify components.
docs/orgs-and-projects/organizations.mdx	Rewrites the Delete Organization section with clearer steps and callouts; uses an absolute URL for an internal link that should be relative.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User opens page] --> B{rudderAnonymousId starts with '$device:'?}
    B -- No / First load --> C[setAnonymousId '$device:' + rawId]
    C --> D[register rawId as $device_id]
    B -- Yes / Repeat load --> E[Skip setAnonymousId guard fires]
    E --> F[register PREFIXED ID as $device_id and double-prefix distinct_id]
    D --> G[Correct identity in Mixpanel]
    F --> H[Broken identity in Mixpanel]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[User opens page] --> B{rudderAnonymousId starts with '$device:'?}
    B -- No / First load --> C[setAnonymousId '$device:' + rawId]
    C --> D[register rawId as $device_id]
    B -- Yes / Repeat load --> E[Skip setAnonymousId guard fires]
    E --> F[register PREFIXED ID as $device_id and double-prefix distinct_id]
    D --> G[Correct identity in Mixpanel]
    F --> H[Broken identity in Mixpanel]

Loading

_{Reviews (3): Last reviewed commit: "Update flutter-replay.mdx" | Re-trigger Greptile}

[greptile-apps]

Broken external $ref paths — openapi/common/ does not exist

The refactored YAML now references ./common/feature-flags-api.yaml, ./common/responses.yaml, and ./common/securitySchemes.yaml, but the openapi/common/ directory is not present in the repository. Every resolver that processes this spec (Mintlify, redocly lint, swagger-ui, CI validation) will fail with "reference not found" errors, making the API reference page un-renderable. The referenced files need to be added alongside this change.

[greptile-apps]

Duplicate navigation entries

The new top-level "MIXPANEL AI" group lists mixpanel-agent, mcp, mcp/mcp-by-industry, mcp/integrations, and headless, but all five of these paths are already registered under the "Empower Your Team" nested section (lines 596–621). Mintlify may render the same pages in both sidebar locations or silently dedup them; either way the intent is unclear. If this is meant to be a standalone top-level shortcut group, the sub-page nesting (mcp/mcp-by-industry and mcp/integrations) inside a flat list is also inconsistent with how the rest of the navigation is structured.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!