@getpeppr/cli 0.11.0 → 0.12.0

package/CHANGELOG.md

@@ -4,6 +4,51 @@ All notable changes to `@getpeppr/cli` are documented here.
 
 The CLI bundles `@getpeppr/sdk` into its published artifact (tsup `noExternal`), so `validate`, `convert` and `init` run the SDK's validators, country rules and UBL builder locally — an SDK release only reaches CLI users once the CLI is rebundled. Rebundle-only releases are listed with the SDK version they ship.
 
+## [0.12.0] — 2026-09-06
+
+Rebundles `@getpeppr/sdk` 5.3.0 (GPR-1280).
+
+- `getpeppr validate` and `getpeppr convert --validate` now enforce the three
+  Peppol billing-profile rules on `invoiceTypeCode` (`P0100`, `P0101`,
+  `P0112`) because they validate or build UBL locally (GPR-884, GPR-1273).
+  Documents outside the profile now fail these commands where they previously
+  passed — pipelines gating on the exit code change verdict, hence the minor.
+- The `structure` section rule IDs now designate the rules they actually
+  verify (GPR-1267): buyer name `BR-06` → `BR-07`, buyer street/city/postal
+  code → `GETPEPPR-BUYER-ADDRESS`, line VAT rate `BR-CO-17` →
+  `GETPEPPR-LINE-VAT-RATE`, `taxCurrencyRate` `BR-53` →
+  `GETPEPPR-TAX-CURRENCY-RATE`, the buyer-reference warning `BR-10` →
+  `PEPPOL-EN16931-R003`, and the due-date warning carries no id.
+- The `structure` section no longer repeats the country advisory warnings
+  that the `countryRules` section already reports: every warning is
+  displayed and counted once, and `totalWarnings` drops accordingly
+  (GPR-1267). Scripts that relied on the duplicated entries in
+  `structure.warnings` must read them from `countryRules.warnings`.
+- `getpeppr send` now uses an explicit JSON-send preflight aligned with
+  `POST /v1/invoices` (GPR-1285). Because that route currently ignores
+  `invoiceTypeCode`, profile rules `P0100`, `P0101`, and `P0112` no longer
+  block that inert field before sending. Structured `BR-CL-01` validation
+  and all other applicable offline and country checks remain active.
+
+## [0.11.1] — 2026-09-04
+
+Rebundles `@getpeppr/sdk` 5.2.0 (GPR-1084).
+
+- The `schematron` section of `getpeppr validate` now reports `BR-16` for a
+  missing invoice line and uses explicit `GETPEPPR-*` IDs for ten SDK-local
+  diagnostics that previously cited different official rules. The separate
+  `structure` and `countryRules` sections are unchanged (GPR-1267 tracks their
+  reverse audit).
+- Validation predicates, warning/error severities and process exit codes are
+  unchanged. The unit warning also stops calling every code outside the SDK's
+  small convenience list invalid under Rec20, and the payable warning no longer
+  invents `prepaidAmount` as the only possible cause. Scripts that filter the
+  `schematron` result by an old rule ID or warning text must update that filter.
+- Human-readable output now labels the section `Offline Checks (partial)` and
+  reports `Pre-flight checks passed` or `Pre-flight checks found errors`; it no
+  longer claims that the partial pass proves validity or non-compliance. The
+  `--json` shape and process exit codes are unchanged.
+
 ## [0.11.0] — 2026-09-04
 
 Rebundles `@getpeppr/sdk` 5.1.0.

package/README.md

@@ -1,6 +1,6 @@
 # @getpeppr/cli
 
-Developer toolkit for Peppol e-invoicing. Scaffold invoices, validate against Peppol BIS 3.0, convert to UBL XML, look up participants in the Peppol Directory, and send invoices to the Peppol network — all from the command line.
+Developer toolkit for Peppol e-invoicing. Scaffold invoices, run offline pre-flight checks, convert to UBL XML, look up participants in the Peppol Directory, and send invoices to the Peppol network — all from the command line.
 
 ## Installation
 
