node-autotask 0.17.0 → 0.18.0

package/ARCHITECTURE.md

@@ -396,8 +396,13 @@ The only total is `count()` (`/query/count`); "more rows exist" is `nextPageUrl
 The node follows `pageDetails.nextPageUrl` (an absolute vendor URL, POSTing the
 filter to it), and the SDK does the same: the walk is the fetcher
 (`BaseResource.fetchPage`), which POSTs the `QueryModel` body to
-`/V1.0/<E>/query` for page 1 (`MaxRecords = pageSize`) and POSTs the preserved
-filter to the ABSOLUTE cursor for every later page. The cursor is rebased to
+`/V1.0/<E>/query` for page 1 (`MaxRecords = pageSize`) and POSTs the SAME body
+(`buildQueryBody` — `MaxRecords`, `IncludeFields` with the `id` append, the
+preserved `filter`) to the ABSOLUTE cursor for every later page (issue #118:
+before the fix the continuation carried `{ filter }` alone and returned the
+full vendor model). Live-verified 2026-10-19: the vendor HONOURS
+`IncludeFields` on a continuation and IGNORES `MaxRecords` (its own 500-row
+page; the walk slices to its limit). The cursor is rebased to
 the client base URL (`cursorToPath`): same-origin cursors are stripped of the
 base and used verbatim, cross-origin ones are re-based onto the client base —
 mirroring the node's custom-zone behaviour. A page reports `hasMore` when
@@ -993,8 +998,9 @@ export const NoopLogger: Logger = {};
   envelope pass-through, per-envelope unwrap errors, error mapping per status (vendor error
   body formatting), retry/backoff on 429 with `Retry-After`, `Itgenatr005` as retryable
   `RateLimitError`, `AbortSignal` timeout, concurrency guard.
-- **Pagination (`pagination.test.ts`)**: multi-page cursor-follow walk (POST the filter
-  to the absolute `nextPageUrl`, rebased to the client base URL), early stop on short
+- **Pagination (`pagination.test.ts`)**: multi-page cursor-follow walk (POST the same
+  `QueryModel` body to the absolute `nextPageUrl`, rebased to the client base URL;
+  issue #118 pins the continuation's `IncludeFields`/`MaxRecords`), early stop on short
   page, **1000-page guard** (`PaginationLimitError`), `collectAll` equivalence.
 - **Query (`query.test.ts`)**: filter builder (13 operators, and/or wrapping, UDF flag),
   cap enforcement (500 OR-conditions, 1 UDF/query), GET-length measurement.

package/MCP_TOOL_CATALOG.json

@@ -1,7 +1,7 @@
 {
   "generatedBy": "scripts/build-tool-catalog.mjs",
-  "generatedAt": "2026-10-17T13:48:44.078Z",
-  "planHash": "bd88648453f58ede018062ce66acefacb672fecaa450af89f421057809971e14",
+  "generatedAt": "2026-10-19T05:26:26.501Z",
+  "planHash": "5176d37fc9bae34139c151ae0ea8336dab63a30382f04acbcaed0e24cdd71d5f",
   "metaTools": [
     {
       "name": "autotask_catalog",

package/MCP_TOOL_MANIFEST.md

@@ -1,6 +1,6 @@
 # MCP Tool Manifest — node-autotask
 
-<!-- GENERATED by scripts/project-mcp-tools.mjs at 2026-10-17T13:48:43.787Z — do not hand-edit. -->
+<!-- GENERATED by scripts/project-mcp-tools.mjs at 2026-10-19T05:26:26.653Z — do not hand-edit. -->
 
 Mechanical MCP projection of the capability registry (generator-design section 7, ARCHITECTURE section 19.5).
 Tool names are the plan `mcpTool` columns (entity-first `autotask_<entity>_<verb>`); descriptions are the
@@ -8,7 +8,7 @@ registry `purpose` + a mechanical bounds/flags sentence; annotations derive from
 Curation edits live ONLY in `MCP_TOOL_OVERRIDES.json` (records `{ tool, field, newValue, reason }`).
 
 Registry: 1213 operations; projected tools: 850 (one per registry op with a non-null `mcpTool`);
-not projected (catalog/describe material): 363. planHash: `bd88648453f58ede…`
+not projected (catalog/describe material): 363. planHash: `5176d37fc9bae341…`
 
 ## Always-on core tier (CORE_RULE — computed, never a hand list)
 
@@ -947,8 +947,8 @@ singleton, so no helper tier is expected there; G8, 2026-09-26.)
 
 ## Meta
 
-- generatedAt: 2026-10-17T13:48:43.787Z
-- planHash: bd88648453f58ede018062ce66acefacb672fecaa450af89f421057809971e14
+- generatedAt: 2026-10-19T05:26:26.653Z
+- planHash: 5176d37fc9bae34139c151ae0ea8336dab63a30382f04acbcaed0e24cdd71d5f
 - registry records: 1213
 - projected tools: 850
 - core tier: 15

package/N8N_MCP_MANIFEST.json

@@ -1,6 +1,6 @@
 {
   "schema": "node-autotask n8n consumer mcp projection v1",
-  "generatedAt": "2026-10-18T23:23:18.804Z",
+  "generatedAt": "2026-10-19T05:26:26.775Z",
   "generator": "scripts/project-n8n-mcp.mjs",
   "inputs": {
     "capabilities": "capabilities.json (the capability registry — the single source of truth)",
@@ -3667,6 +3667,6 @@
     "approvalGatedWrites": 2,
     "destructiveExcluded": 3
   },
-  "capabilitiesHash": "26246eab57263743486ab1afda89379b7b26462c592c5b104e727e337de92886",
+  "capabilitiesHash": "d30f65bc49ac2898667865b753c0f0cd3f0c951c337a1036b48b049e8c32c61a",
   "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-18T23:23:18.804Z — do not hand-edit. -->
+<!-- GENERATED by scripts/project-n8n-mcp.mjs at 2026-10-19T05:26:26.775Z — 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
@@ -282,6 +282,6 @@ only via a recorded change to `n8n-mcp.curation.json`.
 
 ## Meta
 
-- generatedAt: 2026-10-18T23:23:18.804Z
-- capabilitiesHash: 26246eab57263743486ab1afda89379b7b26462c592c5b104e727e337de92886
+- generatedAt: 2026-10-19T05:26:26.775Z
+- capabilitiesHash: d30f65bc49ac2898667865b753c0f0cd3f0c951c337a1036b48b049e8c32c61a
 - curationHash: e19117ce73e38d9aded3be7e7f077a4e185d2e10294622b76c17d67f63cf9e3b