docs: framework Connect guides, reachable SDK nav, "Start the server"

[yuvrxj-afk]

Follow-up to #1209 (stacked on it — the Corsair Connect docs it adds are the base for this). Retarget to main once #1209 merges.

Framework guides — a Corsair Connect example in the Next, Remix, and TanStack guides, each wired to that framework's own refresh:

• Next → router.refresh()
• Remix → useRevalidator().revalidate() (provider in app/root.tsx)
• TanStack → router.invalidate() (provider in the root route)

Each notes that the <CorsairBoundary> read helper is Next-RSC-specific — Remix and TanStack read in loaders, so there call and connect are the surfaces that apply.

Reachability — the SDK reference pages (adapters/handlers, adapters/client, adapters/react) were orphaned (not in the sidebar), which hid Corsair Connect. Added them under a collapsible SDK group in Reference.

Boundary note — <CorsairBoundary> reads provider context and throws without a <CorsairProvider> ancestor; the docs now say so.

"Go green" → "Start the server" across the framework + handler guides. The body still points at the App-sync dot as the success signal.

Docs-only. docs.json validated as JSON; every new link resolves.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
www	Ready	Preview	Aug 31, 2026 2:37pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 89b2f326-297c-4e3b-ae65-a5bad3e3d903

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

This docs-only PR expands Corsair Connect guidance and improves reference-page discoverability.

• Adds framework-specific post-connect refresh examples for Next.js, Remix, and TanStack Start.
• Adds the handler, vanilla client, and React adapter pages to an SDK navigation group.
• Documents the CorsairBoundary provider requirement and consistently renames setup sections to “Start the server.”

Confidence Score: 5/5

The documentation changes appear safe to merge, with no concrete incorrect or unreachable guidance established.

The added framework refresh callbacks match the provider contract, the SDK navigation entries target existing pages, and the remaining edits are consistent terminology and provider-context clarification.

Important Files Changed

Filename	Overview
docs/frameworks/next.mdx	Adds a CorsairProvider example that refreshes Next.js Server Component reads after connection.
docs/frameworks/remix.mdx	Adds root-provider guidance using Remix loader revalidation after connection.
docs/frameworks/tanstack.mdx	Adds root-provider guidance using TanStack Router invalidation after connection.
docs/adapters/react.mdx	Clarifies that CorsairBoundary requires a CorsairProvider ancestor.
docs/docs.json	Makes the handler, client, and React adapter references reachable through a new SDK group.

_{Reviews (1): Last reviewed commit: "docs: framework Connect guides, reachabl..." | Re-trigger Greptile}