Commit 3dfb35700 accidentally saved scripts/install.ps1 with a UTF-8 BOM (EF BB BF) at byte 0. PowerShell's normal file-execution path (`& .\install.ps1`) handles BOMs fine, but the curl-and-iex one-liner documented in the README uses `[scriptblock]::Create((irm ...))` which does NOT strip BOMs — the BOM lands inside the param() block and fails with 'The assignment expression is not valid' on $Branch and $HermesHome. teknium1 hit this trying to reinstall from the PR branch after Brooklyn's commits landed. Every user trying the PR branch install-one-liner hit it too until we notice. Saved without BOM, verified via xxd: file now starts with '# =====' at byte 0 instead of EF BB BF. |
||
|---|---|---|
| .. | ||
| lib | ||
| whatsapp-bridge | ||
| build_model_catalog.py | ||
| build_skills_index.py | ||
| check-windows-footguns.py | ||
| contributor_audit.py | ||
| discord-voice-doctor.py | ||
| hermes-gateway | ||
| install.cmd | ||
| install.ps1 | ||
| install.sh | ||
| keystroke_diagnostic.py | ||
| kill_modal.sh | ||
| lint_diff.py | ||
| profile-tui.py | ||
| release.py | ||
| run_tests.sh | ||
| sample_and_compress.py | ||
| setup_open_webui.sh | ||