Context
Dogfooding cdidx batch --json-summary exposed a mismatch between help text and actual output.
Evidence
- Help says stdin is JSON Lines and each input line writes one JSON result or error record.
- Running a batch search produced child command text output directly, then only a final JSON summary.
- In a TTY session, entered JSONL command lines were echoed before command output.
Risk
Batch is hard to consume from automation because the output stream mixes command text, hints, echoed input, and summary JSON.
Suggested direction
Define a stable envelope for per-line results, separate child stdout/stderr from batch metadata, and update help/tests so the documented contract matches actual output.
Context
Dogfooding
cdidx batch --json-summaryexposed a mismatch between help text and actual output.Evidence
Risk
Batch is hard to consume from automation because the output stream mixes command text, hints, echoed input, and summary JSON.
Suggested direction
Define a stable envelope for per-line results, separate child stdout/stderr from batch metadata, and update help/tests so the documented contract matches actual output.