node-autotask 0.65.0 → 0.67.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.
Files changed (34) hide show
  1. package/CHANGELOG.md +25 -0
  2. package/MCP_TOOL_CATALOG.json +34 -14
  3. package/README.md +1 -1
  4. package/capabilities.json +157 -96
  5. package/dist/capabilities-data.js +156 -95
  6. package/dist/capabilities.cjs +4 -4
  7. package/dist/capabilities.js +1 -1
  8. package/dist/{chunk-N4EO3KAY.js → chunk-4GH73U2I.js} +3 -3
  9. package/dist/{chunk-UHV7SAX6.cjs → chunk-54L7KKUD.cjs} +31 -31
  10. package/dist/{chunk-WKR5IJEC.cjs → chunk-7GBOQ7YA.cjs} +3 -3
  11. package/dist/{chunk-M63TK4ZH.cjs → chunk-C7M7PXLW.cjs} +175 -179
  12. package/dist/{chunk-MXLE2F5G.js → chunk-EXLJHU5W.js} +4 -8
  13. package/dist/{chunk-ULI4UUB3.js → chunk-N7WB65IS.js} +391 -406
  14. package/dist/{chunk-C73NILBZ.js → chunk-UCPSQ6GN.js} +2 -2
  15. package/dist/{chunk-NTHEFYA7.cjs → chunk-VO4ABDZA.cjs} +396 -411
  16. package/dist/{index-vcFKvZqm.d.ts → index-CYlKHo5N.d.ts} +10 -24
  17. package/dist/{index-CRVQBajX.d.cts → index-D_1wP3Je.d.cts} +10 -24
  18. package/dist/index.cjs +84 -84
  19. package/dist/index.d.cts +2 -2
  20. package/dist/index.d.ts +2 -2
  21. package/dist/index.js +5 -5
  22. package/dist/operations/index.cjs +50 -50
  23. package/dist/operations/index.d.cts +3 -3
  24. package/dist/operations/index.d.ts +3 -3
  25. package/dist/operations/index.js +2 -2
  26. package/dist/pool.cjs +8 -8
  27. package/dist/pool.js +4 -4
  28. package/dist/resources/index.cjs +27 -27
  29. package/dist/resources/index.d.cts +1 -1
  30. package/dist/resources/index.d.ts +1 -1
  31. package/dist/resources/index.js +3 -3
  32. package/docs/API.md +2 -2
  33. package/docs/VENDOR-QUIRKS.md +50 -34
  34. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -7,6 +7,31 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.67.0] - 2026-11-17
