@getpeppr/cli 0.7.0 → 0.8.0

package/CHANGELOG.md

@@ -4,6 +4,43 @@ 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.8.0] — 2026-08-19
+
+**`getpeppr whoami`** — show the Peppol identity of the account behind your
+API key (GPR-1094). Environment, company, country, and every registered
+identifier with its status. Works with any key; `--prod`, `--local`, `--key`
+and `--json` behave as on `send` and `lookup`. No identity yet is an answer,
+not an error — the command points you at the console page where you set one up.
+
+Bundles SDK 4.3.0 (`peppol.identity.get()` — the API this command consumes).
+
+## [0.7.1] — 2026-08-18
+
+Rebundle SDK 4.1.1. This release matters for `getpeppr validate`, which runs the
+schematron validator locally from the bundled SDK.
+
+**Four rule identifiers were wrong, and 0.7.0 still reports them.** They named
+real rules from the Peppol rulebook — just not the ones being checked — which is
+worse than a typo: you could look one up, read a genuine rule, and find it had
+nothing to do with your document.
+
+| `validate` reported | It now reports | What the check actually verifies |
+| --- | --- | --- |
+| `BR-S-01` | `BR-S-05` | standard-rated line must carry a VAT rate above zero |
+| `BR-S-05` | `BR-Z-05` | zero-rated line must carry a rate of exactly zero |
+| `BR-S-06` | `BR-E-05` | VAT-exempt line must carry a rate of exactly zero |
+| `BR-S-08` | `BR-AE-05` | reverse-charge line must carry a rate of exactly zero |
+
+The checks themselves were always right — a zero-rated line carrying a non-zero
+rate was always caught. Only the label was wrong. **If you branch on any of these
+identifiers in a pipeline, they change with this version.**
+
+Fixed in SDK 4.1.0 on 2026-08-18; CLI users only receive it now, because the CLI
+bundles the SDK rather than depending on it at runtime.
+
+Also carries SDK 4.1.1, which corrects the JSDoc on `importFile()` — raw import
+does not preserve your document byte for byte, and the SDK said it did.
+
 ## [0.7.0] — 2026-08-16
 
 Rebundle SDK 4.0.0 (GPR-1061). `getpeppr send --watch` could not confirm a

package/README.md

@@ -159,6 +159,30 @@ getpeppr send invoice.json --prod
 
 When sending through the API, getpeppr determines the seller from the API key. A `from` party can still be present for local validation and UBL conversion, but the gateway ignores it for delivery.
 
+### `getpeppr whoami` — Show your Peppol identity
+
+Read the Peppol identity of the account behind your API key: the environment the key operates in, your legal entity as the gateway holds it, and every Peppol identifier registered for it with its status. Works with **any** key — standard keys included. This is the fastest way to check "is my identifier registered and verified?" without opening the console.
+
+```bash
+# Sandbox identity (default)
+getpeppr whoami
+
+# Production identity (uses your live key)
+getpeppr whoami --prod
+
+# Machine-readable
+getpeppr whoami --json
+```
+
+| Flag | Description |
+|------|-------------|
+| `--prod` | Use the live API key (default: sandbox) |
+| `--local` | Target `http://localhost:3001` (dev server) |
+| `--key <key>` | Override API key. CI use only — visible in `ps`/shell history. Prefer `GETPEPPR_API_KEY`. |
+| `--json` | Output the identity as JSON |
+
+If no legal entity exists in the environment yet, `whoami` says so and points to the console page where you create one.
+
 ### `getpeppr logout` — Remove stored credentials
 
 ```bash
@@ -175,6 +199,23 @@ Removes `~/.config/getpeppr/credentials.json`. No-op if the file doesn't exist.
 | `1` | Failure (invalid invoice, participant not found) |
 | `2` | Input error (file not found, invalid JSON, bad arguments) |
 
+### `send --watch` is two outcomes, not one
+
+Since 0.7.0, a watch that fails because the API answered something the CLI
+cannot honestly read exits **1**. Before 0.7.0 it printed a warning and exited
+`0`, which meant an automation could read a broken API as a confirmed delivery.
+
+A watch that runs out of time still exits **0**, and that is a different fact:
+the document was accepted, and the watch stopped without having *seen* a
+terminal status. It does not follow that the document is still in flight. The
+deadline is checked between polls, so a status can turn terminal during the
+final wait and never be read — the status printed on a timeout may already be
+stale. Poll again or use a webhook rather than treating a timeout as a failure.
+
+⚠️ The 60 seconds bound when the **last poll starts**, not when the command
+ends. The deadline is checked before each request, so a slow or retried call
+carries the run past it. If a pipeline needs a hard ceiling, impose your own.
+
 ## CI/CD integration
 
 ```bash
@@ -196,7 +237,7 @@ The CLI runs three validation engines from the [@getpeppr/sdk](https://www.npmjs
 2. **Business Rules** — Peppol BIS 3.0 / EN 16931 compliance (BR-xx, BR-CO-xx, PEPPOL-xx rules)
 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` and `send` need a network connection.
+Scaffolding (`init`), validation, and conversion run fully offline — no API key or network connection required. Only `lookup`, `send`, and `whoami` need a network connection.
 
 ## Invoice format
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getpeppr/cli",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "CLI tool for Peppol e-invoice validation and development",
   "type": "module",
   "bin": {
@@ -44,7 +44,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@getpeppr/sdk": "^4.0.0",
+    "@getpeppr/sdk": "^4.3.0",
     "commander": "^13.1.0",
     "picocolors": "^1.1.1"
   },