@@ -30,7 +30,7 @@ The generated template includes a Belgian seller, the sandbox test receiver as b
 
 ### `getpeppr validate` — Validate an invoice
 
-Run offline validation against Peppol BIS 3.0 business rules:
+Run partial offline pre-flight checks before the network applies the complete Peppol BIS 3.0 rulebooks:
 
 ```bash
 getpeppr validate invoice.json
@@ -44,14 +44,14 @@ Validating: invoice.json
 ── Structure ──────────────────────────────
   ✓ No errors
 
-── Business Rules (Peppol BIS 3.0) ───────
-  ✓ All rules passed
+── Offline Checks (partial) ───────────────────
+  ✓ No findings
 
 ── Country Rules ────────────────────────────
   ⚠ No structured communication reference (BE-02)
 
 ── Summary ──────────────────────────────────
-  ✓ Invoice is valid (1 warning)
+  ✓ Pre-flight checks passed (1 warning)
 ```
 
 | Flag | Description |
@@ -126,6 +126,14 @@ API key resolution order: `--key` flag → `GETPEPPR_API_KEY` env var → stored
 
 Send an invoice through the getpeppr API to the Peppol network. Targets sandbox by default; pass `--prod` for production.
 
+`getpeppr send` runs a JSON preflight aligned with `POST /v1/invoices`. That
+endpoint currently ignores `invoiceTypeCode` and lets the provider generate the
+UBL, so the send preflight does not apply `P0100`, `P0101`, or `P0112` to that
+inert field. Structure checks including `BR-CL-01`, plus every other applicable
+offline and country check, remain active. Use `getpeppr validate` or
+`getpeppr convert --validate` for full local-UBL semantics; both retain those
+profile checks because they validate or build the UBL locally.
+
 ```bash
 # Send a JSON file
 getpeppr send invoice.json
@@ -154,7 +162,7 @@ getpeppr send invoice.json --prod
 | `--attachment` | Attach the bundled test PDF |
 | `--watch` | Poll status until terminal (60s timeout) |
 | `-y, --yes` | Skip the `--prod` confirmation prompt |
-| `--no-validate` | Skip local pre-validation |
+| `--no-validate` | Skip the JSON send preflight |
 | `--json` | Machine-readable JSON output |
 | `--quiet` | Exit code only, no output |
 
@@ -232,10 +240,11 @@ GETPEPPR_API_KEY=$SANDBOX_KEY getpeppr send invoice.json --json
 
 ## What it validates
 
-The CLI runs three validation engines from the [@getpeppr/sdk](https://www.npmjs.com/package/@getpeppr/sdk):
+`getpeppr validate` and `getpeppr convert --validate` run three validation
+engines from the [@getpeppr/sdk](https://www.npmjs.com/package/@getpeppr/sdk):
 
 1. **Structure** — Required fields, type checks, format validation
-2. **Business Rules** — Peppol BIS 3.0 / EN 16931 compliance (BR-xx, BR-CO-xx, PEPPOL-xx rules)
+2. **Offline Checks** — 40 registered partial pre-flight checks: exact network-rule equivalents plus explicit `GETPEPPR-*` diagnostics. The legacy provider-capability diagnostic `unsupported_vat_category` can also appear, but is outside that count. This is not a Peppol conformance verdict.
 3. **Country Rules** — Belgium (BE), France (FR), Italy (IT), Netherlands (NL), Germany (DE)
 
 Scaffolding (`init`), validation, and conversion run fully offline — no API key or network connection required. Only `lookup`, `send`, and `whoami` need a network connection. Before a sandbox `send`, the CLI reads `GET /v1/identity`: its own generated fixture is adapted to the returned O/0 or AE/0 profile, while a user-edited file is never rewritten silently and is refused locally if its tax mode conflicts with the sender.
@@ -294,7 +303,7 @@ This is the exact template generated by `getpeppr init`. See the [full type refe
 
 ## Ready to send?
 
-Once your invoice validates, send it to the Peppol network — straight from the CLI:
+When your invoice JSON is ready, send it to the Peppol network — straight from the CLI:
 
 ```bash
 getpeppr login                       # store your sandbox key once