JavaScript now runs in machine code

The groundwork experiment from the last release is now the engine, switched on for everyone. Hot JavaScript loops - the tight numeric work at the heart of hashing, data crunching, image math, and most real page scripts - no longer run in Floati's interpreter once they prove hot: the engine compiles them to real machine code for your CPU and runs that. Plain arithmetic loops run about twenty times faster than the previous compiled tier, Math-heavy chains up to thirty-eight times, and loops reading and writing arrays four to ten times. It shipped only after an unusually deep safety pass: a nineteen-million-case fuzzing campaign comparing the machine code's results bit-for-bit against the interpreter across ninety-six random seeds, the full engine conformance gate run six different ways (all identical), and a hardening audit of how each operating system grants executable memory. On the Mac the app now carries the same kind of JIT entitlements real browsers use; on any system that refuses executable memory, Floati detects that safely at startup - in a throwaway child process, so the app itself is never at risk - and keeps running on the previous tier with identical results. There is also a kill switch (FLOATI_NO_NATIVE_JIT=1) if you ever want the old behaviour back.