bkper 4.16.6 → 4.16.8

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.
@@ -539,7 +539,9 @@ See [Event Handlers](https://bkper.com/docs/build/apps/event-handlers.md) for de
539
539
 
540
540
  ### Properties schema
541
541
 
542
- The `propertiesSchema` field defines autocomplete suggestions for custom properties in the Bkper UI, helping users discover the correct property keys and values for your app:
542
+ The `propertiesSchema` field defines autocomplete suggestions for custom properties in the Bkper UI, helping users discover the correct property keys and values for your app.
543
+
544
+ Suggested keys must follow the same custom property rules as user-entered keys, including the 30-character maximum after normalization.
543
545
 
544
546
  ```yaml
545
547
  propertiesSchema:
package/lib/docs/taxes.md CHANGED
@@ -14,20 +14,22 @@ Prefer existing trusted routes before creating new ones. If none exists, recomme
14
14
 
15
15
  ## Loading tax rules
16
16
 
17
- When no trusted local tax route exists, or when the user asks to load jurisdiction rules, use external tax-rule libraries only as discovery sources. They may identify candidate rates, thresholds, deadlines, forms, classifications, and citations, but they are not a final computation route.
17
+ When no trusted local tax route exists, or when the user asks to load jurisdiction rules, use external tax-rule libraries only as live discovery sources. They may identify candidate rates, thresholds, deadlines, forms, classifications, and citations, but they are not a final computation route. Figures derived from bundle data remain provisional until reviewed by a local qualified accountant or advisor.
18
18
 
19
- Do not produce tax numbers from loaded rules until the rule source, tax period, assumptions, and Bkper mappings have been reviewed or approved.
19
+ Do not produce tax numbers from loaded rules until the rule source, tax period, assumptions, and Bkper mappings have been reviewed or approved. If the relevant bundle or skill is not accountant-verified, or verifier status is missing or pending, surface that status to the user and label outputs exploratory / provisional.
20
20
 
21
21
  Preferred non-MCP OpenAccountants route:
22
22
 
23
- 1. Start from `https://www.openaccountants.com/llms.txt`.
24
- 2. Resolve the jurisdiction code, such as `BR`, `GB`, `DE`, `US-CA`, or `CA-ON`.
25
- 3. Fetch `https://www.openaccountants.com/api/bundle/<CODE>`.
26
- 4. Do not use MCP unless the user explicitly requests it.
27
- 5. Record source URL, retrieval date, tax year, quality tier, verifier if present, and citations.
23
+ 1. Resolve the jurisdiction code or name, such as `BR`, `GB`, `DE`, `US-CA`, `CA-ON`, or `brazil`.
24
+ 2. Fetch `https://www.openaccountants.com/api/bundle/<CODE_OR_NAME>` live for each rule-loading run; do not compute from cached bundle content.
25
+ 3. Do not use MCP unless the user explicitly requests it.
26
+ 4. If the bundle cannot be resolved, ask the user for the exact jurisdiction or source URL instead of guessing.
27
+ 5. Record source URL, retrieval date, tax year, quality tier, verifier if present, and citations, and surface the quality tier to the user.
28
28
  6. Map rules only to user-approved Bkper Groups, Accounts, properties, or hashtags.
29
29
 
30
- Example: for Brazil, resolve `BR` and fetch `https://www.openaccountants.com/api/bundle/BR`, then clarify whether the scope is IRPF, Carnê-Leão, payroll, indirect tax, e-invoice compliance, or another Brazil tax area.
30
+ Example: for Brazil, fetch `https://www.openaccountants.com/api/bundle/BR` or `https://www.openaccountants.com/api/bundle/brazil`, then clarify whether the scope is IRPF, Carnê-Leão, payroll, indirect tax, e-invoice compliance, or another Brazil tax area.
31
+
32
+ For multi-layer jurisdictions, first determine whether the scope is national/federal-only, sub-jurisdiction-only, or both. Use a national/federal code such as `US` or `US-FED` for US federal-only rules. Use structured sub-jurisdiction codes such as `US-CA` for California or `CA-ON` for Ontario when state or provincial rules are relevant. If both layers matter, load and record each applicable bundle, and verify that the returned bundle title matches the requested layer.
31
33
 
32
34
  ## Bkper tax semantics
33
35
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bkper",
3
- "version": "4.16.6",
3
+ "version": "4.16.8",
4
4
  "description": "Command line client for Bkper",
5
5
  "bin": {
6
6
  "bkper": "./lib/cli.js"