chore(deps): update dependency @types/node to v22.20.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	22.19.17 → 22.20.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[doubleword-code]

Summary

This PR is an automated Renovate dependency update that bumps @types/node from version 22.19.17 to 22.19.18 in the TypeScript SDK's package-lock.json. This is a patch-level update containing type definition fixes/improvements for Node.js APIs.

Verdict: Approved — This is a routine, low-risk maintenance update with no source code changes required.

Research notes

• @types/node v22.19.18: Patch release from DefinitelyTyped containing minor type definition corrections. No breaking changes expected at patch level.
• CI compatibility: The CI workflow (.github/workflows/ci.yml) uses Node.js 22 (node-version: "22"), which aligns with the @types/node v22.x series.
• Package.json constraint: The ^22.0.0 semver range in package.json permits this update automatically.

Suggested next steps

1. Merge as-is — No action required. The update is safe and within the declared dependency range.
2. Verify CI passes — Ensure the TypeScript job (npm run typecheck and npm run build) completes successfully with the updated types.

General findings

The package-lock.json diff includes additional metadata changes beyond the version bump:

• Added bin field to the root autobatcher package entry (lines 14-16 in the new file) — This is a lockfile normalization reflecting the bin declaration already present in package.json.
• Removed "peer": true from three dev dependencies (esbuild, fsevents, typescript) — These are lockfile v3 format adjustments that occur when npm re-resolves the dependency tree. They do not affect runtime behavior or the actual dependency relationships.

These lockfile metadata changes are cosmetic and expected when regenerating the lockfile. They do not introduce any functional changes.

[doubleword-code]

Summary

This is a routine dependency update PR from Renovate that updates @types/node from v22.19.17 to v22.19.19 in the TypeScript SDK's package-lock.json. This is a patch-level update within the same minor version series.

Verdict: Approve - This is a safe, low-risk dependency update that should have no impact on functionality.

Research notes

• @types/node is the DefinitelyTyped type definition package for Node.js APIs
• Patch updates (X.Y.Z) in DefinitelyTyped packages contain only bug fixes and non-breaking improvements to type definitions
• The codebase uses standard Node.js APIs (node:http, node:util) that are stable and well-typed
• The additional changes in package-lock.json (bin entry sync, peer flag removals) are lockfile format normalizations, not functional changes

Suggested next steps

1. Merge this PR - No code changes required, this is a safe dependency bump
2. Verify CI passes - Ensure the TypeScript typecheck and build jobs pass with the updated types (this should be automatic per .github/workflows/ci.yml)

General findings

No issues found. The changes are:

• @types/node: 22.19.17 → 22.19.19 (patch update, safe)
• Lockfile metadata normalization (bin entry, peer flags) - cosmetic only

The TypeScript source files (client.ts, serve.ts, cli.ts) use standard, stable Node.js APIs that are unlikely to be affected by patch-level type definition changes.

[doubleword-code]

Summary

This PR updates the TypeScript SDK's @types/node development dependency from v22.19.17 to v22.19.19. This is a routine Renovate-generated patch update that only affects TypeScript type definitions—no runtime code changes. The diff shows the version bump plus npm lockfile normalization (addition of the bin field and removal of peer: true flags from resolved dependencies).

Verdict: Approve — this is a low-risk, maintenance-focused update.

Research notes

• @types/node provides TypeScript type definitions for Node.js standard library APIs (e.g., node:http, node:util). Patch updates (.17 → .19) typically contain bugfixes and minor type corrections, not breaking changes.
• The TypeScript SDK uses Node-specific imports in cli.ts (parseArgs from node:util) and serve.ts (createServer, IncomingMessage, ServerResponse from node:http). These are stable, well-established APIs unlikely to be affected by a minor type definition update.
• CI validates this change via npm run typecheck (tsc --noEmit) and npm run build — any type incompatibilities would be caught before merge.

Suggested next steps

1. Merge this PR if CI passes (typecheck + build jobs confirm no regressions).
2. No code changes or additional testing required for this type-definition-only update.

General findings

No issues found. This is a standard dependency maintenance PR following best practices for keeping type definitions current.

[doubleword-code]

Summary

This PR updates the @types/node development dependency from v22.19.17 to v22.19.20 in the TypeScript SDK. This is a routine Renovate-managed patch update with no source code changes required.

Verdict: Ready to merge pending CI validation.

Research notes

• @types/node patch releases (22.19.x) contain minor type definition fixes and additions for Node.js 22 LTS
• The codebase uses stable Node.js APIs (node:http for HTTP server, node:util for parseArgs) that are not subject to breaking changes between patch versions
• Per AGENTS.md, the TypeScript SDK requires Node 18+ and CI runs npm run typecheck + npm run build which will validate compatibility
• Lockfile changes include expected normalization: "bin" field reflection (already in package.json) and peer dependency marker cleanup

Suggested next steps

1. Verify CI passes — The typescript job in .github/workflows/ci.yml will run npm install, npm run typecheck, and npm run build. This is the primary validation needed.
2. Merge if green — No additional action required if CI passes.

General findings

No issues found. This is a low-risk dependency maintenance update following standard Renovate conventions.