Non-TTY deploy crashes with Ink stack trace and exits 0

[jariy17]

Summary

Running agentcore deploy without --yes in a non-TTY context (piped stdin, backgrounded, CI) crashes with an Ink raw mode error but exits with code 0. Scripts and CI pipelines cannot detect the failure.

Reproducer

echo "" | agentcore deploy
# or
agentcore deploy < /dev/null

Actual behavior

ERROR Raw mode is not supported on the current process.stdin, which Ink uses
     as input stream by default.
     Read about how to prevent this error on
     https://github.com/vadimdemedes/ink/#israwmodesupported

Exit code: 0 (should be non-zero)

Expected behavior

Either:

1. Detect non-TTY and print a clear error with non-zero exit: "Interactive mode requires a TTY. Use --yes for non-interactive deploy."
2. Or auto-assume --yes when stdin is not a TTY

Impact

• CI/CD pipelines that forget --yes silently fail (no deploy, exit 0)
• Any scripted usage without --yes is broken

Notes

This affects all TUI-based commands (deploy, create, etc.), not just deploy. Found during runtime endpoint bug bash testing.