Julian lechnerandClaude Sonnet 5
1c2d155fcc
Windows PowerShell 5.1's -Encoding UTF8 always prepends a BOM, and Get-FileHash returns uppercase hex. Bash's manifest reader expects neither, so a manifest written by this module and later read by the Bash equivalent (or vice versa) mismatched on every single entry: the BOM folded into the header's first field, and every hash comparison failed on case alone. Hashes are now lowercased on read and write, and the manifest file itself is written UTF-8 without a BOM. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>