Mohamed Boudra c4c0787286 Fix terminal test assertion for non-zero exit codes ...

The test was failing because terminal output wrapping caused "No such file"
to be split across lines with a newline between "No" and "such file". The
actual output was:
  "No\n such file or directory"

Changed the assertion to check for more reliable parts of the error message:
- "cannot access" - always present in ls errors
- "nonexistent-directory-test" - the directory name we're testing with

This is a test assertion fix, not a code bug. The terminal output is correct,
but the test expectation needed to account for line wrapping.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-30 01:22:04 +00:00

..

app

fix: lazy agent loading and type safety improvements

2025-11-29 22:44:03 +00:00

server

Fix terminal test assertion for non-zero exit codes

2025-11-30 01:22:04 +00:00