test: guard CLI errors against stack trace leaks

[cursor]

Risky behavior now covered

• Rejected CLI commands must exit unsuccessfully while emitting only the safe error message.
• Source locations, stack frames, and other exception details must not leak to users.
• The failure path must not write anything to stdout.

Test files

• Added test/cli.test.ts, a black-box subprocess test of the real CLI entrypoint.

Regression value

This directly protects the recent CLI information-disclosure fix. Replacing the guarded parseAsync() rejection handler with the previous bare call makes the test fail on the emitted source location and stack trace, proving the test detects the security regression without changing production behavior.

Validation

• npm exec vitest -- run — 133 tests passed
• npm run build — passed
• npm exec prettier -- --check test/cli.test.ts — passed

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
polyagent	Ready	Preview	Aug 13, 2026 10:07am