feat(core): add nx cloud connect flow to the tui performance report

## Current Behavior

The TUI performance report shows run stats but no way to act on the remote-cache
recommendation. Connecting means quitting the run and running `nx connect`.

## Expected Behavior

- While the workspace is not connected, the performance report footer offers
  `enable remote cache: <shift>+c` (clickable). Pressing it runs `nx connect`
  logic headlessly and shows the onboarding URL inline under the stats, so the
  whole flow stays in the TUI.
- The browser is never opened automatically: `o` (or a click on the link) opens
  the URL; the report stays open. `<shift>+c` retries after a failure.
- A missing VCS remote does not block: the URL is generated anyway and the
  report nudges to https://github.com/new (Nx Cloud covers VCS in the browser).
- The connect experience is a reusable `ConnectFlow` component that owns its own
  lifecycle state and rendering; the report embeds it and forwards keys via a
  small intent enum. Other popups can embed it later without touching the report.
- Its state lives in `TuiState` so it survives F11 mode switches. The URL is a
  registry-backed clickable link, not OSC 8 (which breaks ratatui layout).
- Connection crosses napi as the constructor's existing optional bool:
  undefined = cloud off, true = connected, false = not connected.

## Related Issue(s)

NXC-4701

Author: jaysoo

packages/nx/src/command-line/nx-cloud/connect/connect-to-nx-cloud.ts

@@ -242,6 +242,69 @@ function sleep(ms: number) {
   return new Promise((resolve) => setTimeout(resolve, ms));
 }
 
+export interface TuiConnectResult {
+  /** The onboarding URL to open in the browser. */
+  url: string;
+  /**
+   * True when the workspace has no VCS remote yet. The browser onboarding
+   * still works (and covers VCS itself), so this only lets the TUI nudge the
+   * user rather than block them.
+   */
+  needsVcsPush: boolean;
+}
+
+/**
+ * Runs the same logic as `nx connect` headlessly for the TUI: no prompts, no
+ * spinner, no browser open (the TUI displays the returned onboarding URL in a
+ * popup instead). Rejects when the workspace cannot be created (e.g. the
+ * create-org API is unreachable) so the TUI can surface the error; note the
+ * already-connected branch resolves with a fallback URL even offline. A missing
+ * VCS remote is not a failure - it comes back as `needsVcsPush`.
+ */
+export async function connectToNxCloudFromTui(): Promise<TuiConnectResult> {
+  return withConnectStats(
+    connectStatMeta({ source: 'nx-tui' }),
+    () => true,
+    () => generateConnectUrlForTui()
+  );
+}
+
+async function generateConnectUrlForTui(): Promise<TuiConnectResult> {
+  const nxJson = readNxJson();
+  // A missing remote does not block the TUI: the browser flow walks the user
+  // through pushing to a VCS provider, so we generate the URL regardless and
+  // let the popup surface the nudge.
+  const needsVcsPush = !getVcsRemoteInfo();
+
+  // The connect shortcut is only offered while not connected, but guard anyway
+  // (e.g. the workspace was connected from another terminal mid-run).
+  if (isNxCloudUsed(nxJson)) {
+    const token =
+      process.env.NX_CLOUD_AUTH_TOKEN ||
+      process.env.NX_CLOUD_ACCESS_TOKEN ||
+      nxJson.nxCloudAccessToken ||
+      nxJson.nxCloudId;
+    const url = await createNxCloudOnboardingURL(
+      'nx-tui',
+      token,
+      undefined,
+      false
+    );
+    return { url, needsVcsPush };
+  }
+
+  const token = await connectWorkspaceToCloud({
+    installationSource: 'nx-tui',
+  });
+  const url = await createNxCloudOnboardingURL(
+    'nx-tui',
+    token,
+    undefined,
+    false
+  );
+  return { url, needsVcsPush };
+}
+
 export async function connectExistingRepoToNxCloudPrompt(
   command = 'init',
   key: MessageKey = 'setupNxCloud',

packages/nx/src/native/index.d.ts

@@ -32,7 +32,7 @@ export declare class ExternalObject<T> {
   }
 }
 export declare class AppLifeCycle {
-  constructor(tasks: Array<Task>, initiatingTasks: Array<string>, runMode: RunMode, pinnedTasks: Array<string>, tuiCliArgs: TuiCliArgs, tuiConfig: TuiConfig, titleText: string, workspaceRoot: string, taskGraph: TaskGraph, isCloudEnabled?: boolean | undefined | null)
+  constructor(tasks: Array<Task>, initiatingTasks: Array<string>, runMode: RunMode, pinnedTasks: Array<string>, tuiCliArgs: TuiCliArgs, tuiConfig: TuiConfig, titleText: string, workspaceRoot: string, taskGraph: TaskGraph, isConnectedToCloud?: boolean | undefined | null)
   startCommand(threadCount?: number | undefined | null): void
   scheduleTask(task: Task): void
   startTasks(tasks: Array<Task>, metadata: object): void
@@ -57,6 +57,25 @@ export declare class AppLifeCycle {
    * Cloud client can call it via the lifecycle it already receives.
    */
   setCloudLink(label: string, url: string): void
+  /**
+   * Register the callback fired when the user presses the connect-to-cloud
+   * shortcut. JS runs the `nx connect` logic and pushes the resulting URL
+   * back via `setConnectUrl` / `setConnectError`.
+   */
+  registerConnectToCloudCallback(connectCallback: (() => unknown)): void
+  /**
+   * Deliver the Nx Cloud onboarding URL to the connect flow. `needsVcsPush`
+   * is true when the workspace has no VCS remote yet, so the popup can nudge
+   * the user to create one (the browser flow still works either way).
+   */
+  setConnectUrl(url: string, needsVcsPush: boolean): void
+  /** Surface a connect failure in the connect flow. */
+  setConnectError(message: string): void
+  /**
+   * Mark the workspace as connected, once a TUI-initiated connect has
+   * written an nxCloudId to nx.json.
+   */
+  setConnectedToCloud(): void
 }
 
 export declare class ChildProcess {