Chrome-related setup now has a Nexus-owned landing surface instead of an inherited external CTA.

Keep browser setup messaging anchored on the Nexus domain.

• Use this page as the canonical customer-facing entry point.
• Link technical setup details from the docs page instead of raw vendor docs.
• Hide unsupported flows instead of pointing to non-owned onboarding.

Only replace operational Chrome flows once Nexus owns the corresponding runtime and auth pieces.

• Customer-facing text can be Nexus-owned now.
• Extension download and native-host specifics should move only with backend readiness.
• Do not ship fake browser onboarding paths.