jaz-clio 5.48.2 → 5.49.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.
- package/assets/skills/api/SKILL.md +1 -1
- package/assets/skills/cli/SKILL.md +1 -1
- package/assets/skills/cli/references/error-recovery.md +2 -2
- package/assets/skills/conversion/SKILL.md +1 -1
- package/assets/skills/jaz-kit/SKILL.md +1 -1
- package/assets/skills/jaz-pseudo-sql/SKILL.md +1 -1
- package/assets/skills/jaz-pseudo-sql/references/error-catalog.md +22 -0
- package/assets/skills/jobs/SKILL.md +1 -1
- package/assets/skills/transaction-recipes/SKILL.md +1 -1
- package/cli.mjs +251 -251
- package/package.json +1 -1
|
@@ -23,7 +23,7 @@
|
|
|
23
23
|
| Error | Cause | Fix |
|
|
24
24
|
|-------|-------|-----|
|
|
25
25
|
| `Multiple contacts match 'Acme'` | Fuzzy match found 2+ candidates above threshold | Use exact billingName or UUID |
|
|
26
|
-
| `Contact not found: 'xyz'` | No match in org's contact list | Run `clio contacts search xyz` to check spelling |
|
|
26
|
+
| `Contact not found: 'xyz'` | No match in org's contact list | Run `clio contacts search --name xyz` to check spelling |
|
|
27
27
|
| `Account not found: 'xyz'` | No matching account name or code | Run `clio accounts list --json` to see available accounts |
|
|
28
28
|
| `Bank account not found` | Name doesn't match any bank-type account | Run `clio bank accounts --json` for exact names |
|
|
29
29
|
| `Tax profile not found` | No match on tax profile name or code | Run `clio tax-profiles list --json` for available profiles |
|
|
@@ -98,7 +98,7 @@ echo $JAZ_ORG # Check for pinned org
|
|
|
98
98
|
|
|
99
99
|
**Entity not found?** Search before creating:
|
|
100
100
|
```bash
|
|
101
|
-
clio contacts search "partial name" --json | jq '.data[] | {name, resourceId}'
|
|
101
|
+
clio contacts search --name "partial name" --json | jq '.data[] | {name, resourceId}'
|
|
102
102
|
clio accounts list --json | jq '.data[] | {name, code: .accountCode, id: .resourceId}'
|
|
103
103
|
```
|
|
104
104
|
|
|
@@ -31,6 +31,28 @@ Surfaces when the query is syntactically valid but semantically rejected — wro
|
|
|
31
31
|
| `a query must SELECT FROM at least one table` | `SELECT 1` (constant-only) | Add `FROM <table>` from the curated set. |
|
|
32
32
|
| `unknown table "<name>"` (note: lowercased) | Table not in curated schema | Call `get_pseudo_sql_schema` for the live inventory. Common typos: plural vs singular (`invoice` vs `invoices`), wrong case. |
|
|
33
33
|
|
|
34
|
+
## `PSEUDOSQL_DISABLED` (engine switched off)
|
|
35
|
+
|
|
36
|
+
Surfaces on **both** `/sql-query/preview` and `/sql-query/export` when the query engine is not
|
|
37
|
+
running. Delivered as a **422**, which reads like a validation failure and is not one.
|
|
38
|
+
|
|
39
|
+
| Message | Trigger | Recovery |
|
|
40
|
+
|---|---|---|
|
|
41
|
+
| `The SQL query feature is not available.` | The reporting service has no read-only query pool: its connection string is unset for this deployment, or the pool failed to build, ping, or match the catalog at startup | None available to you. Do not rewrite the query. Use the report tools (`generate_report`, the operational report family) and tell the user the engine is off. |
|
|
42
|
+
|
|
43
|
+
**The catalog stays readable while the engine is off.** `get_pseudo_sql_schema` is served from a
|
|
44
|
+
static in-process snapshot and never touches the query pool, so it keeps returning the full table,
|
|
45
|
+
join and function list. Measured on 2026-09-06: the schema endpoint returned 79 tables / 104 joins
|
|
46
|
+
/ 47 functions in the same run where every preview and export returned `PSEUDOSQL_DISABLED`.
|
|
47
|
+
|
|
48
|
+
So **a table appearing in the catalog is not evidence you can query it.** Confirming a table exists
|
|
49
|
+
before querying is a reasonable habit and it will not detect this state. The only signal is the
|
|
50
|
+
error itself.
|
|
51
|
+
|
|
52
|
+
This is not an organization setting and not a plan entitlement — it is a platform deployment
|
|
53
|
+
change, so neither you, the user, nor an organization admin can turn it on. Retrying later is only
|
|
54
|
+
worth it if someone has said the engine is being re-enabled.
|
|
55
|
+
|
|
34
56
|
## Export-specific terminal states
|
|
35
57
|
|
|
36
58
|
The `export_pseudo_sql` + `get_pseudo_sql_export` flow uses status enums (NOT error codes). Terminal states:
|