jaz-clio 5.50.0 → 5.51.0

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.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-api
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill whenever you call, debug, or review code that touches the Jaz
6
6
  REST API. Covers field names, response shapes, 159 production gotchas, error
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-cli
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill when running Clio CLI commands, building shell scripts with
6
6
  Clio, debugging auth issues, understanding --json output, paginating results,
@@ -299,8 +299,15 @@ The navigation tool (`navigate` — no destination to discover keys, a destinati
299
299
 
300
300
  CLI commands exit with standard codes:
301
301
  - **Exit 0** — success
302
- - **Exit 1** — user error (missing flags, invalid input, validation failure)
303
- - **Exit 2** — auth error (invalid key, unreachable API)
302
+ - **Exit 1** — your input needs changing (missing flags, malformed id, over-limit or duplicate batch, blank required text, unknown enum value). Also a business refusal on some commands, e.g. `approvals`.
303
+ - **Exit 2** — the request was fine and the API refused or failed, OR an internal defect
304
+ - **Exit 3** — auth (invalid, missing or unresolvable key)
305
+
306
+ **Branch on the `code` in the `--json` error envelope, not on the number alone.** Exit 1 is
307
+ `VALIDATION_ERROR` for bad input but is also used by commands that report a refusal (there the
308
+ outcome is on stdout, not stderr). Exit 2 splits into `API_ERROR` (the server refused; a
309
+ different request may work) and `UNKNOWN_ERROR` (our defect; an identical retry fails
310
+ identically). The code is the signal for whether retrying with different input can help.
304
311
 
305
312
  Error messages go to stderr. When `--json` is set, the error is still on stderr so stdout stays parseable. Common errors:
306
313
 
@@ -382,7 +382,9 @@ The other end of `drafts submit-for-approval`. Approving POSTS THE LEDGER and is
382
382
 
383
383
  `request-changes` accepts more families than `approve`: also `purchase-orders`, `purchase-requests`, `sale-orders`, `sale-quotes`, `claims`.
384
384
 
385
- **Exit codes carry the outcome, because a refusal is not always an error.** Credit notes refuse with HTTP 200, `isSuccess:false`, and an `approvalStatus` that still reads `APPROVED` — the document's state, not the call's. `0` = approved · `1` = refused (reason printed) or UNCONFIRMED (no per-record outcome came back) · `2` = API error. Never read HTTP 200 or `approvalStatus` as success.
385
+ **Exit codes carry the outcome, because a refusal is not always an error.** Credit notes refuse with HTTP 200, `isSuccess:false`, and an `approvalStatus` that still reads `APPROVED` — the document's state, not the call's. `0` = approved · `1` = refused, UNCONFIRMED, **or your input was rejected before anything was sent** · `2` = API error. Never read HTTP 200 or `approvalStatus` as success.
386
+
387
+ Exit 1 carries three meanings here, so **read the JSON, not the number**: a refusal or UNCONFIRMED writes an outcome to **stdout** (`{"approved": false}` / `null`), while a rejected input writes `{"error":{"code":"VALIDATION_ERROR"}}` to **stderr** and nothing to stdout. Only the first two mean the request reached the API.
386
388
 
387
389
  Claims approve via `clio claims approve` (a different endpoint), not through this group.
388
390
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-conversion
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill when migrating accounting data into Jaz — importing from Xero,
6
6
  QuickBooks, Sage, MYOB, or Excel exports. Covers the full conversion pipeline:
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-kit
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill when an accountant, bookkeeper, or owner is running real books
6
6
  in Jaz across one or more organizations from the terminal — setting up a
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-pseudo-sql
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill when answering ad-hoc data questions that aren't covered by
6
6
  download_export (canonical reports — anomaly, audit, aging, P&L, BS, GL,
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-jobs
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill for recurring accounting workflows — month/quarter/year-end
6
6
  close, bank reconciliation, GST/VAT filing, payment runs, credit control,
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: jaz-recipes
3
- version: 5.50.0
3
+ version: 5.51.0
4
4
  description: >-
5
5
  Use this skill when modeling complex multi-step accounting transactions —
6
6
  anything that spans multiple periods, involves changing amounts, or requires