Release rpc-node-toolkit 0.1.4

[n-car]

What changed

• rewrites the root TypeScript declarations around the canonical CommonJS export = plus namespace-merging model;
• adds a dedicated declaration for the /safe object entrypoint while preserving all runtime exports;
• makes /safe named exports discoverable to Node.js ESM consumers without changing object values or order;
• adds tarball-based TypeScript and runtime consumer tests for ESM and CommonJS;
• adds publint and Are the Types Wrong validation, CI packaging coverage, and compatibility documentation;
• updates the package and lockfile to 0.1.4.

Why

The previous declarations described an ESM-shaped default while the runtime uses module.exports = RpcEndpoint; the /safe entrypoint also pointed to the wrong declaration and its spread exports were not statically visible to Node.js ESM.

Impact

This release restores strict TypeScript compatibility while preserving the constructable CommonJS root, all 13 named runtime properties, and the /safe subpath.

Validation

• 8 Node.js tests
• TypeScript 6 ESM/NodeNext and CommonJS consumers with skipLibCheck: false and esModuleInterop: false
• Node.js ESM and CommonJS runtime smoke tests
• publint strict and ATTW for root and /safe
• npm publish --dry-run
• dependency audit with no vulnerabilities