fix: use process.stdin.isTTY with dry-run bypass

guardNonInteractive uses isatty(0) which isn't mockable in tests
and has a different error message. Keep the original isTTY check
but add --dry-run bypass so dry-run works non-interactively.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: betegon

src/lib/init/wizard-runner.ts

@@ -25,7 +25,6 @@ import { formatBanner } from "../banner.js";
 import { CLI_VERSION } from "../constants.js";
 import { getAuthToken } from "../db/auth.js";
 import { terminalLink } from "../formatters/colors.js";
-import { guardNonInteractive } from "../mutate-command.js";
 import { getSentryBaseUrl } from "../sentry-urls.js";
 import { slugify } from "../utils.js";
 import {
@@ -326,11 +325,9 @@ async function preamble(
   yes: boolean,
   dryRun: boolean
 ): Promise<boolean> {
-  try {
-    guardNonInteractive({ yes, "dry-run": dryRun });
-  } catch (err) {
+  if (!(yes || dryRun || process.stdin.isTTY)) {
     process.stderr.write(
-      `Error: ${err instanceof Error ? err.message : "Interactive mode requires a terminal. Use --yes for non-interactive mode."}\n`
+      "Error: Interactive mode requires a terminal. Use --yes for non-interactive mode.\n"
     );
     process.exitCode = 1;
     return false;