Extends test_rcfile_integration.sh with 2 scenarios proving Requirements 3.1-3.4: a failing rc-file command in piped/scripted mode aborts before any of the piped script's own commands run, exiting nonzero; the same failing command in an interactive session still reports the failure, continues executing the rc file's remaining lines, and reaches the normal prompt -- while still carrying the session's sticky nonzero exit-code verdict (g_session_failed is never cleared, matching how any other failing-command-then-quit interactive session already behaves). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AgYRU3zDTqNGV5Jk8aiKLg |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||