wgsextract-cli v0.6.5

Fixes

• Fresh Windows installs from the app work again. v0.6.4 checked the Pixi
  download with Get-FileHash. That cmdlet is missing when the app starts
  Windows PowerShell 5.1 from PowerShell 7, so new installs failed. The
  installer now computes the SHA-256 with .NET and still refuses a mismatched
  download. (#286)
• Invalid configuration values are reported, not silently used. A value of
  the wrong type in config.toml used to be coerced silently or fail later
  with a traceback. It is now ignored with a warning that names the key and
  the expected type, and the command carries on with the default. (#282, #281)

New

• One-command developer setup. From a source checkout, run
  ./scripts/dev_setup.sh (macOS/Linux) or
  powershell -ExecutionPolicy Bypass -File scripts\dev_setup.ps1 (Windows).
  The script installs Pixi and just for your user if they're missing,
  installs the locked environments and pre-commit hooks, then runs the CLI,
  deps check and the smoke tests. See
  docs/developer_setup.md.
  On Windows, just run and just test now also work under the default
  Restricted script policy. (#285, #289)

Full Changelog: v0.6.4...v0.6.5