wotann 0.5.67 → 0.5.68

package/dist/index.js

@@ -198,50 +198,17 @@ program
     // (every shell is just chrome over the SAME shared slash-command
     // + runtime engine). The env/flag escape hatches and the three
     // tui-variant resolvers went with them.
-    // Auto-launch onboarding wizard on first-run when no providers are
-    // detected. The TUI also shows an inline banner (App.tsx
-    // needsOnboarding) but the explicit wizard hand-holds the user
-    // through provider auth + a smoke-test message. Skip when an
-    // explicit --provider/--model was supplied (user knows what they
-    // want), or when WOTANN_SKIP_WIZARD=1 (CI / power users), OR when
-    // stdin/stdout isn't a real TTY — the Ink wizard uses useInput()
-    // which BLOCKS forever waiting for keypresses that never arrive
-    // when no controlling TTY is attached. This was the "npx wotann
-    // hangs" failure: certain npx exec wrappers and shells run the
-    // child with a degraded TTY, the wizard mounts to a void, and
-    // every keystroke is dropped. Matching the `wotann init` guard
-    // at the corresponding code path below ensures parity.
+    // First-run onboarding is the IN-TUI OnboardingTour, mounted by
+    // AppV3 when no provider is configured (user chose the in-TUI
+    // flow over a separate pre-TUI CLI wizard — 2026-05-18). The
+    // standalone Ink wizard still exists for explicit `wotann init
+    // --wizard`; auto-launching it here too would double-onboard.
+    // For NON-TTY callers (piped / CI) no interactive tour can run —
+    // the raw-mode guard refuses cleanly — so we just print how to
+    // authenticate the standardized way and fall through.
     const detected = interactive.providers.filter((p) => p.available).length;
     const isInteractiveTTY = Boolean(process.stdin.isTTY) && Boolean(process.stdout.isTTY);
-    const skipWizard = process.env["WOTANN_SKIP_WIZARD"] === "1" ||
-        Boolean(options.provider) ||
-        Boolean(options.model) ||
-        !isInteractiveTTY;
-    if (detected === 0 && !skipWizard) {
-        try {
-            // Give the user immediate feedback so they know the wizard is
-            // about to mount — the Ink render itself can take 1-2s on
-            // cold start while react + ink load. Without this, the user
-            // sees a black screen and assumes it's hung.
-            process.stderr.write("[wotann] No providers detected — launching onboarding wizard…\n");
-            const { runOnboardingWizard } = await import("./cli/run-onboarding-wizard.js");
-            await runOnboardingWizard();
-            // After the wizard completes, re-bootstrap so the TUI sees the
-            // newly-configured providers.
-            interactive = await bootstrapInteractiveSession(process.cwd(), options);
-        }
-        catch (err) {
-            // Wizard import or run failed — log so first-launch users get
-            // a hint why the hand-holding wizard didn't appear, then fall
-            // through to the in-TUI onboarding banner.
-            const msg = err instanceof Error ? err.message : String(err);
-            process.stderr.write(`[wotann] onboarding wizard unavailable: ${msg}\n`);
-        }
-    }
-    else if (detected === 0 && !isInteractiveTTY) {
-        // Non-TTY caller with no providers: surface a plain-text hint
-        // so the user knows WHY the wizard didn't run. Then fall through
-        // to App.tsx's static banner (also TTY-safe).
+    if (detected === 0 && !isInteractiveTTY) {
         process.stderr.write("[wotann] No providers detected and stdin is not a TTY. " +
             "Run `wotann init` in an interactive terminal, or set " +
             "ANTHROPIC_API_KEY / OPENAI_API_KEY / GEMINI_API_KEY etc. " +