Allow tcpConnectionToken when cliUrl is set (Node + Go)

CliUrl/CLIUrl always implies TCP mode (it overrides useStdio/UseStdio
internally), so rejecting the token when useStdio: true is set should
only fire when no cliUrl is provided. Brings Node and Go in line with
the .NET behavior.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: SteveSandersonMS

go/client.go

@@ -171,8 +171,9 @@ func NewClient(options *ClientOptions) *Client {
 			panic("GitHubToken and UseLoggedInUser cannot be used with CLIUrl (external server manages its own auth)")
 		}
 
-		// Validate token vs stdio
-		if options.TCPConnectionToken != "" && options.UseStdio != nil && *options.UseStdio {
+		// Validate token vs stdio. CLIUrl always implies TCP mode (it overrides UseStdio
+		// below), so only reject the token when stdio is actually going to be used.
+		if options.TCPConnectionToken != "" && options.UseStdio != nil && *options.UseStdio && options.CLIUrl == "" {
 			panic("TCPConnectionToken cannot be used with UseStdio: true")
 		}
 

nodejs/src/client.ts

@@ -331,7 +331,7 @@ export class CopilotClient {
             ) {
                 throw new Error("tcpConnectionToken must be a non-empty string");
             }
-            if (options.useStdio === true) {
+            if (options.useStdio === true && !options.cliUrl) {
                 throw new Error("tcpConnectionToken cannot be used with useStdio: true");
             }
         }