fix(build): add missing @emnapi install records to kun lockfile

[XingYu-Zhong]

Summary / 概要

• Fix the release builds (macOS / Windows / Linux) failing at the Install dependencies step on develop.

Why / 背景

• The root postinstall hook runs npm --prefix kun ci (via scripts/ensure-kun-install.cjs), which failed in CI:

  npm error `npm ci` can only install packages when package.json and package-lock.json are in sync
  npm error Missing: @emnapi/core@1.11.1 from lock file
  npm error Missing: @emnapi/runtime@1.11.1 from lock file
  

• kun/package-lock.json was out of sync with kun/package.json: it referenced @emnapi/core@1.11.1 / @emnapi/runtime@1.11.1 (optional peer deps of @napi-rs/wasm-runtime, pulled transitively through vitest 4's rolldown wasm fallback) but was missing their install records, so npm ci (strict mode) refused to install on all three platforms.

Changes / 变更

• Add the two missing install records for @emnapi/core@1.11.1 and @emnapi/runtime@1.11.1 to kun/package-lock.json, using the existing npmmirror mirror URLs with the official content-hash integrity. Lockfile is back in sync with package.json.

Media / 截图或录屏

• N/A (build/lockfile only, no UI change).

Tests / 测试

• N/A (no logic change). Verified by reproducing and re-running the CI install command (see Validation).

Validation / 验证

• I agree that this contribution is submitted under the Contributor License Agreement. / 我同意本贡献遵循 Contributor License Agreement 提交。
• Reproduced the failure from origin/develop, then confirmed npm --prefix kun ci --dry-run (the exact CI command) passes after the fix.
• A real npm --prefix kun ci downloaded and integrity-validated @emnapi/core, @emnapi/runtime, and @emnapi/wasi-threads, confirming the URLs and integrity hashes are correct.

Notes / 备注

• Minimal 25-line addition to kun/package-lock.json only; no source or dependency-version changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BuDt5m3agtnihau5MYt2Gd

---

Generated by Claude Code