[0xcadams]

What

Update the repository's Next.js development dependency from 16.4.0 to 16.4.3, above the compatible dependency layer in #489. Published SDK dependencies, product versions, and the supported Node minimum remain unchanged.

Why

Next 16.4.0's security assessment detects the coding agent and exits the development server before the framework fixture's first page request. Both the old and corrected SDK reproduce that exit, which surfaces later as ECONNREFUSED; it is not an SDK startup failure.

The registry advisories include 16.4.0 but not 16.4.3, and Next's assessment reports 16.4.3 as unaffected. The real framework tests and full JavaScript checks pass with the security check still enabled. No notice suppression, fixture retry, or timeout change is needed.

Changes

• Pin the development-only Next dependency to 16.4.3 and regenerate its matching environment and platform SWC lock entries.
• Keep Node >=22.18, the optional Next peer range, all unrelated dependency resolutions, and runtime license output unchanged.

[0xcadams]

incorporated into #489 at signed head eebe196. pushing its signed commit to this PR’s comparison base caused GitHub to mark it merged into that branch; main remains 51fd72b. both original signed commits and this review are preserved. the combined source passed Go tests/lint/harness, JavaScript checks and source packing, Chrome browser checks, generated-source verification, vulncheck, and framework/generation checks on the supported Node 22.18 minimum.