node-autotask 0.21.0 → 0.23.0

package/N8N_MCP_MANIFEST.json

@@ -1,6 +1,6 @@
 {
   "schema": "node-autotask n8n consumer mcp projection v1",
-  "generatedAt": "2026-10-20T21:35:52.181Z",
+  "generatedAt": "2026-10-21T12:07:42.002Z",
   "generator": "scripts/project-n8n-mcp.mjs",
   "inputs": {
     "capabilities": "capabilities.json (the capability registry — the single source of truth)",
@@ -3688,10 +3688,26 @@
       "purpose": "Delete a time entry.",
       "confirmRule": "confirm: \"time_entries.delete\" (must equal the operation key exactly) — the call is refused pre-request without it",
       "note": "Excluded from the n8n consumer surface by curation (timeEntry: excludeDestructive: true). The capability exists on the canonical SDK MCP surface: the autotask_delete mode tool (confirm required) or the per-op tool. Re-include on the consumer surface only via a recorded change to n8n-mcp.curation.json."
+    },
+    {
+      "entity": "timeEntry",
+      "apiEntity": "time_entries",
+      "op": "time_entries.moveToTicket",
+      "verb": "moveToTicket",
+      "effect": "destructive",
+      "kind": "helper",
+      "flags": [],
+      "requiredArgs": [
+        "sourceId",
+        "toTicketId"
+      ],
+      "purpose": "Move a time entry to another ticket. The vendor update does NOT change ticketID, so this creates the record on the target ticket, verifies it, then deletes the source — with refusals for billed/approved/old sources and a twin check against duplicates.",
+      "confirmRule": "confirm: \"time_entries.moveToTicket\" (must equal the operation key exactly) — the call is refused pre-request without it",
+      "note": "Excluded from the n8n consumer surface by curation (timeEntry: excludeDestructive: true). The capability exists on the canonical SDK MCP surface: the autotask_delete mode tool (confirm required) or the per-op tool. Re-include on the consumer surface only via a recorded change to n8n-mcp.curation.json."
     }
   ],
   "stats": {
-    "registryRecords": 1213,
+    "registryRecords": 1216,
     "curatedEntities": 7,
     "includedEntities": 7,
     "readTools": 7,
@@ -3700,8 +3716,8 @@
     "readOperations": 84,
     "writeOperations": 21,
     "approvalGatedWrites": 2,
-    "destructiveExcluded": 3
+    "destructiveExcluded": 4
   },
-  "capabilitiesHash": "5dbc8f4b9a993123b72dd51983d26806476845e1148cac87f2962f91f614e37a",
+  "capabilitiesHash": "466880cd0488797463b1317445eea24047a9bfe7dd3b7f0711dda135e9869d62",
   "curationHash": "e19117ce73e38d9aded3be7e7f077a4e185d2e10294622b76c17d67f63cf9e3b"
 }

package/N8N_MCP_MANIFEST.md

@@ -1,6 +1,6 @@
 # N8N MCP Manifest — node-autotask (consumer projection)
 
-<!-- GENERATED by scripts/project-n8n-mcp.mjs at 2026-10-20T21:35:52.181Z — do not hand-edit. -->
+<!-- GENERATED by scripts/project-n8n-mcp.mjs at 2026-10-21T12:07:42.002Z — do not hand-edit. -->
 
 The n8n CONSUMER projection of the capability registry: the canonical source for what the
 n8n-side MCP tools must expose. The SDK is canonical — this is a projection of it, never a
@@ -266,10 +266,11 @@ only via a recorded change to `n8n-mcp.curation.json`.
 | contact | `contacts.delete` | idempotent+requiresApproval+sensitive | parentId, id | confirm: "contacts.delete" (must equal the operation key exactly) — the call is refused pre-request without it | Delete a contact. (under a company) |
 | companyLocation | `company_locations.delete` | idempotent+requiresApproval | parentId, id | confirm: "company_locations.delete" (must equal the operation key exactly) — the call is refused pre-request without it | Delete a company location. |
 | timeEntry | `time_entries.delete` | idempotent+requiresApproval | id | confirm: "time_entries.delete" (must equal the operation key exactly) — the call is refused pre-request without it | Delete a time entry. |
+| timeEntry | `time_entries.moveToTicket` | — | sourceId, toTicketId | confirm: "time_entries.moveToTicket" (must equal the operation key exactly) — the call is refused pre-request without it | Move a time entry to another ticket. The vendor update does NOT change ticketID, so this creates the record on the target ticket, verifies it, then deletes the source — with refusals for billed/approved/old sources and a twin check against duplicates. |
 
 ## Stats
 
-- registryRecords: 1213
+- registryRecords: 1216
 - curatedEntities: 7
 - includedEntities: 7
 - readTools: 7
@@ -278,10 +279,10 @@ only via a recorded change to `n8n-mcp.curation.json`.
 - readOperations: 84
 - writeOperations: 21
 - approvalGatedWrites: 2
-- destructiveExcluded: 3
+- destructiveExcluded: 4
 
 ## Meta
 
-- generatedAt: 2026-10-20T21:35:52.181Z
-- capabilitiesHash: 5dbc8f4b9a993123b72dd51983d26806476845e1148cac87f2962f91f614e37a
+- generatedAt: 2026-10-21T12:07:42.002Z
+- capabilitiesHash: 466880cd0488797463b1317445eea24047a9bfe7dd3b7f0711dda135e9869d62
 - curationHash: e19117ce73e38d9aded3be7e7f077a4e185d2e10294622b76c17d67f63cf9e3b

package/README.md

