[Windows] Desktop packaging fails: payload smoke test requires the removed fs-ext dependency

[hinagigu]

Summary

pnpm package:desktop:win:x64:unsigned fails on Windows at the prepare:dsh stage. apps/desktop/tests/fixtures/runtime-payload-smoke.mjs (checkFsExt) requires fs-ext, but no package in the current dependency tree depends on it anymore.

Environment

• OS: Windows 11 (10.0.26200)
• Node: v24.19.0 (system; the bundled runtime is used for the smoke itself)
• Commit: c291e7961a (master, version 0.1.5-rc.2)
• Command: pnpm package:desktop:win:x64:unsigned

Error

Error: desktop native payload smoke failed: ...
Error: Cannot find module 'fs-ext'
  Require stack:
  - ...\targets\win-x64\dsh\package.json
      at checkFsExt (apps/desktop/tests/fixtures/runtime-payload-smoke.mjs:69:17)

The prepare:runtime and prepare:packages stages complete; the failure is inside prepare:dsh before the Host smoke and descriptor verification.

Root cause

• c58097a826 (Aug 31) added "fs-ext": "2.1.1" to packages/session/session-persistence-jsonl/package.json for the cross-process write-ownership lease.
• d927cbff99 (Sep 7, feat(native): add prebuilt Node-API flock support) removed fs-ext and replaced it with @deepseek-ai/node-addon-system/flock.
• fc7abdcfb5 (Sep 9, 优化 windows 安装包打包) added the payload smoke test whose checkFsExt() still requires fs-ext — referencing the already-removed dependency, and running on Windows where the replacement cannot apply: @deepseek-ai/node-addon-system ships platform packages only for darwin/linux (native/system/packages/); Windows keeps its koffi-based locking.
• No CI workflow exercises the desktop packaging path, so this never surfaced.

Suggested fix

Make checkFsExt() skip when fs-ext cannot be resolved (POSIX keeps the existing seek assertions), or replace the check with @deepseek-ai/node-addon-system on POSIX plus the existing koffi check on Windows.

Notes

Local workaround: wrap the require in try/catch and skip on absence — packaging then completes on Windows.

Two further requirements we hit while packaging Windows locally, possibly worth documenting:

1. The system tar must resolve to C:\Windows\System32\tar.exe. From a Git-Bash-launched environment, tar resolves to Git's GNU tar, which mangles Windows paths (D:\... arrives as D\:\\...), and the release:pack verification (tar -tzf) fails with gzip: stdin: unexpected end of file.
2. DSH_DESKTOP_APP_ID must be exported even for --unsigned builds (reverse-DNS form).