fix(release): regenerate third-party notices for the upgraded production tree

[Astro-Han]

Summary

#2055 upgraded four production dependencies to clear the release audit, but did not regenerate the bundled license inventory. Release macOS arm64 run 30849279454 then failed inside npm run package:macos-arm64:

Error: Production dependency notices are stale. Run npm run generate:third-party-notices.

This is the output of npm run generate:third-party-notices. Four version lines change, one per upgraded package:

Package	Before	After
@hono/node-server	1.19.15	2.0.12
@modelcontextprotocol/sdk	1.29.0	1.30.0
fast-uri	3.1.4	3.1.5
undici	8.7.0	8.10.0

No package is added or removed and no declared license changes (MIT and BSD-3-Clause throughout). The @hono/node-server entry also normalizes its repository URL to the git+https:// form the package now publishes.

Verification

• npm run check:release — the exact command the release packaging step runs, and the one that caught this. All three gates pass: check:stale reports dist fresh, check:third-party-notices reports the inventory current, check-dead-css finds nothing dead.
• npm ci then npm run build: clean.
• npm run format:check: clean.

Review focus

check:release only runs inside npm run package:macos-arm64, so no ordinary CI lane exercises it — #2055 was fully green and still left this stale. Any future change to the production dependency tree needs npm run generate:third-party-notices in the same commit, or the release fails at packaging.

Rollout

Re-dispatch Release macOS arm64 once this is on main and CI is green. The failed run stopped before Create draft GitHub Release, so no v0.1.4 tag or release exists yet and the version does not need another bump.