[gewenyu99]

💡 Motivation and Context

We have a wave of breaking changes with new major versions for most SDKs. References are now read mostly by bots, not humans, and the HogRef format is heavy. This is part of the stack below.

• Commits posthog-ios-4.md and posthog-ios-migration.md, generated from feat/v4-capture-v1.
• The capability tags need to land on that branch before the page can be regenerated there.

💚 How did you test it?

• Every generated page compiles under posthog.com's MDX 1 check.

📝 Checklist

• All commits are signed
• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Claude Code: Sonnet 5.5 built it and Opus 5.5 opened it, directed by Vincent. Not yet reviewed line by line.

Merge order

• docs: generate the SDK reference as Markdown with DocC #1030 docs: generate the SDK reference as Markdown with DocC
• docs: tag public methods with their sdk-specs capability #1031 docs: tag public methods with their sdk-specs capability
• docs: generate the iOS SDK 3.x and experimental 4.x references #1032 docs: generate the iOS SDK 3.x reference
• docs: generate the experimental iOS SDK 4.x reference #1033 docs: generate the experimental iOS SDK 4.x reference (this PR)
• Then PostHog/squeak-strapi adds this SDK to its sync, and PostHog/posthog.com adds the nav entries

🤖 Generated with Claude Code

[gewenyu99]

Folded into #1032, so each SDK is two PRs: the code, then the generated pages.