@@ -4,7 +4,7 @@ Fully-typed TypeScript SDK for the Autotask (Datto) PSA REST API. Zero runtime
 dependencies. Built for building MCP servers and integrations.
 
 The SDK is also the **deterministic execution layer for agents** (ARCHITECTURE
-section 19): a generated capability registry (1213 operations across the 121-entity
+section 19): a generated capability registry (1214 operations across the 121-entity
 MVP set), a mechanical MCP substrate (registry → manifest → overrides → core tier +
 catalog meta-tool), and a write governor (dry-run-first, destructive
 confirmation). The SDK boundary also redacts response field values — the
@@ -326,14 +326,14 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
      explicitly until the server 0.2.0 preset work, after which they can
      send nothing) so a tenant's repeated single-record reads stay cheap
      across requests.
-   Both MCP servers share `examples/mcp-register.ts` (one registration code
+   Both MCP servers share `examples/mcp-register.ts` (entry; implementation in `examples/mcp/`; one registration code
    path: manifest descriptions, zod v4 schemas, annotations derived from
    `effect` + `flags`, the mode-enforced `autotask_read` / `autotask_write` /
    `autotask_delete` governor dispatch), so the two
    transports expose the same surface by construction; `node
    scripts/check-mcp-surface.mjs` proves it (spawn, initialize, `tools/list` =
    15 core tools, descriptions verbatim vs the manifest). The future Autotask
-   MCP server package reuses `examples/mcp-register.ts` as its registration
+   MCP server package reuses `examples/mcp-register.ts` (`examples/mcp/*`) as its registration
    layer and swaps the examples' devDependencies (`@modelcontextprotocol/server`,
    `zod`) for runtime ones — the SDK itself remains MCP-import-free and
    zod-free. No dedicated write is in the core tier: reads travel through
@@ -344,22 +344,22 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
    governor place: `src/operations/invoke.ts`).
 
    **Harness approval policy (recommended).** Require approval on every tool
-   whose MCP annotation is `readOnlyHint !== true` — today exactly **254
-   tools**: the 252 dedicated write/delete tools (198 `effect=write` + 54
+   whose MCP annotation is `readOnlyHint !== true` — today exactly **256
+   tools**: the 254 dedicated write/delete tools (198 `effect=write` + 56
    `effect=destructive`, every one of them has a dedicated tool) +
-   `autotask_write` + `autotask_delete`. The remaining **601 tools** (the 588
+   `autotask_write` + `autotask_delete`. The remaining **602 tools** (the 589
    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 — pinned by the test inventory). Refined class for the
-   highest-risk ops: the **55 tools with `destructiveHint: true`** (54
+   highest-risk ops: the **57 tools with `destructiveHint: true`** (56
    dedicated delete tools + `autotask_delete`) additionally require
    `confirm === <operation key>` even inside `autotask_delete`, and the 3
    approval-gated writes (`configuration_items.moveConfigurationItem`,
    `contacts.moveToCompany`, `resources.transferOwnership`) require the same
    confirm inside `autotask_write`. Migration: `autotask_invoke` is REPLACED
    by `autotask_read`/`autotask_write`/`autotask_delete` — update harness
-   config (approve the 254 above) and remove any `autotask_invoke` entry. The
+   config (approve the 256 above) 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.
 
@@ -519,7 +519,7 @@ node-parity paths the vendored swagger lacks, all UNVERIFIED-live this run), and
 | `npm run capabilities:check` | `scripts/check-capabilities.mjs` — the batch gate (missing/incomplete/stale records → exit 1) |
 | `npm run public-surface` | `scripts/public-surface.mjs` — capture (`--write`) / verify the public API surface baseline; default mode fails on unannounced removals, **and** checks the BUILT surface: every tsup entry has a matching `exports` key (and vice versa), every declared target was emitted and loads (ESM+CJS), and no runtime dependency leaks into `dist` |
 | `npm run live-smoke` | `scripts/live-smoke.mjs` — read-only live smoke: 5 vendor probes (5-6 wire calls worst case: 4 GET + 1 bounded query that may walk a 2nd, empty page) + a zero-network shape guard; `--dry` prints the plan with no calls (DRY-RUN-ONLY verdict, exit 0); live via `AUTOTASK_*` env — missing/partial credentials hard-fail exit 2 |
-| `npm run live-coverage` | `scripts/live-coverage.mjs` — the live coverage sweep over all 1213 registry ops (`--dry`: full call plan, no calls; live: bounded reads for real, mutations `dryRun: true` only — zero mutating requests, every governor-gated row (the 54 delete dry-runs included) routed through invoke with `confirm`; budget <= 1159 plan-honest / <= 1311 wire-honest worst case) |
+| `npm run live-coverage` | `scripts/live-coverage.mjs` — the live coverage sweep over all 1214 registry ops (`--dry`: full call plan, no calls; live: bounded reads for real, mutations `dryRun: true` only — zero mutating requests, every governor-gated row (the 54 delete dry-runs included) routed through invoke with `confirm`; budget <= 1160 plan-honest / <= 1314 wire-honest worst case) |
 | `npm run mcp:project` | `scripts/project-mcp-tools.mjs` — mechanical MCP projection → `MCP_TOOL_MANIFEST.md` (`:check` verifies) |
 | `npm run n8n:project` / `n8n:project:check` | `scripts/project-n8n-mcp.mjs` — the n8n consumer projection from the SAME registry → `N8N_MCP_MANIFEST.json`/`.md` (`--check` rebuilds and diffs; the gate is wired into `verify`) |
 | `npm run catalog:build` / `catalog:check` | `scripts/build-tool-catalog.mjs` — the catalog meta-tool row data → `MCP_TOOL_CATALOG.json` + mechanical CORE profile (`--check` verifies drift) |