Illegal instruction panic on non-AVX2 Windows CPU (SSE4.2/AVX only)

[pxthreads]

What happened

1. Ran freebuff on a Windows 10 laptop with a CPU that only supports SSE4.2/AVX (no AVX2).
2. Expected the CLI to start normally since it detected and reported "no_avx2" and "Features: no_avx2" in its own startup banner.
3. Instead, it immediately crashed with "panic: Illegal instruction" followed by "panicked during a panic. Aborting."

Steps to reproduce

1. Install on a Windows 10 x64 machine with a CPU lacking AVX2 support (has SSE4.2 and AVX only).
2. Run npm install -g freebuff
3. Run freebuff
4. Deleted %USERPROFILE%.config\manicode folder and let it re-download the binary fresh, then ran freebuff again.
5. Same crash occurs both times, immediately on startup, before any prompt or interaction.

Note: the tool's own startup banner correctly detects "no_avx2", but still appears to run AVX2 instructions internally, causing the CPU to fault.

Where does this happen?

CLI (terminal client)

Operating system

Windows

Version

0.1.4

Model

MiMo V2.5

Logs or screenshots

PS C:\Users\iamza> freebuff                                                       
Download complete! Starting Freebuff...
============================================================
Bun v1.3.14 (0d9b296a) Windows x64
Windows v.win10_cu
CPU: sse42 avx
Args: 
Features: no_avx2 
panic: Illegal instruction at address 0x7FF7B521F82C
panicked during a panic. Aborting.
PS C:\Users\iamza>