fix: prevent stdout truncation when piped (#20)

[stephendolan]

Summary

Closes #20.

of was truncating its JSON output to exactly 512 bytes whenever stdout was a pipe (e.g. of inbox list | cat, ssh host 'of perspective view Forecast'). Downstream consumers like MCP servers wrapping of over SSH received valid-but-truncated JSON and threw parse errors mid-object.

Root cause is the well-known Node.js footgun: writes to a pipe are asynchronous on macOS, so calling process.exit(code) terminates the process before the queued pipe buffer drains. There were two process.exit(1) call sites — one in handleError (every error response) and one in the top-level parseAsync().catch (parse failures).

Fix replaces both with process.exitCode = code and lets the event loop drain naturally. This is the documented Node.js solution.

Verification

Repro from the issue, after the fix:

node dist/cli.js inbox list | wc -c            # 10385
node dist/cli.js inbox list | cat | wc -c      # 10385  (was 512)
node dist/cli.js inbox list | tee /tmp/x.json | wc -c  # 10385  (was 512)

Error path still returns exit code 1:

node dist/cli.js project view nonexistent | cat  # PIPESTATUS[0] = 1

Tests

Added src/lib/__tests__/errors.test.ts covering every handleError branch (OmniFocusCliError, "not found" → 404, "Multiple" → 400, plain Error, non-Error values) plus a direct regression test that pipes the JSON body and parses it end-to-end.

The tests spawn handleError in a child process: setting process.exitCode inside the test runner itself makes bun's native test runner fail the suite. The child-process approach also gives a faithful end-to-end check — it actually pipes stdout the way SSH and MCP wrappers do.

Test plan

• bun run typecheck passes
• bun run lint passes
• bun test passes (21/21)
• bun run test (vitest) passes
• bun run build succeeds
• Manual repro of all three pipe scenarios from the issue
• Manual verification that error exit code 1 still propagates through pipes
• CI green