Plain downloads, one-file engines, and v0.0.26

v0.0.26 ships plain native files and one .wasm per engine with a default-deny sandbox loader, passes the latest Test262 unmodified on 64-bit and 32-bit builds, and imports torch in WebKit in under 0.4 s instead of about 32 s.

v0.0.26 was published on 18 October from 5f1c0578, the first release of plain files. Windows gets zipp-0.0.26-windows-x86_64-portable.exe (17,624,064 bytes) and zipp-0.0.26-windows-x86_64-installer.msi (5,718,016), which installs per user into %LOCALAPPDATA%\Programs\ZIPP and adds zipp to the user's PATH with no administrator rights. Linux gets zipp-0.0.26-linux-x86_64, -linux-arm64 and -linux-armv7, the last for 32-bit Arm with hard float and interpreter only; they need glibc 2.35 or later and chmod +x. The WebAssembly engines are four .wasm files and the torch package, each engine carrying its own bindings, and zipp-0.0.26-wasm-embed-kit.zip holds zipp.mjs, which loads any of them and runs programs in a Worker with nothing permitted unless granted. As published, the JavaScript engine is 4,673,483 bytes and 1,197,743 after Brotli; without its bindings, 1,184,942 after Brotli, 3.3% more than v0.0.25's 1,146,621. The sandbox playground runs it.

Test262 at the corpus of 13 October 2026 (d53ebc8b), unmodified, passes 96,229 of 96,230 executions with one expected Annex B failure, and so do a 32-bit build, which CI now runs as a Windows i686 job (65c1c1d8), and the arm64 Linux CLI built on an Arm runner. Indices and lengths past 2^32 had been truncated on 32-bit hosts, wasm32 and armv7, in every earlier WebAssembly release too, and are exact now (2d337999). The first import torch in a fresh engine falls from about 32 s to under 0.4 s in WebKit, from 0.64 s to about 0.27 s in Chromium and from 0.78 s to about 0.3 s in Node (7eb926e9, f091e2fe, a4099b74). Over the cycle, on canonical held-out builds, the interpreter went from 1.199× to 0.931× of Bellard's QuickJS's time on the 21 expansion workloads and from 0.834× to 0.791× on the 17 hostile ones.