node-autotask 0.25.0 → 0.27.0

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 (1214 operations across the 121-entity
+section 19): a generated capability registry (1275 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
@@ -288,7 +288,9 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
    destructive ones; the plan-derived `untrustedFields` read tools additionally
    carry the untrusted-content sentence + the field list as the `x-untrusted`
    output-schema extension (issue #1 — externally-sourced free text is
-   marker-wrapped in the projection; the SDK primitives stay raw).
+   marker-wrapped in the projection; the SDK primitives stay raw); the
+   cross-resource tools carry `["*"]` rather than the union (the per-resource
+   lists are the authority, and the served surface has a hard token budget).
 3. **Overrides** — [`MCP_TOOL_OVERRIDES.json`](./MCP_TOOL_OVERRIDES.json): the ONLY
    place a curation delta may live (`{ tool, field, newValue, reason }`); silent
    divergence between projection and curation is a defect; the delta file is reviewed
@@ -344,10 +346,10 @@ 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 **256
-   tools**: the 254 dedicated write/delete tools (198 `effect=write` + 56
+   whose MCP annotation is `readOnlyHint !== true` — today exactly **267
+   tools**: the 265 dedicated write/delete tools (209 `effect=write` + 56
    `effect=destructive`, every one of them has a dedicated tool) +
-   `autotask_write` + `autotask_delete`. The remaining **603 tools** (the 590
+   `autotask_write` + `autotask_delete`. The remaining **629 tools** (the 616
    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
@@ -359,7 +361,7 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
    `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 256 above) and remove any `autotask_invoke` entry. The
+   config (approve the 267 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.
 
@@ -413,7 +415,7 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
    source.
 
 7. **Agent QoL surface (the stage-12 issue wave, live-verified on ww29)** —
-   the zero-wire planning reads `operations.blindSurfaces` (the 116-surface
+   the zero-wire planning reads `operations.blindSurfaces` (the 124-surface
    blind/data inventory) and `operations.createGuidance` (per-child zone
    facts with verbatim vendor evidence), the bounded live
    `operations.probeReachability` sweep (confirm-gated, over-cap refuses),
@@ -453,7 +455,7 @@ The SDK ships the mechanical substrate, not a server (no MCP imports, no zod):
 ## Partial-update merge (collectionUpdate resources)
 
 The vendor's top-level **collection PUT** validates the **FULL model**: a partial body is
-rejected with a 500 `Missing Required Field`. This applies to the **40 top-level update ops**
+rejected with a 500 `Missing Required Field`. This applies to the **45 top-level update ops**
 whose spec defines no item-path write (the `collectionUpdate` class — the flag is derived from
 `api-docs.json` by the shared `scripts/lib/collection-update.mjs`, stamped into both the
 generated resource config and the registry record's `metadata.collectionUpdate`, and pinned by
@@ -519,7 +521,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 1217 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 <= 1161 plan-honest / <= 1315 wire-honest worst case) |
+| `npm run live-coverage` | `scripts/live-coverage.mjs` — the live coverage sweep over all 1275 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 <= 1161 plan-honest / <= 1315 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) |