etlplus 0.16.5__tar.gz → 0.16.10__tar.gz

{etlplus-0.16.5 → etlplus-0.16.10}/CONTRIBUTING.md

@@ -14,7 +14,7 @@ email, or any other method with the owners of this repository before making a ch
   - [Type Checking](#type-checking)
   - [Typing Philosophy](#typing-philosophy)
   - [Testing](#testing)
-    - [Unit vs. Integration](#unit-vs-integration)
+    - [Unit vs. Smoke vs. Integration](#unit-vs-smoke-vs-integration)
     - [Where to put tests](#where-to-put-tests)
     - [Common patterns](#common-patterns)
 
@@ -54,8 +54,8 @@ but using the stubs can provide a nicer editing experience.
 
 We optimize for a great editor experience and a permissive runtime:
 
-- TypedDicts in `etlplus/config/types.py` are editor/type-checking hints.  They are intentionally
-  `total=False` (all keys optional) and are not enforced at runtime.
+- TypedDicts in `etlplus/*/types.py` (for example `etlplus/api/types.py`) are editor/type-checking
+  hints. They are intentionally `total=False` (all keys optional) and are not enforced at runtime.
 - Constructors named `*.from_obj` accept `Mapping[str, Any]` and perform tolerant parsing and light
   casting.  This keeps runtime permissive while improving autocomplete and static analysis.
 - Prefer `Mapping[str, Any]` for inputs and plain `dict[...]` for internal state/returns.  Avoid
@@ -104,26 +104,32 @@ class ExampleConfig:
 
 ## Testing
 
-### Unit vs. Integration
+### Unit vs. Smoke vs. Integration
 
-Use these guidelines to decide whether a test belongs in the unit or integration suite:
+Use these guidelines to decide whether a test belongs in the unit, smoke, or integration suite:
 
 - Unit tests (put under `tests/unit/`):
   - Exercise a single function or class in isolation (no orchestration across modules).
   - No real file system or network I/O. Use in-memory data and stubs.
-  - Examples in this repo: `etlplus.cli.create_parser`, small helpers in `etlplus.utils`, validation and transform functions.
+  - Examples in this repo: small helpers in `etlplus.utils`, validation and transform functions.
   - Fast and deterministic; rely on `monkeypatch` to stub collaborators.
 
 - Integration tests (put under `tests/integration/`):
   - Exercise end-to-end flows across modules and boundaries (CLI `main()`, `run()` pipeline orchestration, file connectors, API client pagination wiring).
   - Can use temporary files/directories, and stub network with fakes/mocks.
-  - Examples in this repo: CLI end-to-end, pipeline smoke tests, pagination strategy, runner defaults for pagination/rate limits, target URL composition.
+  - Examples in this repo: CLI end-to-end, pagination strategy, runner defaults for pagination/rate limits, target URL composition.
+
+- Smoke tests (put under `tests/smoke/`):
+  - Minimal end-to-end checks for core flows; very fast and stable.
+  - May touch temporary files but avoid external network calls.
+  - Examples in this repo: pipeline smoke tests.
 
 If a test calls `etlplus.cli.main()` or `etlplus.ops.run.run()`, it is integration by default.
 
 ### Where to put tests
 
 - Unit tests live in `tests/unit/` and should import and test specific functions/classes directly.
+- Smoke tests live in `tests/smoke/` and should focus on minimal end-to-end CLI/pipeline checks.
 - Integration tests live in `tests/integration/` and may simulate real usage using CLI argv, temporary files, and fake clients.
 - The `tests/integration/conftest.py` applies `@pytest.mark.integration` to all tests in that folder. You don’t need to add the marker per test.
 - Markers are declared in `pytest.ini`. Avoid introducing ad-hoc markers without adding them there.

{etlplus-0.16.5 → etlplus-0.16.10}/DEMO.md

@@ -32,10 +32,10 @@ etlplus 0.3.4
 
 ```bash
 $ etlplus --help
-usage: etlplus [-h] [--version] {extract,validate,transform,load} ...
+Usage: etlplus [OPTIONS] COMMAND [ARGS]...
 
 ETLPlus - A Swiss Army knife for enabling simple ETL operations
-...
+# (Output abbreviated; run `etlplus --help` for the full command list.)
 ```
 
 ## Demo 1: Extract Data from Different Sources
@@ -43,7 +43,7 @@ ETLPlus - A Swiss Army knife for enabling simple ETL operations
 ### Extract from JSON
 ```bash
 $ echo '{"name": "John", "age": 30}' > sample.json
-$ etlplus extract file sample.json
+$ etlplus extract sample.json
 {
   "name": "John",
   "age": 30
@@ -111,8 +111,8 @@ $ etlplus transform --operations '{
 
 ### Sort Data
 ```bash
-$ etlplus transform -\
-  -operations '{"sort": {"field": "score", "reverse": true}}' \
+$ etlplus transform \
+  --operations '{"sort": {"field": "score", "reverse": true}}' \
   '[{"name": "Charlie", "score": 85}, {"name": "Alice", "score": 95}, {"name": "Bob", "score": 90}]'
 ```
 
@@ -133,9 +133,8 @@ $ etlplus transform --operations '{"aggregate": {"field": "sales", "func": "sum"
 
 ### Load to JSON File
 ```bash
-$ etlplus load \
-  '{"name": "John", "status": "active"}' \
-  output.json --target-type file
+$ echo '{"name": "John", "status": "active"}' \
+  | etlplus load output.json --target-type file
 {
   "status": "success",
   "message": "Data loaded to output.json",
@@ -145,12 +144,12 @@ $ etlplus load \
 
 ### Load to CSV File
 ```bash
-$ etlplus load \
-  '[
-    {"name": "John", "email": "john@example.com"},
-    {"name": "Jane", "email": "jane@example.com"}
-  ]' \
-  users.csv --target-type file
+$ cat << 'JSON' | etlplus load users.csv --target-type file
+[
+  {"name": "John", "email": "john@example.com"},
+  {"name": "Jane", "email": "jane@example.com"}
+]
+JSON
 {
   "status": "success",
   "message": "Data loaded to users.csv",
@@ -190,7 +189,7 @@ $ etlplus validate \
   transformed.json
 
 # Step 4: Load
-$ etlplus load transformed.json file final_output.csv
+$ cat transformed.json | etlplus load final_output.csv
 ```
 
 ## Demo 6: Using Python API
@@ -199,7 +198,7 @@ $ etlplus load transformed.json file final_output.csv
 from etlplus.ops import extract, validate, transform, load
 
 # Extract
-data = extract("file", "data.csv", format="csv")
+data = extract("file", "data.csv", file_format="csv")
 
 # Validate
 validation_result = validate(data, {
@@ -214,7 +213,7 @@ if validation_result["valid"]:
     })
 
     # Load
-    load(transformed, "file", "output.json", format="json")
+    load(transformed, "file", "output.json", file_format="json")
     print("ETL pipeline completed successfully!")
 else:
     print(f"Validation errors: {validation_result['errors']}")

{etlplus-0.16.5/etlplus.egg-info → etlplus-0.16.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: etlplus
-Version: 0.16.5
+Version: 0.16.10
 Summary: A Swiss Army knife for simple ETL operations
 Home-page: https://github.com/Dagitali/ETLPlus
 Author: ETLPlus Team
@@ -141,7 +141,7 @@ ETLPlus supports Python 3.13 and above.
 
 - **Extract** data from multiple sources:
   - Files (CSV, JSON, XML, YAML)
-  - Databases (connection string support)
+  - Databases (connection string support; extract is a placeholder today)
   - REST APIs (GET)
 
 - **Validate** data with flexible rules:
@@ -161,7 +161,7 @@ ETLPlus supports Python 3.13 and above.
 
 - **Load** data to multiple targets:
   - Files (CSV, JSON, XML, YAML)
-  - Databases (connection string support)
+  - Databases (connection string support; load is a placeholder today)
   - REST APIs (PATCH, POST, PUT)
 
 ## Installation
@@ -188,7 +188,7 @@ etlplus --help
 etlplus --version
 
 # One-liner: extract CSV, filter, select, and write JSON
-etlplus extract file examples/data/sample.csv \
+etlplus extract examples/data/sample.csv \
   | etlplus transform --operations '{"filter": {"field": "age", "op": "gt", "value": 25}, "select": ["name", "email"]}' \
   - temp/sample_output.json
 ```
@@ -218,8 +218,9 @@ include GET for extract and PATCH/POST/PUT for load.
 
 ### Databases (`database`)
 
-Database connectors use connection strings for extraction and loading, and
-DDL can be rendered from table specs for migrations or schema checks.
+Database connectors use connection strings for extraction and loading, and DDL can be rendered from
+table specs for migrations or schema checks. Database extract/load operations are currently
+placeholders; plan to integrate a database client in your runner.
 
 ### Files (`file`)
 
@@ -298,7 +299,7 @@ Recognized file formats are listed in the tables below. Support for reading to o
 | `numbers` | N | N | Apple Numbers |
 | `ods` | N | N | OpenDocument |
 | `wks` | N | N | Lotus 1-2-3  |
-| `xls` | Y | Y | Microsoft Excel (BIFF) |
+| `xls` | Y | N | Microsoft Excel (BIFF; read-only) |
 | `xlsm` | N | N | Microsoft Excel Macro-Enabled (Open XML) |
 | `xlsx` | Y | Y | Microsoft Excel (Open XML) |
 
@@ -320,8 +321,8 @@ Recognized file formats are listed in the tables below. Support for reading to o
 
 #### Logs and Event Streams
 
-| Format | Supported | Description |
-| --- | --- | --- |
+| Format | Read | Write | Description |
+| --- | --- | --- | --- |
 | `log` | N | N | Generic log file |
 
 #### Data Archives
@@ -354,13 +355,14 @@ etlplus --help
 etlplus --version
 ```
 
-The CLI is implemented with Typer (Click-based). There is no argparse compatibility layer, so rely
-on the documented commands/flags and run `etlplus <command> --help` for current options.
+The CLI is implemented with Typer (Click-based). The legacy argparse parser has been removed, so
+rely on the documented commands/flags and run `etlplus <command> --help` for current options.
 
 **Example error messages:**
 
 - If you omit a required argument: `Error: Missing required argument 'SOURCE'.`
-- If you place an option before its argument: `Error: Option '--source-format' must follow the 'SOURCE' argument.`
+- If you place an option before its argument: `Error: Option '--source-format' must follow the
+  'SOURCE' argument.`
 
 #### Argument Order and Required Options
 
@@ -424,27 +426,27 @@ specific parser.
 
 Extract from JSON file:
 ```bash
-etlplus extract file examples/data/sample.json
+etlplus extract examples/data/sample.json
 ```
 
 Extract from CSV file:
 ```bash
-etlplus extract file examples/data/sample.csv
+etlplus extract examples/data/sample.csv
 ```
 
 Extract from XML file:
 ```bash
-etlplus extract file examples/data/sample.xml
+etlplus extract examples/data/sample.xml
 ```
 
 Extract from REST API:
 ```bash
-etlplus extract api https://api.example.com/data
+etlplus extract https://api.example.com/data
 ```
 
 Save extracted data to file:
 ```bash
-etlplus extract file examples/data/sample.csv > temp/sample_output.json
+etlplus extract examples/data/sample.csv > temp/sample_output.json
 ```
 
 #### Validate Data
@@ -510,13 +512,13 @@ etlplus transform \
 
 Load to JSON file:
 ```bash
-etlplus extract file examples/data/sample.json \
+etlplus extract examples/data/sample.json \
   | etlplus load temp/sample_output.json --target-type file
 ```
 
 Load to CSV file:
 ```bash
-etlplus extract file examples/data/sample.csv \
+etlplus extract examples/data/sample.csv \
   | etlplus load temp/sample_output.csv --target-type file
 ```
 
@@ -553,13 +555,13 @@ operations = {
 transformed = transform(data, operations)
 
 # Load data
-load(transformed, "file", "temp/sample_output.json", format="json")
+load(transformed, "file", "temp/sample_output.json", file_format="json")
 ```
 
 For YAML-driven pipelines executed end-to-end (extract → validate → transform → load), see:
 
 - Authoring: [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
-- Runner API and internals: [`docs/run-module.md`](docs/run-module.md)
+- Runner API and internals: see `etlplus.ops.run` docstrings and `docs/pipeline-guide.md`.
 
 CLI quick reference for pipelines:
 
@@ -576,7 +578,7 @@ etlplus run --config examples/configs/pipeline.yml --job file_to_file_customers
 
 ```bash
 # 1. Extract from CSV
-etlplus extract file examples/data/sample.csv > temp/sample_extracted.json
+etlplus extract examples/data/sample.csv > temp/sample_extracted.json
 
 # 2. Transform (filter and select fields)
 etlplus transform \
@@ -611,7 +613,7 @@ etlplus load output.bin --target-type file --target-format csv < data.json
 
 # Leave the flags off when extensions already match the desired format
 etlplus extract data.csv --source-type file
-etlplus load data.json --target-type file  < data.json
+etlplus load output.json --target-type file < data.json
 ```
 
 ## Transformation Operations
@@ -706,8 +708,9 @@ Looking for the HTTP client and pagination helpers?  See the dedicated docs in
 
 Curious how the pipeline runner composes API requests, pagination, and load calls?
 
-- Runner overview and helpers: [`docs/run-module.md`](docs/run-module.md)
-- Unified "connector" vocabulary (API/File/DB): `etlplus/config/connector.py`
+- Runner overview and helpers: see `etlplus.ops.run` docstrings and
+  [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
+- Unified "connector" vocabulary (API/File/DB): `etlplus/connector`
   - API/file targets reuse the same shapes as sources; API targets typically set a `method`.
 
 ### Running Tests
@@ -718,10 +721,12 @@ pytest tests/ -v
 
 #### Test Layers
 
-We split tests into two layers:
+We split tests into three layers:
 
 - **Unit (`tests/unit/`)**: single function or class, no real I/O, fast, uses stubs/monkeypatch
-  (e.g.  `etlplus.cli.create_parser`, transform + validate helpers).
+  (e.g. small helpers in `etlplus.utils`, transform + validate helpers).
+- **Smoke (`tests/smoke/`)**: minimal end-to-end checks for core flows; may touch temp files but
+  avoids external network calls.
 - **Integration (`tests/integration/`)**: end-to-end flows (CLI `main()`, pipeline `run()`,
   pagination + rate limit defaults, file/API connector interactions) may touch temp files and use
   fake clients.
@@ -808,7 +813,7 @@ Navigate to detailed documentation for each subpackage:
 - [etlplus.cli](etlplus/cli/README.md): Command-line interface definitions for `etlplus`
 - [etlplus.database](etlplus/database/README.md): Database engine, schema, and ORM helpers
 - [etlplus.templates](etlplus/templates/README.md): SQL and DDL template helpers
-- [etlplus.validation](etlplus/validation/README.md): Data validation utilities and helpers
+- [etlplus.ops](etlplus/ops/README.md): Extract/validate/transform/load primitives
 - [etlplus.workflow](etlplus/workflow/README.md): Helpers for data connectors, pipelines, jobs, and
   profiles
 
@@ -824,7 +829,7 @@ Navigate to detailed documentation for each subpackage:
 - API client docs: [`etlplus/api/README.md`](etlplus/api/README.md)
 - Examples: [`examples/README.md`](examples/README.md)
 - Pipeline authoring guide: [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
-- Runner internals: [`docs/run-module.md`](docs/run-module.md)
+- Runner internals: see `etlplus.ops.run` docstrings and [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
 - Design notes (Mapping inputs, dict outputs): [`docs/pipeline-guide.md#design-notes-mapping-inputs-dict-outputs`](docs/pipeline-guide.md#design-notes-mapping-inputs-dict-outputs)
 - Typing philosophy: [`CONTRIBUTING.md#typing-philosophy`](CONTRIBUTING.md#typing-philosophy)
 - Demo and walkthrough: [`DEMO.md`](DEMO.md)

{etlplus-0.16.5 → etlplus-0.16.10}/README.md

@@ -91,7 +91,7 @@ ETLPlus supports Python 3.13 and above.
 
 - **Extract** data from multiple sources:
   - Files (CSV, JSON, XML, YAML)
-  - Databases (connection string support)
+  - Databases (connection string support; extract is a placeholder today)
   - REST APIs (GET)
 
 - **Validate** data with flexible rules:
@@ -111,7 +111,7 @@ ETLPlus supports Python 3.13 and above.
 
 - **Load** data to multiple targets:
   - Files (CSV, JSON, XML, YAML)
-  - Databases (connection string support)
+  - Databases (connection string support; load is a placeholder today)
   - REST APIs (PATCH, POST, PUT)
 
 ## Installation
@@ -138,7 +138,7 @@ etlplus --help
 etlplus --version
 
 # One-liner: extract CSV, filter, select, and write JSON
-etlplus extract file examples/data/sample.csv \
+etlplus extract examples/data/sample.csv \
   | etlplus transform --operations '{"filter": {"field": "age", "op": "gt", "value": 25}, "select": ["name", "email"]}' \
   - temp/sample_output.json
 ```
@@ -168,8 +168,9 @@ include GET for extract and PATCH/POST/PUT for load.
 
 ### Databases (`database`)
 
-Database connectors use connection strings for extraction and loading, and
-DDL can be rendered from table specs for migrations or schema checks.
+Database connectors use connection strings for extraction and loading, and DDL can be rendered from
+table specs for migrations or schema checks. Database extract/load operations are currently
+placeholders; plan to integrate a database client in your runner.
 
 ### Files (`file`)
 
@@ -248,7 +249,7 @@ Recognized file formats are listed in the tables below. Support for reading to o
 | `numbers` | N | N | Apple Numbers |
 | `ods` | N | N | OpenDocument |
 | `wks` | N | N | Lotus 1-2-3  |
-| `xls` | Y | Y | Microsoft Excel (BIFF) |
+| `xls` | Y | N | Microsoft Excel (BIFF; read-only) |
 | `xlsm` | N | N | Microsoft Excel Macro-Enabled (Open XML) |
 | `xlsx` | Y | Y | Microsoft Excel (Open XML) |
 
@@ -270,8 +271,8 @@ Recognized file formats are listed in the tables below. Support for reading to o
 
 #### Logs and Event Streams
 
-| Format | Supported | Description |
-| --- | --- | --- |
+| Format | Read | Write | Description |
+| --- | --- | --- | --- |
 | `log` | N | N | Generic log file |
 
 #### Data Archives
@@ -304,13 +305,14 @@ etlplus --help
 etlplus --version
 ```
 
-The CLI is implemented with Typer (Click-based). There is no argparse compatibility layer, so rely
-on the documented commands/flags and run `etlplus <command> --help` for current options.
+The CLI is implemented with Typer (Click-based). The legacy argparse parser has been removed, so
+rely on the documented commands/flags and run `etlplus <command> --help` for current options.
 
 **Example error messages:**
 
 - If you omit a required argument: `Error: Missing required argument 'SOURCE'.`
-- If you place an option before its argument: `Error: Option '--source-format' must follow the 'SOURCE' argument.`
+- If you place an option before its argument: `Error: Option '--source-format' must follow the
+  'SOURCE' argument.`
 
 #### Argument Order and Required Options
 
@@ -374,27 +376,27 @@ specific parser.
 
 Extract from JSON file:
 ```bash
-etlplus extract file examples/data/sample.json
+etlplus extract examples/data/sample.json
 ```
 
 Extract from CSV file:
 ```bash
-etlplus extract file examples/data/sample.csv
+etlplus extract examples/data/sample.csv
 ```
 
 Extract from XML file:
 ```bash
-etlplus extract file examples/data/sample.xml
+etlplus extract examples/data/sample.xml
 ```
 
 Extract from REST API:
 ```bash
-etlplus extract api https://api.example.com/data
+etlplus extract https://api.example.com/data
 ```
 
 Save extracted data to file:
 ```bash
-etlplus extract file examples/data/sample.csv > temp/sample_output.json
+etlplus extract examples/data/sample.csv > temp/sample_output.json
 ```
 
 #### Validate Data
@@ -460,13 +462,13 @@ etlplus transform \
 
 Load to JSON file:
 ```bash
-etlplus extract file examples/data/sample.json \
+etlplus extract examples/data/sample.json \
   | etlplus load temp/sample_output.json --target-type file
 ```
 
 Load to CSV file:
 ```bash
-etlplus extract file examples/data/sample.csv \
+etlplus extract examples/data/sample.csv \
   | etlplus load temp/sample_output.csv --target-type file
 ```
 
@@ -503,13 +505,13 @@ operations = {
 transformed = transform(data, operations)
 
 # Load data
-load(transformed, "file", "temp/sample_output.json", format="json")
+load(transformed, "file", "temp/sample_output.json", file_format="json")
 ```
 
 For YAML-driven pipelines executed end-to-end (extract → validate → transform → load), see:
 
 - Authoring: [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
-- Runner API and internals: [`docs/run-module.md`](docs/run-module.md)
+- Runner API and internals: see `etlplus.ops.run` docstrings and `docs/pipeline-guide.md`.
 
 CLI quick reference for pipelines:
 
@@ -526,7 +528,7 @@ etlplus run --config examples/configs/pipeline.yml --job file_to_file_customers
 
 ```bash
 # 1. Extract from CSV
-etlplus extract file examples/data/sample.csv > temp/sample_extracted.json
+etlplus extract examples/data/sample.csv > temp/sample_extracted.json
 
 # 2. Transform (filter and select fields)
 etlplus transform \
@@ -561,7 +563,7 @@ etlplus load output.bin --target-type file --target-format csv < data.json
 
 # Leave the flags off when extensions already match the desired format
 etlplus extract data.csv --source-type file
-etlplus load data.json --target-type file  < data.json
+etlplus load output.json --target-type file < data.json
 ```
 
 ## Transformation Operations
@@ -656,8 +658,9 @@ Looking for the HTTP client and pagination helpers?  See the dedicated docs in
 
 Curious how the pipeline runner composes API requests, pagination, and load calls?
 
-- Runner overview and helpers: [`docs/run-module.md`](docs/run-module.md)
-- Unified "connector" vocabulary (API/File/DB): `etlplus/config/connector.py`
+- Runner overview and helpers: see `etlplus.ops.run` docstrings and
+  [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
+- Unified "connector" vocabulary (API/File/DB): `etlplus/connector`
   - API/file targets reuse the same shapes as sources; API targets typically set a `method`.
 
 ### Running Tests
@@ -668,10 +671,12 @@ pytest tests/ -v
 
 #### Test Layers
 
-We split tests into two layers:
+We split tests into three layers:
 
 - **Unit (`tests/unit/`)**: single function or class, no real I/O, fast, uses stubs/monkeypatch
-  (e.g.  `etlplus.cli.create_parser`, transform + validate helpers).
+  (e.g. small helpers in `etlplus.utils`, transform + validate helpers).
+- **Smoke (`tests/smoke/`)**: minimal end-to-end checks for core flows; may touch temp files but
+  avoids external network calls.
 - **Integration (`tests/integration/`)**: end-to-end flows (CLI `main()`, pipeline `run()`,
   pagination + rate limit defaults, file/API connector interactions) may touch temp files and use
   fake clients.
@@ -758,7 +763,7 @@ Navigate to detailed documentation for each subpackage:
 - [etlplus.cli](etlplus/cli/README.md): Command-line interface definitions for `etlplus`
 - [etlplus.database](etlplus/database/README.md): Database engine, schema, and ORM helpers
 - [etlplus.templates](etlplus/templates/README.md): SQL and DDL template helpers
-- [etlplus.validation](etlplus/validation/README.md): Data validation utilities and helpers
+- [etlplus.ops](etlplus/ops/README.md): Extract/validate/transform/load primitives
 - [etlplus.workflow](etlplus/workflow/README.md): Helpers for data connectors, pipelines, jobs, and
   profiles
 
@@ -774,7 +779,7 @@ Navigate to detailed documentation for each subpackage:
 - API client docs: [`etlplus/api/README.md`](etlplus/api/README.md)
 - Examples: [`examples/README.md`](examples/README.md)
 - Pipeline authoring guide: [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
-- Runner internals: [`docs/run-module.md`](docs/run-module.md)
+- Runner internals: see `etlplus.ops.run` docstrings and [`docs/pipeline-guide.md`](docs/pipeline-guide.md)
 - Design notes (Mapping inputs, dict outputs): [`docs/pipeline-guide.md#design-notes-mapping-inputs-dict-outputs`](docs/pipeline-guide.md#design-notes-mapping-inputs-dict-outputs)
 - Typing philosophy: [`CONTRIBUTING.md#typing-philosophy`](CONTRIBUTING.md#typing-philosophy)
 - Demo and walkthrough: [`DEMO.md`](DEMO.md)

{etlplus-0.16.5 → etlplus-0.16.10}/docs/README.md

@@ -1,8 +1,12 @@
 # Documentation Notes
 
+- [Documentation Notes](#documentation-notes)
+  - [CLI Parser Status](#cli-parser-status)
+  - [Migration Hints](#migration-hints)
+
 ## CLI Parser Status
-- The CLI is now Typer/Click-only. The historical `argparse` parser and `create_parser` entrypoint
-  are deprecated and no longer supported for new integrations.
+
+- The CLI is Typer/Click-only. The historical `argparse` parser has been removed.
 - Downstream tools should invoke the Typer app exported at `etlplus.cli.commands.app` (e.g., `python
   -m etlplus` or `etlplus ...`).
 - Handler functions still accept keyword arguments; the legacy namespace shim is temporary and will
@@ -10,8 +14,9 @@
   handlers with explicit keyword arguments if you integrate programmatically.
 
 ## Migration Hints
-- Replace any imports of `etlplus.cli.main.create_parser` with Typer invocations (`etlplus` binary
-  or `app` directly).
+
+- Replace any `argparse`-based integrations with Typer invocations (`etlplus` binary or `app`
+  directly).
 - If you maintained custom subcommands around the old parser, port them to Typer by attaching to
   `app` or wrapping the `etlplus` executable.
 - Tests and examples now target the Typer surface; expect argparse-focused helpers (e.g., namespace