Unit tests for lib/output.js (table, csv, sparkline)

[Ashutosh0x]

lib/output.js (table renderer, CSV escaping, sparkline, ANSI-aware padding) has no test coverage. It is pure functions — ideal first contribution.

Task
Add node:test-based tests (no new dependencies) covering:

• table() column widths with ANSI-colored cells (visibleLength handling).
• csv() quoting of commas, quotes, and newlines; ANSI stripped.
• sparkline() min/max normalization and single-value input.
• pad() left/right alignment.

Wire up npm test in package.json.

[pk1427]

Hie, I'd like to work on this issue if it's available. I'll add the node:test coverage for lib/output.js as described.

[Ashutosh0x]

Hi @pk1427 — it's yours, thanks for picking it up. Assigning you now.

A few pointers to save you time:

• Everything you need is already exported from lib/output.js, including the visibleLength and pad internals — no need to reach into private state.
• The color helpers in lib/util.js emit ANSI codes unconditionally (there is no NO_COLOR gate), so your width assertions can use exact expected strings, e.g. c.green("abc") always measures as visible length 3.
• Please use node:test with node:assert/strict and zero new dependencies — a test/output.test.js is a fine layout. Wire it up as "test": "node --test" in package.json (there is no scripts block yet, so you will be adding it).
• For sparkline(), the single-value input case is the interesting one: assert what the current min/max normalization actually does with a flat series so we lock the behavior in.
• For csv(), cover a cell containing all three of comma, double quote and newline at once, plus one with ANSI color to prove it gets stripped.

Open the PR whenever you're ready and I'll review quickly. If anything in the renderer looks like a bug while you're writing the tests, note it in the PR rather than fixing it silently — I'd rather see the failing assertion.