From the roadmap (VISION.md, "Future: compare mode"): run the same predicate across two tables - flat vs partitioned, before vs after compaction, before vs after OPTIMIZE - and render a side-by-side report with the delta highlighted.
This is the largest new surface in the backlog and deliberately scheduled last:
- CLI shape to design (two table arguments?
--compare <path>?).
- JSON contract implications: a comparison document is a new top-level shape, not an additive field on the single-table report.
- Text rendering and the report viewer both need a two-column story.
No analysis semantics change: both sides run the existing pipeline; compare mode is presentation over two reports.
From the roadmap (VISION.md, "Future: compare mode"): run the same predicate across two tables - flat vs partitioned, before vs after compaction, before vs after
OPTIMIZE- and render a side-by-side report with the delta highlighted.This is the largest new surface in the backlog and deliberately scheduled last:
--compare <path>?).No analysis semantics change: both sides run the existing pipeline; compare mode is presentation over two reports.