fix(marketing): connect Grok discovery pages to setup

[leoisadev1]

Problem

The homepage did not connect Grok search intent directly to the existing discovery and setup pages. The open-source page needed concrete product context and a practical next step without implying that self-hosting includes model access or keeps prompts offline.

Changes

Link the homepage to Grok discovery and setup, expand the open-source page with a labeled demonstration screenshot and provider/privacy/cost answers, and add a cautious read-only first-task walkthrough. Refresh the three affected sitemap dates and cover the discovery-to-setup path in SEO tests.

Verification

• All 10 focused marketing SEO tests passed.
• Targeted lint passed; marketing Astro typecheck reported no errors or warnings; marketing production build passed.
• The primary agent verified both repaired pages at 1440×1000 and 390×844, including the first-task link, guide return link, corrected provider instructions, default storage wording, inline spacing, and absence of horizontal overflow. No UI changes were made after that pass.
• Greptile's two accuracy findings were fixed in both discovery and setup pages, with regression assertions for default storage wording and removal of the obsolete Subscriptions heading.
• Leo explicitly waived PR screenshot/attachment evidence for this change.
• Marketing-only change: application web/desktop/native-mobile entry points, provider runtimes, wire contracts, and connection modes are unchanged.

Implemented through the primary-agent workflow; PR preparation and verification by Grok in the Grok agent harness.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
akeru-bot-landing	Building	Preview	Sep 8, 2026 3:25am UTC

[greptile-apps]

Greptile Summary

This PR improves Grok-oriented discovery and setup guidance, including provider navigation, provider-cost boundaries, and default local storage behavior.

Confidence Score: 5/5

Safe to merge.

No outstanding issues remain. greptile-apps[bot] resolved both earlier documentation threads without explanation.

_{Reviews (2): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile}