test(cli): cover entrypoint behavior and exit codes

[scorpevans]

Summary

• Source change: main() is now exported and wraps parseYaml in a narrow try-catch so ENOENT and YAML parse errors are caught, printed, and exit 1 — without swallowing the process.exit calls for help/no-args (which must remain outside the catch boundary to keep exit codes correct when process.exit is intercepted in tests)
• printUsage flag tests: --out, --overwrite, --no-overwrite flags are listed in usage output
• --help / -h: exits 0, prints usage
• Missing argument: exits 1, prints usage
• File not found: exits 1, prints the ENOENT error message to stderr
• Invalid YAML: exits 1, prints [rule] entryKey: message validation errors to stderr
• Happy path: resolves normally, process.exit is never called (implicit exit 0), created/updated lines appear in stdout

Each scenario is a separate commit. Exit codes are verified explicitly in every main() test via a captured exitCodes array (the process.exit mock pushes the code and throws to stop execution).

Test plan

• pnpm --filter odetovibe test — all 158 tests pass
• Verify CI passes on push

🤖 Generated with Claude Code

[scorpevans]

Reviewed. Checked: (1) all 6 commits target distinct gaps; (2) source change is minimal — export + narrow try-catch around parseYaml only, leaving all other process.exit calls outside any catch boundary (critical for correct exit codes under test); (3) ExitError throw-and-capture pattern is correct — codes are pushed before the throw so they survive even when the error propagates; (4) fakeConfigIndex satisfies the ConfigIndex interface; (5) happy-path test asserts exitCodes is empty (implicit exit 0) rather than asserting no-throw, which is more precise; (6) validation error format ([rule] entryKey) matches the exact format in cli.ts; (7) no untracked files referenced.