Fix CI build failures: resolve ESLint errors and formatting issues

[Copilot]

Summary

This PR fixes failing CI builds by addressing code quality issues that were preventing the pipeline from passing. The changes are minimal and surgical, focusing only on the blocking errors without modifying functional code.

Issues Fixed

1. ESLint Errors (2 blocking errors)

• Location: tests/cli/index.test.ts (lines 41 and 83)
• Issue: ESLint rule @typescript-eslint/prefer-nullish-coalescing was violated
• Fix: Replaced logical OR (||) with nullish coalescing (??) operator

Before:

resolve(code || 0);

After:

resolve(code ?? 0);

2. Prettier Formatting Issues

• Location: tests/cli/index.test.ts
• Issue: Code style violations detected by Prettier
• Fix: Applied automatic formatting using npm run format

Validation

All CI quality gates now pass:

• ✅ Type checking: No TypeScript compilation errors
• ✅ Formatting: All files follow Prettier code style
• ✅ Linting: 0 errors, 79 warnings (within CI limit of 100)
• ✅ Tests: All 32 tests passing, 3 skipped (no regressions)
• ✅ Build: TypeScript compilation successful

Impact

• No functional changes: Only code quality improvements
• No breaking changes: All existing tests continue to pass
• CI pipeline: Should now pass all quality gates
• Developer experience: Cleaner code that follows project standards

The changes align with the project's preference for nullish coalescing over logical OR when dealing with potentially null/undefined values, providing more predictable behavior when code is 0 (falsy but valid exit code).

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[elad12390]

Didn't do what i requested already did this myself.