11
+
12
+ ### Fixed
13
+
14
+ - Prevent zone-scoped capability guidance with a structured-quirk hygiene check that covers numeric zone identifiers and keeps region/date provenance in evidence (#451). Remove the remaining zone qualifier from the contacts `isActive` wire-type guidance while preserving the field constraint and its original evidence. Shared API contracts do not imply shared tenant inventory or API-user visibility.
15
+
16
+ ## [0.66.0] - 2026-11-17
17
+
18
+ ### Fixed
19
+
20
+ - Expose the vendor-supported `currencies.update` operation (#448), including the generated registry, MCP and n8n projections. Partial updates use a fresh read and the existing collection PUT merge; the write is marked account-wide. Currency create and delete remain unsupported by the vendor.
21
+
22
+ - Stop declaring documented opportunity and attachment creates impossible based on unsuccessful
23
+ reference-tenant probes (#447). Those attachment/opportunity rows now report `blocker.kind: unknown`,
24
+ retain `unproven: true` and their error evidence, and omit the previous `unsatisfiableViaApi: true`
25
+ flag. Consumers should treat retained `blind-parent` / `blind-reference` kinds as conditional
26
+ diagnostics, never as a current-user permission or inventory check.
27
+ Product and configuration-item guidance no longer infers tenant inventory or asset capability from
28
+ an empty product count. Configuration-item profiles no longer mark successfully returned product
29
+ associations blind merely because asset creates require a productID. Existing API operations
30
+ remain reachable through the same governed paths. Static parent/reference guidance, visibility
31
+ warnings and discovery notes now distinguish prior observations from current-tenant permissions
32
+ and inventory; known valid ids remain usable. The association-target plan and documentation
33
+ identify Vendor references as vendor-type Companies and retain official entity documentation links.
34
+
10
35
  ## [0.65.0] - 2026-11-17
11
36
 
12
37
  ### Fixed
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "generatedBy": "scripts/build-tool-catalog.mjs",
3
- "generatedAt": "2026-11-17T02:57:14.178Z",
4
- "planHash": "546e9de78d62f2c30190c1bb82f89be73f9cc0a75d633d771956566c78f4efeb",
3
+ "generatedAt": "2026-11-17T06:07:35.025Z",
4
+ "planHash": "448bad244d0dfa1f8af0f6dfa4bc1a080ca60a114dc10366660585ff2dbc3e55",
5
5
  "metaTools": [
6
6
  {
7
7
  "name": "autotask_catalog",
@@ -51,7 +51,7 @@
51
51
  {
52
52
  "name": "autotask_read",
53
53
  "title": "Read One Registry Operation (read mode)",
54
- "description": "Route an effect=read registry operation by its exact name (never fuzzy, never a tool name): the 390 field/entity/UDF-info reads (getEntityInfo/getFieldInfo/getUdfInfo) have no dedicated tool and ride this one, and any read op is routable. For field discovery use operations.fieldCatalog (compact) instead of per-resource getFieldInfo (full dump). Read-only by construction — every op it can route is effect=read (zero mutating requests), and a write or delete op is refused BEFORE any request (cross-mode refusal; the message names the correct tool). Reads have no dry run (a read with dry_run: true is refused). Harness approval policy: approve every tool with readOnlyHint !== true (exactly 251 today); the 610 readOnlyHint: true tools — including this one — are safe ungated; the 57 destructiveHint: true tools (56 dedicated delete tools + autotask_delete) require confirm === the operation key. Migration: autotask_invoke is REPLACED by autotask_read/autotask_write/autotask_delete — update harness config. For query/count ops args[0] is a params object (filter/limit); call autotask_describe first for the exact arg shape and filter grammar. The argument set is CLOSED at the top level: an unknown argument is refused before any request, with a typed error naming the key and the valid keys.",
54
+ "description": "Route an effect=read registry operation by its exact name (never fuzzy, never a tool name): the 390 field/entity/UDF-info reads (getEntityInfo/getFieldInfo/getUdfInfo) have no dedicated tool and ride this one, and any read op is routable. For field discovery use operations.fieldCatalog (compact) instead of per-resource getFieldInfo (full dump). Read-only by construction — every op it can route is effect=read (zero mutating requests), and a write or delete op is refused BEFORE any request (cross-mode refusal; the message names the correct tool). Reads have no dry run (a read with dry_run: true is refused). Harness approval policy: approve every tool with readOnlyHint !== true (exactly 252 today); the 610 readOnlyHint: true tools — including this one — are safe ungated; the 57 destructiveHint: true tools (56 dedicated delete tools + autotask_delete) require confirm === the operation key. Migration: autotask_invoke is REPLACED by autotask_read/autotask_write/autotask_delete — update harness config. For query/count ops args[0] is a params object (filter/limit); call autotask_describe first for the exact arg shape and filter grammar. The argument set is CLOSED at the top level: an unknown argument is refused before any request, with a typed error naming the key and the valid keys.",
55
55
  "input": {
56
56
  "operation": {
57
57
  "type": "string",
@@ -71,7 +71,7 @@
71
71
  {
72
72
  "name": "autotask_write",
73
73
  "title": "Write One Registry Operation (write mode)",
74
- "description": "Route an effect=write registry operation by its exact name (never fuzzy, never a tool name), dry-run-first: the first call always travels dry_run: true (the pinned DryRunResult envelope, simulated: true — the mutating request is never issued); pass dry_run: false to apply. A read or delete op is refused BEFORE any request (cross-mode refusal; the message names the correct tool). The 2 approval-gated writes (configuration_items.moveConfigurationItem, contacts.moveToCompany) additionally require confirm === the operation key, in BOTH dry-run and apply mode. Harness approval policy: this tool is one of the 251 tools that require approval (readOnlyHint !== true); the 610 readOnlyHint: true tools are safe ungated, and the 57 destructiveHint: true tools (56 dedicated delete tools + autotask_delete) require confirm === the operation key. Migration: autotask_invoke is REPLACED by autotask_read/autotask_write/autotask_delete — update harness config. For query/count ops args[0] is a params object (filter/limit); call autotask_describe first for the exact arg shape and filter grammar. The argument set is CLOSED at the top level: an unknown argument is refused before any request, with a typed error naming the key and the valid keys.",
74
+ "description": "Route an effect=write registry operation by its exact name (never fuzzy, never a tool name), dry-run-first: the first call always travels dry_run: true (the pinned DryRunResult envelope, simulated: true — the mutating request is never issued); pass dry_run: false to apply. A read or delete op is refused BEFORE any request (cross-mode refusal; the message names the correct tool). The 2 approval-gated writes (configuration_items.moveConfigurationItem, contacts.moveToCompany) additionally require confirm === the operation key, in BOTH dry-run and apply mode. Harness approval policy: this tool is one of the 252 tools that require approval (readOnlyHint !== true); the 610 readOnlyHint: true tools are safe ungated, and the 57 destructiveHint: true tools (56 dedicated delete tools + autotask_delete) require confirm === the operation key. Migration: autotask_invoke is REPLACED by autotask_read/autotask_write/autotask_delete — update harness config. For query/count ops args[0] is a params object (filter/limit); call autotask_describe first for the exact arg shape and filter grammar. The argument set is CLOSED at the top level: an unknown argument is refused before any request, with a typed error naming the key and the valid keys.",
75
75
  "input": {
76
76
  "operation": {
77
77
  "type": "string",
@@ -101,7 +101,7 @@
101
101
  {
102
102
  "name": "autotask_delete",
103
103
  "title": "Delete One Registry Operation (delete mode)",
104
- "description": "Route an effect=destructive (delete) registry operation by its exact name (never fuzzy, never a tool name), dry-run-first: the first call always travels dry_run: true (the pinned DryRunResult envelope, simulated: true); pass dry_run: false to apply. confirm === the operation key is REQUIRED for every delete (all 56), in BOTH dry-run and apply mode — the deliberate act is the call, not the delete. A read or write op is refused BEFORE any request (cross-mode refusal; the message names the correct tool). Harness approval policy: this tool is one of the 57 destructiveHint: true tools that require approval + confirm; approve every tool with readOnlyHint !== true (exactly 251 today); the 610 readOnlyHint: true tools are safe ungated. Migration: autotask_invoke is REPLACED by autotask_read/autotask_write/autotask_delete — update harness config. The argument set is CLOSED at the top level: an unknown argument is refused before any request, with a typed error naming the key and the valid keys.",
104
+ "description": "Route an effect=destructive (delete) registry operation by its exact name (never fuzzy, never a tool name), dry-run-first: the first call always travels dry_run: true (the pinned DryRunResult envelope, simulated: true); pass dry_run: false to apply. confirm === the operation key is REQUIRED for every delete (all 56), in BOTH dry-run and apply mode — the deliberate act is the call, not the delete. A read or write op is refused BEFORE any request (cross-mode refusal; the message names the correct tool). Harness approval policy: this tool is one of the 57 destructiveHint: true tools that require approval + confirm; approve every tool with readOnlyHint !== true (exactly 252 today); the 610 readOnlyHint: true tools are safe ungated. Migration: autotask_invoke is REPLACED by autotask_read/autotask_write/autotask_delete — update harness config. The argument set is CLOSED at the top level: an unknown argument is refused before any request, with a typed error naming the key and the valid keys.",
105
105
  "input": {
106
106
  "operation": {
107
107
  "type": "string",
@@ -3227,6 +3227,26 @@
3227
3227
  "reachReason": null,
3228
3228
  "boundedAlternative": null
3229
3229
  },
3230
+ {
3231
+ "operation": "currencies.update",
3232
+ "core": false,
3233
+ "tool": "autotask_currency_update",
3234
+ "purpose": "Update a currency, including its exchange rate and display settings.",
3235
+ "preferredWhen": "Change supported fields on an existing currency; the vendor specification does not define currency create or delete operations.",
3236
+ "backingOperation": "currencies.update",
3237
+ "effect": "write",
3238
+ "dryRunFirst": true,
3239
+ "confirm": false,
3240
+ "requiredArgs": [
3241
+ "id",
3242
+ "data"
3243
+ ],
3244
+ "tier": "advanced",
3245
+ "reachable": true,
3246
+ "reach": "dedicated tool",
3247
+ "reachReason": null,
3248
+ "boundedAlternative": null
3249
+ },
3230
3250
  {
3231
3251
  "operation": "departments.count",
3232
3252
  "core": false,
@@ -17902,7 +17922,7 @@
17902
17922
  "reachReason": null,
17903
17923
  "boundedAlternative": null,
17904
17924
  "writeQuirks": {
17905
- "dateConventions": "date convention (live-proven on one reference zone, not universal): startDate and endDate are date-only at 00:00Z; tickets.dueDateTime is a true UTC instant."
17925
+ "dateConventions": "date convention (verify against current field metadata): startDate and endDate are date-only at 00:00Z; tickets.dueDateTime is a true UTC instant."
17906
17926
  }
17907
17927
  },
17908
17928
  {
@@ -18108,7 +18128,7 @@
18108
18128
  "reachReason": null,
18109
18129
  "boundedAlternative": null,
18110
18130
  "writeQuirks": {
18111
- "dateConventions": "date convention (live-proven on one reference zone, not universal): startDate and endDate are date-only at 00:00Z; tickets.dueDateTime is a true UTC instant."
18131
+ "dateConventions": "date convention (verify against current field metadata): startDate and endDate are date-only at 00:00Z; tickets.dueDateTime is a true UTC instant."
18112
18132
  }
18113
18133
  },
18114
18134
  {
@@ -22649,8 +22669,8 @@
22649
22669
  "operation": "operations.createGuidance",
22650
22670
  "core": false,
22651
22671
  "tool": "autotask_create_guidance",
22652
- "purpose": "Answer 'what does the vendor ACTUALLY require to create a record here?' in one ZERO-wire call: the 92 campaign-decoded create entities — the live-proven required-field prefix, the structured blocker (the exact wall class), the exact vendor message text, the remedy, and the delete boundary — instead of rediscovering it one failed write at a time.",
22653
- "preferredWhen": "Before writing any create on a resource whose spec lists few/no required fields: check the catalog first (free) — the campaign already paid the discovery cost (461 classified write requests). For the served relationship facts of ONE resource (children + scoped ops + natural keys + the 12 hand-authored zone facts) use operations.relationshipMap.",
22672
+ "purpose": "Read static creation requirements, prior validation findings and unproven input guidance. This is not a live test of current-tenant capability, inventory or permissions.",
22673
+ "preferredWhen": "Consult before a create, together with current field metadata and a governed preview; never substitute static reference-tenant observations for a live permission or inventory check.",
22654
22674
  "backingOperation": "operations.createGuidance",
22655
22675
  "effect": "read",
22656
22676
  "dryRunFirst": false,
@@ -22772,8 +22792,8 @@
22772
22792
  "operation": "operations.relationshipMap",
22773
22793
  "core": false,
22774
22794
  "tool": "autotask_relationship_map",
22775
- "purpose": "Describe one resource's full relationship surface in a single ZERO-wire call: its parent, its children (with the scoped-op presence per child), its natural lookup keys, its pinned blind surfaces, and the zone-verified create required sets + quirks.",
22776
- "preferredWhen": "The first call when planning any multi-step composition (what exists under this resource, what a create requires, which surfaces are blind) — zero wire, so it is free to consult before every plan. For a live record, use the resource's read ops.",
22795
+ "purpose": "Describe a resource’s SDK-covered parent/child operations, lookup keys and static create guidance without a vendor call. Current-user visibility and tenant inventory require live reads.",
22796
+ "preferredWhen": "Before composing related operations; use live read operations to establish the current tenant’s records and API-user visibility.",
22777
22797
  "backingOperation": "operations.relationshipMap",
22778
22798
  "effect": "read",
22779
22799
  "dryRunFirst": false,
@@ -22919,10 +22939,10 @@
22919
22939
  }
22920
22940
  ],
22921
22941
  "counts": {
22922
- "registryOperations": 1246,
22942
+ "registryOperations": 1247,
22923
22943
  "coreOperations": 10,
22924
- "catalogRows": 1246,
22925
- "withTool": 856,
22944
+ "catalogRows": 1247,
22945
+ "withTool": 857,
22926
22946
  "readModeOnly": 390,
22927
22947
  "neverExposed": 0,
22928
22948
  "metaTools": 5
package/README.md CHANGED
@@ -342,7 +342,7 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
342
342
  governor place: `src/operations/invoke.ts`).
343
343
 
344
344
  <!-- BEGIN GENERATED:approval-policy -->
345
- **Harness approval policy (recommended).** Require approval on every tool whose MCP annotation is `readOnlyHint !== true` — today exactly **251 tools**: the 249 dedicated write/delete tools (193 `effect=write` + 56 `effect=destructive`, every one of them has a dedicated tool) + `autotask_write` + `autotask_delete`. The remaining **610 tools** (the 597 dedicated read tools + the 10 core read tools + `autotask_read` + `autotask_catalog` + `autotask_describe`) all carry `readOnlyHint: true` and are safe ungated: every op they can route is `effect=read` (zero mutating requests). Refined class for the highest-risk ops: the **57 tools with `destructiveHint: true`** (56 dedicated delete tools + `autotask_delete`) additionally require `confirm === <operation key>` even inside `autotask_delete`. The approval-gated writes (`configuration_items.moveConfigurationItem`, `contacts.moveToCompany`) require the same confirm inside `autotask_write`. Migration: `autotask_invoke` is REPLACED by `autotask_read`/`autotask_write`/`autotask_delete` — update harness config and remove any `autotask_invoke` entry. The rule is derivable from the registry `effect` column and the mode tools’ fixed annotations; it never needs a hand-maintained name list.
345
+ **Harness approval policy (recommended).** Require approval on every tool whose MCP annotation is `readOnlyHint !== true` — today exactly **252 tools**: the 250 dedicated write/delete tools (194 `effect=write` + 56 `effect=destructive`, every one of them has a dedicated tool) + `autotask_write` + `autotask_delete`. The remaining **610 tools** (the 597 dedicated read tools + the 10 core read tools + `autotask_read` + `autotask_catalog` + `autotask_describe`) all carry `readOnlyHint: true` and are safe ungated: every op they can route is `effect=read` (zero mutating requests). Refined class for the highest-risk ops: the **57 tools with `destructiveHint: true`** (56 dedicated delete tools + `autotask_delete`) additionally require `confirm === <operation key>` even inside `autotask_delete`. The approval-gated writes (`configuration_items.moveConfigurationItem`, `contacts.moveToCompany`) require the same confirm inside `autotask_write`. Migration: `autotask_invoke` is REPLACED by `autotask_read`/`autotask_write`/`autotask_delete` — update harness config and remove any `autotask_invoke` entry. The rule is derivable from the registry `effect` column and the mode tools’ fixed annotations; it never needs a hand-maintained name list.
346
346
  <!-- END GENERATED:approval-policy -->
347
347
  **Provider tool-search interop.** Hosts with provider-native tool search
348
348
  (OpenAI `type: "tool_search"` / `defer_loading`; Anthropic's tool search