docs: fix dead link and anchors, tidy TikTok image filenames

[CodeFire98]

Rebased onto main (ad5f9cb). Fixes one genuinely broken link and two dead anchors, plus some link/filename hygiene.

Correction to the original framing

I opened this claiming it fixed "29 broken links." That count was wrong, and the reason is worth knowing.

This repo's node_modules has mintlify 4.0.592 pinned, while npx mintlify pulls 4.2.800. They disagree badly:

Checker	Result on main
4.0.592 (repo's node_modules)	29 broken links
4.2.800 (npx, current)	1 broken link

4.0.592 false-positives on percent-encoded image paths and on any path that resolves through a docs.json redirect. I verified each case by hand against docs.json and the target headings rather than trusting either tool. Only 3 links were actually doing the wrong thing.

package.json declares "mintlify": "latest", so whoever installed last froze an old version into the lockfile. Worth a separate bump.

Actually broken

• features/mcp.mdx — /api-reference/introduction 404s. No such page, no redirect covering it. Now points at /api-reference/data-apis, which matches the link text ("Linkrunner data API").
• sdk/expo.mdx, sdk/flutter.mdx — /sdk/android/installation#backup-configuration. The path redirects fine, but #backup-configuration does not exist in sdk/android.mdx; the heading is ### Step 3: Backup Configuration. So the link silently dumped you at the top of the Android page. Now /sdk/android#step-3%3A-backup-configuration, matching how features/remarketing.mdx, features/remarketing-guide.mdx, and testing/integration-testing.mdx already write that same anchor.

Not broken, cleaned up anyway

• features/deferred-deep-linking.mdx — the five /sdk/<platform>/usage#getting-attribution-data links resolve via redirects in docs.json, and the fragment survives the hop. Pointed directly at /sdk/<platform>#getting-attribution-data to drop the redirect.
• features/skadnetwork-conversion-values.mdx — /sdk/skadnetwork/integration likewise redirects to /features/skadnetwork-integration. Now direct.
• TikTok screenshots — the files were never missing. They were named image NN.png with a literal space, referenced as %20, which percent-decodes correctly and works in production. Renamed to image-NN.png per the lowercase-hyphens rule in CLAUDE.md, since spaces in asset filenames are a trap waiting to spring. No screenshots need recapturing.

Verification

• npx mintlify broken-links (4.2.800) → no broken links found
• npm run check:routes → 86 pages, no unredirected removals

Caveat worth knowing: mintlify broken-links validates paths but not anchors, in either version. I confirmed this by pointing a link at a deliberately bogus anchor and the check still passed. That is exactly why the #backup-configuration bug survived this long. So every anchor here was checked by hand against the heading in the target file:

• ## Getting Attribution Data exists in sdk/android.mdx, sdk/ios.mdx, sdk/react-native.mdx, sdk/flutter.mdx
• ### Step 3: Backup Configuration exists in sdk/android.mdx:59

No overlap with #185 — that PR touches docs.json and features/{users,events}-tab.mdx, none of which this one changes. They can merge in either order.

🤖 Generated with Claude Code