Version: 1.1.3 fix(deps): refresh dependencies and prepare release

[sergeliatko]

Summary

The locked dependency tree had three high-severity and one moderate-severity vulnerable packages. This patch updates all compatible direct dependency floors and refreshes transitive resolutions; full, production-only, and fresh generated app audits now report zero vulnerabilities.

Prepare version 1.1.3 with matching package metadata, changelog, release notes, and README link. Align generated app SOAP and Node type ranges, and replace the stale Node 20 development pin with Node 24. TypeScript remains at 6.0.3, matching the maintained compiler policy and lint peer requirements.

This update covers the dependency bumps proposed in #211, #212, #213, #214, and #215, including newer Node type and typescript-eslint patches. No generated API or configuration migration is required.

Checklist

• Existing WSDL fixtures cover parsing, generation, and real local SOAP transport.
• Tests and pipeline smoke cover the dependency updates.
• Release notes and README documentation index are updated.
• No breaking changes; TypeScript 7 is excluded.

Validation

• Clean lockfile installation with npm 12.0.1; dependency tree has no invalid packages.
• Full and production-only audits and a fresh generated app audit: zero vulnerabilities.
• Node 24 release preflight: 18 passed checks, zero failures or skips; expected feature-branch warning.
• Full CI: 661 tests across 52 files, including conformance; pipeline generation/typecheck passed.
• Installed npm package smoke: 73 TypeScript artifacts, CLI/API generation, consumer typecheck/tests, and SOAP transport.
• Node 26 compatibility: 423 unit tests, build, typecheck, and pipeline smoke passed.
• Agent skill ZIP and checksum manifest built; preflight preserved the tracked tree.

Release delivery

After Node 24 and Node 26 CI pass, merge and verify that main matches the preflight-validated tree. Require merged-main CI before pushing immutable tag v1.1.3. The Draft Release workflow packages, attests, uploads, and verifies the skill artifact. Maintainer publication of the verified draft triggers the guarded npm publishing workflow.