cdx-chores 0.1.2-canary.3 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,13 +2,15 @@
2
2
 
3
3
  A Node.js CLI for file-processing chores, tabular data workflows, rename automation, and Codex-assisted tasks.
4
4
 
5
- Stable release scope in `v0.1.1`:
5
+ Stable release scope in `v0.1.2`:
6
6
 
7
7
  - interactive mode + nested CLI commands, including `Esc` exit on command menus
8
8
  - `doctor` capability checks
9
9
  - CSV / TSV / JSON conversion and preview workflows, including explicit headerless preview support
10
10
  - `data extract` for shaped-table materialization across delimited, SQLite, and Excel inputs
11
11
  - DuckDB-backed query, reviewed header-mapping, source-shape replay, and Parquet preview workflows
12
+ - `data stack` for assembling multiple CSV, TSV, JSONL, or JSON files and directories into one output table
13
+ - replayable `data stack` plan artifacts, dry-run diagnostics, duplicate/key checks, and optional reviewed Codex assistance
12
14
  - `md to-docx` via `pandoc`
13
15
  - preview-first rename flows
14
16
  - `ffmpeg`-backed video wrappers, including GIF quality modes and profiles
@@ -48,7 +50,7 @@ Runtime requirement:
48
50
  | Command group | Important subcommands | Purpose | Capability notes |
49
51
  | ------------- | --------------------- | ------- | ---------------- |
50
52
  | `doctor` | `doctor`, `doctor --json` | Inspect current tool and feature readiness | Run this first on a new machine or after environment changes |
51
- | `data` | `preview`, `extract`, `query`, `query codex`, `parquet preview`, `duckdb doctor`, `duckdb extension install`, `(conversion actions)` | Tabular conversion, preview, extraction, DuckDB-backed SQL query, and Codex SQL drafting | lightweight `csv` / `tsv` / `json` preview and conversion stay on the in-memory PapaParse-backed path; `extract` is best suited to shaping one clean table, especially from awkward Excel inputs, while `query` is the more expressive lane for nontrivial filtering, projection, and output selection |
53
+ | `data` | `preview`, `extract`, `query`, `query codex`, `stack`, `stack replay`, `parquet preview`, `duckdb doctor`, `duckdb extension install`, `(conversion actions)` | Tabular conversion, preview, extraction, multi-source stacking, DuckDB-backed SQL query, and Codex SQL drafting | lightweight `csv` / `tsv` / `json` preview and conversion stay on the in-memory PapaParse-backed path; `extract` is best suited to shaping one clean table, `stack` assembles many matching local sources before later work, and `query` is the expressive lane for filtering, projection, and output selection |
52
54
  | `md` | `to-docx`, `frontmatter-to-json` | Markdown conversion and metadata extraction | `to-docx` requires `pandoc` |
53
55
  | `rename` | `file`, `batch`, `cleanup`, `apply` | Safe rename previews, cleanup flows, and replayable apply runs | Codex analyzer routes are optional, not required for standard rename usage |
54
56
  | `video` | `convert`, `resize`, `gif` | `ffmpeg`-backed video wrappers | Requires `ffmpeg` |
@@ -57,7 +59,8 @@ Runtime requirement:
57
59
  Data notes:
58
60
 
59
61
  - conversion actions are `json-to-csv`, `json-to-tsv`, `csv-to-json`, `csv-to-tsv`, `tsv-to-csv`, and `tsv-to-json`
60
- - `data extract` materializes one shaped table from one input file to `.csv`, `.tsv`, or `.json`; in `v0.1.1` its strongest shaping surface is Excel-oriented cleanup, where it can target a sheet or range, set `--header-row` and `--body-start-row`, and replay reviewed source-shape or header-mapping artifacts for awkward header bands or merged-cell layouts
62
+ - `data extract` materializes one shaped table from one input file to `.csv`, `.tsv`, or `.json`; its strongest shaping surface is Excel-oriented cleanup, where it can target a sheet or range, set `--header-row` and `--body-start-row`, and replay reviewed source-shape or header-mapping artifacts for awkward header bands or merged-cell layouts
63
+ - `data stack` materializes one merged table from many local files or directories; use it before `data query` when the first problem is file assembly rather than SQL
61
64
  - `data query` is the current general-purpose lane when you need richer filtering or transformation logic than `data extract` exposes without SQL
62
65
 
63
66
  ## Capability Checks And External Tools
@@ -356,8 +359,11 @@ Data:
356
359
 
357
360
  - `docs/guides/data-preview-usage.md`
358
361
  - `docs/guides/data-extract-usage.md`
362
+ - `docs/guides/data-stack-usage.md`
363
+ - `docs/guides/data-source-shape-usage.md`
359
364
  - `docs/guides/data-schema-and-mapping-usage.md`
360
365
  - `docs/guides/data-query-usage.md`
366
+ - `docs/guides/data-query-interactive-usage.md`
361
367
  - `docs/guides/data-duckdb-usage.md`
362
368
  - `docs/guides/data-query-codex-usage.md`
363
369