fix(deps): clear the high-severity advisories blocking the release audit

[Astro-Han]

Summary

The Release macOS arm64 run for 0.1.4 failed at its first real gate, npm audit --omit=dev --audit-level=high, before it reached packaging or reserved a release identity (run 30848094969). Four production advisories were outstanding, two of them high:

Package	Before	After	Severity	Advisory
undici	8.7.0, 8.8.0	8.10.0	high ×2	GHSA-8xcm-r25x-g524, GHSA-4cwx-7wf7-3272
fast-uri	3.1.4	3.1.5	high	GHSA-7p8r-x3mc-p8w7
@hono/node-server	1.19.15	2.0.12	moderate	GHSA-frvp-7c67-39w9
@modelcontextprotocol/sdk	1.29.0	1.30.0	moderate	depends on the above

Lockfile only. Every fixed version already satisfies the existing declared ranges — undici ^8.7.0 in runtime and headless, @modelcontextprotocol/sdk ^1.24.3 in mcp, and fast-uri through ajv's ^3.0.1 — so no package.json changes are needed. SDK 1.30.0 widens its own range to ^1.19.9 || ^2.0.5, which is what lets @hono/node-server move off the vulnerable line. @hono/node-server 2.x requires Node >=20; the repository already requires >=22.19.0.

Verification

• npm audit --omit=dev --audit-level=high: 0 vulnerabilities (was 4).
• npm ci then npm run build: clean.
• @maka/mcp 11/11 pass, @maka/headless 1337/1337 pass.
• @maka/runtime 3076/3089 pass. The 4 failures are builtin-tools workspace-containment cases that fail identically on unmodified main on macOS, where the temp dir resolves through the /var → /private/var symlink; they are environment-specific and unrelated to this change. CI runs on Linux and does not hit them.
• npm run format:check and npm run lint: clean.

Review focus

undici moves three minors. Its use is confined to bot bridges (WebSocket) and the network layer (Agent, ProxyAgent, EnvHttpProxyAgent, fetch). Worth noting: packages/headless/src/provider-auth-proxy.ts documents the 8.7-vs-8.8 h2 multiplexing gate and deliberately forces h1 pools so it does not depend on which undici build serves the fetch — that comment stays accurate at 8.10.

Rollout

Once this is on main and CI is green, re-dispatch Release macOS arm64. The failed run stopped before Resolve and reserve release identity, so the v0.1.4 tag and release name are still unused and the version does not need to be bumped again.