{"content":"fix: compile the NSIS harness with the real build's UTF8 charset and a pinned POSIX locale (IDBots e4c96ba48)\n\nThe NSIS grammar gate (verify-nsis-harness.mjs) failed on win-sign with 'Bad text encoding: nsis-syntax-harness.nsi:47' the first time the new CI gate actually executed there: makensis without an explicit input charset reads the .nsi as the system ANSI codepage, and on the zh-CN (GBK) signing machine the BOM-less UTF-8 em-dash punctuation in the 2026-11-19 harness comments is an invalid GBK sequence. The real electron-builder packaging path was never exposed because NsisTarget pushes exactly -INPUTCHARSET UTF8 at makensis — the gate simply did not match its own production compile.\n\nChange: verify-nsis-harness.mjs now passes -INPUTCHARSET UTF8 (mirroring NsisTarget.js:487) so the gate compiles the same source the same way the real installer build does, on any ACP. Second surface found while verifying: POSIX makensis ignores -INPUTCHARSET and derives the input charset from the process locale, so a C/POSIX-locale caller (CI shells, agent harnesses) rejects the same valid UTF-8 with the identical error even though an interactive UTF-8 terminal passes. The script now pins LC_ALL/LANG=en_US.UTF-8 for the makensis child on non-Windows, making the local grammar gate deterministic regardless of caller environment.\n\nVerified on the target machine: hand-driven makensis 3.0.4.1 (electron-builder 24.13.3's pinned NSIS, already in the machine cache) compiled BOTH harness shapes clean under -WX -INPUTCHARSET UTF8 (installer 799 instructions, uninstaller processed). Locally: the gate now passes under a C-locale caller on homebrew makensis 3.13, which previously reproduced the failure via a minimal em-dash comment repro.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}