fix(cli): gracefully exit when user declines to fork session from another project

When --resume <session-id> targets a session in a different project,
the CLI prompts whether to fork into the current directory. If the
user answers 'n', the previous code threw an uncaught Error that
bubbled up as an ugly stack trace.

Instead, return undefined from createSessionManager and handle it in
runRootCommand by printing a dimmed message and returning cleanly.

Fixes the uncaught exception:
  Error: Session "..." is in another project (C:\tmp).
  at createSessionManager (.../main.ts:407:16)

Author: oldschoola

packages/coding-agent/src/main.ts

@@ -412,7 +412,7 @@ async function createSessionManager(
 			if (normalizedCwd !== normalizedMatchCwd) {
 				const shouldFork = await promptForkSession(match.session);
 				if (!shouldFork) {
-					throw new Error(`Session "${sessionArg}" is in another project (${match.session.cwd}).`);
+					return undefined;
 				}
 				return await SessionManager.forkFrom(match.session.path, cwd, parsed.sessionDir);
 			}
@@ -852,7 +852,12 @@ export async function runRootCommand(
 		cwd,
 		settingsInstance,
 	);
-
+	// User declined to fork a session from another project — exit gracefully
+	if (typeof parsedArgs.resume === "string" && !sessionManager) {
+		process.stdout.write(`${chalk.dim(`Resume cancelled: session is in another project.`)}
+`);
+		return;
+	}
 	// Handle --resume (no value): show session picker
 	if (parsedArgs.resume === true && !parsedArgs.fork) {
 		const sessions = await logger.time("SessionManager.list", SessionManager.list, cwd, parsedArgs.sessionDir);