🤖 fix: initialize ORPCProvider in connected state when client prop provided

Fixes Storybook tests failing in CI. When a client prop is passed to
ORPCProvider, the component now starts in "connected" state immediately
instead of waiting for useEffect. This prevents a flash of null content
that caused tests to see an empty storybook-root div.

Change-Id: I048104e7f2fe434efcf9b50db0bae445d912b014
Signed-off-by: Thomas Kosiewski <tk@coder.com>

Author: ThomasK33

src/browser/orpc/react.tsx

@@ -70,7 +70,16 @@ function createBrowserClient(authToken: string | null): {
 }
 
 export const ORPCProvider = (props: ORPCProviderProps) => {
-  const [state, setState] = useState<ConnectionState>({ status: "connecting" });
+  // If client is provided externally, start in connected state immediately
+  // This avoids a flash of null content on first render
+  const [state, setState] = useState<ConnectionState>(() => {
+    if (props.client) {
+      // Also set the global client reference immediately
+      window.__ORPC_CLIENT__ = props.client;
+      return { status: "connected", client: props.client, cleanup: () => undefined };
+    }
+    return { status: "connecting" };
+  });
   const [authToken, setAuthToken] = useState<string | null>(() => {
     // Check URL param first, then localStorage
     const urlParams = new URLSearchParams(window.location.search);