feat: stream CSV input through the terminal adapter

[tecfu]

The terminal adapter currently buffers all stdin before parsing, despite presenting itself as a streaming adapter. This changes the CSV path to pipe stdin through the csv parser and render each record as it arrives. JSON remains buffered because the existing interface accepts a complete JSON array.

[tecfu]

Review: do not merge — rework the output contract

The diagnosis is right: buffering all stdin in a "streaming" adapter is silly, and the empty-input handling (sawRow + the "No input" message, closing the third #121 crash path properly) is a genuine improvement worth keeping.

But the implementation changes what the shipped CLI means by output, and its own golden proves it: examples/cli-test.js fails, 20/21 goldens otherwise pass, matrix 0 (library untouched).

What the golden diff shows: previously one CSV rendered as one cumulative table. Now every record triggers runTable(header, [row]), and because the adapter renders in terminal-redraw mode, each record prints a complete framed table followed by \e[?25l … \e[7A\e[0J cursor-rewrite sequences. The stream is no longer a table — it's N overlapping frames. Concretely:

• cat data.csv | tty-table > out.txt (the documented usage, README + --help) produces cursor-junk instead of a table. That is a breaking change to the bin's primary contract.
• Exit semantics: with end no longer gating, the process lifetime now depends on the csv parser's stream ending; the win32 hack below the changed block still assumes the old listener shape.
• Mode flip 100755 → 100644 on adapters/terminal-adapter.js — the file is not the bin (package.json bin points at it, per fix: the tty-table command explains bad input instead of throwing #121's notes, so a non-executable bit may break direct shebang invocation; at minimum this is an unintended drive-by).

Suggested rework: keep per-record streaming but split the two modes honestly:

1. TTY → current redraw behavior, but rows accumulate (reuse the fix: column width cache was process-global, keyed by a module counter #119 adapterWidths shared-geometry path so columns don't jitter per frame — see my note on fix: invalidate measured widths when terminal geometry changes #126 which makes this worse).
2. Not a TTY → buffer-and-print once, or print the frame once and then only body lines. Either way > file must stay a valid table.

Add a golden that pipes a 2-row CSV through the bin so the contract is pinned. The JSON branch and validateRows restructure are clean and can stay.

Sincerely qwen3.8-flash-next

[tecfu]

Review: request changes — CLI output contract is still the blocker

The CSV parser is now genuinely incremental, but each parsed record calls runTable with a single row. In this adapter that means each record produces a complete table frame and terminal redraw control sequences. That may be appropriate for an interactive TTY, but it breaks the existing non-TTY contract: redirecting CSV to a file now captures multiple frames and cursor-control sequences rather than one ordinary table.

The changed golden already demonstrates this behavior, so this is not theoretical. The documented pipe/redirection use needs to remain a valid table output.

Please distinguish TTY and non-TTY output. For a TTY, incremental redraw can be appropriate; for redirected stdout, preserve the existing single-table output semantics. Also restore the executable bit on adapters/terminal-adapter.js if the mode change to 100644 was unintended.

The parser and empty-input improvements are good and can remain.

— GPT-5.6 Luna

[tecfu]

Re-review: changes addressed

CSV parsing remains incremental for interactive TTYs, while redirected/non-TTY stdout retains the single-frame plain-text contract. Cursor-control sequences are limited to interactive terminals.

CI is green. No further changes requested.

— GPT-5.6 Luna