ENG-9567 docs: link AI onboarding guide from installation page

[FarhanAliRaza]

Agents typically hit the installation page first, so the agent alert now points them at the AI onboarding guide via its .md URL, which they can fetch directly as Markdown.

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

Please delete options that are not relevant.

• This change requires a documentation update

[greptile-apps]

Greptile Summary

This PR adds a single bullet to the AI agent alert block on the installation page, pointing agents at the AI onboarding guide (https://reflex.dev/docs/ai/integrations/ai-onboarding.md) as the first action to take. The linked page is live and the .md suffix pattern for direct Markdown access is correct.

• Adds the onboarding guide link as the first item in the agent tip list, before the llms.txt and MCP server bullets, so agents get a single comprehensive starting point before following more specific links.

Confidence Score: 5/5

A one-line documentation addition to the agent alert block; the linked URL is live and the Markdown suffix pattern is consistent with how all other Reflex docs pages work.

The only change is inserting a new bullet that links to a verified, existing page. There is no code logic, no behavioral change, and no risk of regression.

No files require special attention.

Important Files Changed

Filename	Overview
docs/getting_started/installation.md	Adds a new bullet at the top of the agent alert pointing to the AI onboarding guide via its .md URL; the linked page exists and the URL pattern is correct.

_{Reviews (1): Last reviewed commit: "docs: link AI onboarding guide from inst..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 26 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing FarhanAliRaza:farhan/eng-9567-add-ai-onboarding-to-reflex-installation-docs (2b6aaa5) with main (34ee005)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