wotann 0.5.92 → 0.5.93

package/dist/ui/raw-mode-guard.d.ts

@@ -46,10 +46,26 @@ export interface ResolveStdinOptions {
 }
 /**
  * Resolve an input stream Ink can drive `useInput()` with:
- *   1. `stdin` itself if it is already raw-capable.
- *   2. else the controlling terminal (`/dev/tty`) if raw-capable.
+ *   1. controlling terminal (`/dev/tty`) if raw-capable — preferred.
+ *   2. else `stdin` if it is raw-capable — fallback for CI / Windows /
+ *      detached processes that have no controlling terminal.
  *   3. else `null` — caller MUST NOT mount the interactive Ink app
  *      (it would hang); print guidance + exit instead.
+ *
+ * Why /dev/tty FIRST (changed 2026-05-28 from stdin-first):
+ * Under `npx wotann`, `npm exec`, `sudo`, and other launchers, the
+ * subprocess's `process.stdin` can pass the static shape check
+ * (`isTTY === true`, `setRawMode` is a function) yet behave oddly
+ * when Ink actually drives it — the probe's no-op `setRawMode(false)`
+ * succeeds while Ink's `setRawMode(true)` then fails, the stream is in
+ * flowing mode because some boot import attached a `data` listener,
+ * the launcher transformed the descriptor, etc. The controlling
+ * terminal is the canonical "user's keyboard" source and is
+ * unaffected by any of that — the same pattern `less`, `vim`, `sudo`,
+ * and `git rebase -i` use for stdin-needs-tty scenarios. The fallback
+ * to `stdin` covers the no-`/dev/tty` cases (CI containers, Windows
+ * without a console, detached processes).
+ *
  * Never throws.
  */
 export declare function resolveInteractiveStdin(stdin?: unknown, opts?: ResolveStdinOptions): NodeJS.ReadStream | null;
@@ -77,10 +93,14 @@ export interface StdinDiagnosis {
     readonly ttyProbeResult?: string;
 }
 /**
- * Walks the same `resolveInteractiveStdin` steps and records what each
- * one saw. Use this when the resolver returns `null` to print a
- * self-explanatory refusal — future bug reports will include the
- * diagnosis automatically instead of just "guard refused, why?".
+ * Records the full state of BOTH potential input sources — /dev/tty
+ * (the preferred source after the 2026-05-28 reorder) and `stdin`
+ * (the fallback). Always walks both regardless of whether the
+ * resolver would have short-circuited, because the diagnostic is most
+ * useful when something looks wrong with one source: the user / next
+ * agent gets the full picture, not "stdin worked, didn't look at tty".
+ *
+ * Never throws.
  */
 export declare function diagnoseStdin(stdin?: unknown, opts?: ResolveStdinOptions): StdinDiagnosis;
 /**

package/dist/ui/raw-mode-guard.js

@@ -72,24 +72,42 @@ function defaultOpenControllingTty() {
 }
 /**
  * Resolve an input stream Ink can drive `useInput()` with:
- *   1. `stdin` itself if it is already raw-capable.
- *   2. else the controlling terminal (`/dev/tty`) if raw-capable.
+ *   1. controlling terminal (`/dev/tty`) if raw-capable — preferred.
+ *   2. else `stdin` if it is raw-capable — fallback for CI / Windows /
+ *      detached processes that have no controlling terminal.
  *   3. else `null` — caller MUST NOT mount the interactive Ink app
  *      (it would hang); print guidance + exit instead.
+ *
+ * Why /dev/tty FIRST (changed 2026-05-28 from stdin-first):
+ * Under `npx wotann`, `npm exec`, `sudo`, and other launchers, the
+ * subprocess's `process.stdin` can pass the static shape check
+ * (`isTTY === true`, `setRawMode` is a function) yet behave oddly
+ * when Ink actually drives it — the probe's no-op `setRawMode(false)`
+ * succeeds while Ink's `setRawMode(true)` then fails, the stream is in
+ * flowing mode because some boot import attached a `data` listener,
+ * the launcher transformed the descriptor, etc. The controlling
+ * terminal is the canonical "user's keyboard" source and is
+ * unaffected by any of that — the same pattern `less`, `vim`, `sudo`,
+ * and `git rebase -i` use for stdin-needs-tty scenarios. The fallback
+ * to `stdin` covers the no-`/dev/tty` cases (CI containers, Windows
+ * without a console, detached processes).
+ *
  * Never throws.
  */
 export function resolveInteractiveStdin(stdin = process.stdin, opts = {}) {
-    if (isRawModeCapable(stdin))
-        return stdin;
     const open = opts.openControllingTty ?? defaultOpenControllingTty;
     let tty = null;
     try {
         tty = open();
     }
     catch {
-        return null;
+        tty = null;
     }
-    return isRawModeCapable(tty) ? tty : null;
+    if (tty !== null && isRawModeCapable(tty))
+        return tty;
+    if (isRawModeCapable(stdin))
+        return stdin;
+    return null;
 }
 /**
  * Same observation pattern as `isRawModeCapable` but captures the
@@ -123,21 +141,16 @@ function probeStdinDetail(stream) {
     }
 }
 /**
- * Walks the same `resolveInteractiveStdin` steps and records what each
- * one saw. Use this when the resolver returns `null` to print a
- * self-explanatory refusal — future bug reports will include the
- * diagnosis automatically instead of just "guard refused, why?".
+ * Records the full state of BOTH potential input sources — /dev/tty
+ * (the preferred source after the 2026-05-28 reorder) and `stdin`
+ * (the fallback). Always walks both regardless of whether the
+ * resolver would have short-circuited, because the diagnostic is most
+ * useful when something looks wrong with one source: the user / next
+ * agent gets the full picture, not "stdin worked, didn't look at tty".
+ *
+ * Never throws.
  */
 export function diagnoseStdin(stdin = process.stdin, opts = {}) {
-    const stdinProbe = probeStdinDetail(stdin);
-    if (stdinProbe.probeResult === "ok") {
-        return {
-            stdinIsTTY: stdinProbe.isTTY,
-            stdinHasSetRawMode: stdinProbe.hasSetRawMode,
-            stdinProbeResult: stdinProbe.probeResult,
-            ttyOpenResult: "not-attempted",
-        };
-    }
     const open = opts.openControllingTty ?? defaultOpenControllingTty;
     let tty = null;
     let ttyOpenResult;
@@ -148,6 +161,7 @@ export function diagnoseStdin(stdin = process.stdin, opts = {}) {
     catch (e) {
         ttyOpenResult = e instanceof Error ? e.message : String(e);
     }
+    const stdinProbe = probeStdinDetail(stdin);
     if (tty === null) {
         return {
             stdinIsTTY: stdinProbe.isTTY,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wotann",
-  "version": "0.5.92",
+  "version": "0.5.93",
   "description": "WOTANN — The All-Father of AI Agent Harnesses",
   "type": "module",
   "main": "dist/index.js",