rc8在离线本地部署的情况下，会出现报错，定位在scripts文件中

[Intelligentist]

报错如下
$ tsx scripts/build.ts
node:internal/errors:998
const err = new Error(message);
^

Error: Command failed: git rev-parse HEAD
at genericNodeError (node:internal/errors:998:15)
at wrappedFn (node:internal/errors:543:14)
at checkExecSyncError (node:child_process:925:11)
at execFileSync (node:child_process:961:15)
at repositoryCommitHash (D:\deepseek-harness\scripts\client-build-environment.ts:49:29)
at main (D:\deepseek-harness\scripts\build.ts:41:29)
at (D:\deepseek-harness\scripts\build.ts:55:23)
at ModuleJob.run (node:internal/modules/esm/module_job:377:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:671:26)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5) {
status: 128,
signal: null,
output: [ null, '', null ],
pid: 133284,
stdout: '',
stderr: null
}

Node.js v25.1.0
pnpm版本为11.7.0

rc7多次重装均正常安装，pnpm run build正常，rc8 在pnpm run build环节会出现如上报错

[denial123789]

I checked this against rc.8 source revision 141eb6f. The stack is a source-provenance failure before compilation or offline dependency resolution.

rc.8 introduced a root build orchestrator that calls repositoryCommitHash() first. That function uses DSH_CLIENT_COMMIT_HASH when explicitly present; otherwise it runs git rev-parse HEAD in the repository root. An extracted source directory without .git therefore produces exactly this exit-128 path even if Git is installed and every pnpm dependency is locally available.

The reported Node 25.1.0 and pnpm 11.7.0 match rc.8's declared contracts (^22.19.0 || >=24.0.0, pnpm@11.7.0), so I would not change those first for this signature.

Two safe source-identity paths:

1. Preferred: transfer a verified Git bundle for tag dsh-v0.1.0-rc.8, verify its media digest offline, clone it, and require git rev-parse HEAD = 141eb6fef83422698aef7a981029e843e8161534.
2. Supported metadata-free fallback: only after independently authenticating the snapshot as that exact commit, set DSH_CLIENT_COMMIT_HASH=141eb6fef83422698aef7a981029e843e8161534 before pnpm run build. The rc.8 function explicitly supports 7–40 hex characters and embeds the seven-character prefix.

Do not initialize a new repository, make a synthetic commit, or insert 0000000; those make the build pass with false provenance. Also keep this separate from the second air-gap boundary: frozen lockfile, transferred pnpm store, matching Windows architecture/native packages, and an offline rehearsal with networking disabled.

I wrote the PowerShell/CMD/POSIX commands, Git-bundle flow, dependency-closure checklist, build-record verification, and regression contract here:

• Visual route: https://sandbaseai.github.io/deepseek-harness-handbook/air-gapped-source-build.html
• Full guide: https://github.com/sandbaseai/deepseek-harness-handbook/blob/main/docs/en/getting-started/air-gapped-source-build.md

[shudingbo]

ubuntu 24.04, node24.13 一样错误