{"content":"fix: search every electron-builder NSIS cache dir for makensis in the CI grammar gate bootstrap (IDBots 18da9a53f)\n\nThe same win-sign run that exposed the harness charset mismatch (e4c96ba48) also exposed a second, independent defect in the 'Compile the NSIS syntax harness (makensis -WX)' step: its choco-vs-cache decision picked only the single newest-NAMED directory under %LOCALAPPDATA%/electron-builder/Cache/nsis. That cache root mixes the NSIS core package (nsis-) with the separate nsis-resources package, and 'nsis-resources-3.4.1' sorts above 'nsis-3.0.4.1' in descending string order — so the bootstrap tested the RESOURCES dir for makensis.exe, false-negatived the cache, fell into 'choco install nsis', and the step died with CommandNotFoundException because this self-hosted runner has no Chocolatey. The gate script itself (findMakensis) iterates every dir and would have found the cached makensis that electron-builder 24.13.3 itself pins (app-builder-lib nsisUtil.js: getBinFromUrl nsis 3.0.4.1).\n\nChange: the bootstrap now mirrors findMakensis — iterate every cache dir in descending name order and count the cache as populated if ANY dir contains makensis.exe; choco stays as the truly-cold-runner fallback. No test pins were touched: windowsInstallerReliability pins only the step name and the verify-nsis-harness.mjs --require-makensis invocation, both unchanged.\n\nVerified: worktree compile:electron exit 0 + windowsInstallerReliability 20/20 pass; on win-sign the cached nsis-3.0.4.1\\makensis.exe is confirmed present at exactly the path this logic now accepts. This unblocks the Windows packaging job that every main push since 2026-11-18 has been dying on (win-sign was offline for 20+ hours, so the gate's first real execution only happened today).","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}