fix: install.ps1 ASCII-clean — PS 5.1 no-BOM ANSI read caused ParserError cascade #19
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/installer-ps51-ascii"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stock Windows PowerShell 5.1 (the win11-test golden's only shell; pwsh absent) reads BOM-less script files as the system ANSI codepage. The installer's U+2014 em-dashes, U+2500 box rules, and U+2713 checkmarks decode to cp1252 bytes whose 0x93/0x94 trail bytes become U+201C/U+201D — which PowerShell tokenizes as string delimiters. Strings close early, braces unbalance, and the hash-pinned runbook installer dies with a MissingEndCurlyBrace/ParseException cascade before executing (observed on win11-test, inv-20260912T000801Z vm/win/install-bypass.transcript).
Pure ASCII is codepage-invariant (every byte < 0x80 decodes identically under any ANSI codepage), which removes the parser-mode question entirely — preferred over a UTF-8 BOM, which future ASCII-loving editors can silently strip.
Known separate blocker (NOT this PR): the vendored-minisign gate ($MinisignExeSha256 placeholder + tools-minisign-0.11 release absent) still refuses every install until S011 publishes — plan-gated on Operator confirmation.
aa06813027to2752d76fde