[Maintenance]: Refresh dependency and test tooling drift

[Fermionic-Lyu]

Summary

The SDK repo has dependency/toolchain drift. Unit tests currently pass, but the test run emits a Vite CJS Node API deprecation warning and npm outdated reports multiple major-version gaps in the test/lint stack.

Validation

Valid. npm run typecheck passes and npm test -- --run passes, but the test command prints the Vite CJS Node API deprecation warning. npm --cache /private/tmp/insforge-sdk-npm-cache outdated --json was run on May 29, 2026.

Relevant Code

• package.json:66 - @vitest/coverage-v8 is declared as ^1.3.1; current lock has 1.3.1, wanted 1.6.1, latest 4.1.7.
• package.json:70 - vitest is declared as ^1.3.1; current lock has 1.3.1, wanted 1.6.1, latest 4.1.7.
• package.json:67 - eslint is declared as ^8.57.0; current lock has 8.57.1, latest 10.4.0.
• package.json:63 and package.json:64 - @typescript-eslint/* are on 7.x; latest reported was 8.60.0.
• package.json:59 - socket.io-client current 4.8.1, wanted/latest 4.8.3.
• package.json:68 - tsup current 8.5.0, wanted/latest 8.5.1.
• npm test -- --run output - The CJS build of Vite's Node API is deprecated.

Proposed Solution

Plan a dependency/toolchain refresh, starting with safe patch/minor updates and then a separate major-upgrade pass for Vitest/Vite, ESLint, and TypeScript-ESLint.

Acceptance Criteria

• Patch/minor dependency updates are applied where safe.
• Test output no longer emits the Vite CJS Node API deprecation warning, or the warning is documented with a tracked upstream blocker.
• Major toolchain upgrades have a separate compatibility checklist and verification path.
• npm run typecheck and npm test -- --run pass after the update.