Add "How Fern uses AI" cross-product page

[devin-ai-integration]

Summary

Adds a single customer-facing page that inventories every AI capability across Fern's products, for customers (and Fern's legal team, working through the updated Terms of Service) who need one place that answers: what AI runs, what it's for, which provider/model processes the data, what Fern stores, and how to turn it off.

New page: fern/products/home/pages/ai.mdx → published at /learn/home/ai, linked from the Home landing page CTA row and from the Docs AI overview intro. Changelog entry added under fern/products/docs/pages/changelog/.

Content is grounded in the platform/CLI source rather than in existing docs prose, and deliberately separates three categories that were previously blurred together:

• capabilities that call a model (Ask Fern and its Slack app, MCP server, search suggestions, AI-generated examples, Fern Writer, Ask Fern analytics, four dashboard capabilities, fern sdk-diff),
• features that are fully deterministic and involve no model call (llms.txt, Markdown access, agent directives, API catalog discovery, agent skills),
• ordinary SDK/docs generation, which is deterministic and is stated as such.

Two sections exist specifically for the legal review: a provider/model-family table per capability (Anthropic direct with Bedrock fallback, OpenAI-compatible gateway for embeddings), and a "Data Fern sends and stores" section covering what reaches a provider per capability, query persistence and the configurable 1–3650 day retention window, and the no-training statement. Claims are limited to what the source establishes — where a deployment mapping is ambiguous (the two registry AI-example Lambda implementations use different providers), the page says "depending on the generation path" rather than naming one.

Setup instructions are not duplicated: every capability row links to its existing canonical page.

Note on the URL: the page lives in the Home product, which resolves at /learn/home/... in the generated site. AGENTS.md states Home pages resolve at /learn/{page-slug}; that isn't what the CLI produces. Making /learn/ai work required a product-level slug override that broke /learn itself (redirect to /learn/home → 404), so this PR links /learn/home/ai and leaves routing alone. Worth fixing separately if the short URL matters.

Rendered locally at /learn/home/ai; all 18 internal links verified against the running preview; pre-commit (Vale) clean and fern check --warnings reports 0 errors.

Link to Devin session: https://app.devin.ai/sessions/bad46565be904b3b8be9c63da0241d38

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[github-actions]

🌿 Preview your docs: https://fern-preview-devin-1787598000-how-fern-uses-ai.docs.buildwithfern.com/learn

Here are the markdown pages you've updated:

• learn/docs/ai-features/overview
• learn/docs/changelog/2026/8/24
• learn/home/ai
• learn/home