release: Kun v0.2.27-1

[XingYu-Zhong]

Summary

Prepare the 0.2.27-1 release retry after the previous merged release workflow failed before producing Windows and Linux artifacts.

Changes

• Prevent media-handle persistence from serializing Windows filesystem identifiers that exceed JavaScript's safe integer range, while retaining available identity checks.
• Replay extension-discovery notifications through the packaged renderer cold-start window instead of blocking the desktop smoke on a precondition that can never become true.

Root cause

• Windows failed in the Extension public release gate because a large NTFS inode was rejected by Zod during atomic JSON validation.
• Linux successfully built its AppImage, then the packaged Chromium smoke timed out waiting for a workbench contribution before it had replayed the event that starts the renderer retry path.

Validation

• npm run build:kun
• npm run typecheck
• npm --prefix kun run test -- src/services/extension-media-handle-service.test.ts src/services/extension-media-ffmpeg-service.test.ts src/services/extension-media-archive-service.test.ts src/services/extension-media-process-service.test.ts
• node --test scripts/smoke-packaged-extension-desktop.test.cjs
• npm run check:extension-release-gate

[github-actions]

PR checks failed. Please fix the failing CI jobs before merging.

Failed jobs:

• Build Linux package
• Ad-hoc macOS packaged validation (PR)
• Windows NSIS packaged validation (PR)

Run details: https://github.com/KunAgent/Kun/actions/runs/29596284227