Explicit extern "sysv64" and "win64" (and their -unwind forms) follow
rustc's x86_64 conventions, with rustc's E0570 on other targets. A quit is
clean at any time (signal, window close, remote quit, during boot); the boot
window moves, resizes and closes while the app boots, and a boot probe
reports stalls. `makepad check --boundary` audits every provided crate the
loader binds: JIT code reaches makepad-hal, script, shader and Linux
capture state only through #[relax_api] ops. Domains keep their package
names and threads; constants are copied per domain through their pointer
words; a read binding owns its snapshot on the reading thread. Android:
zone arenas reserve 8 GB, inspect shows thread stacks, opening an app from
the phone WM no longer hangs. Windows: the source watcher ends at quit and
the boot window's shaders compile for D3D11. Tests that build or drop a JIT
unit run alone in a child process. The load screen follows the WM's
dark/light live, has a close button and drags from anywhere.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>