build-number

Stop Windows release builds running out of memory, and fix the cdylib link Two failures on x86_64-pc-windows-msvc. rustc-LLVM ERROR: out of memory Allocation failed [profile.release] sets lto = true, codegen-units = 1 and debug = "full". Across executorch, onig, zstd, lzma and blake3 that puts the entire program in a single LLVM module with full debug info and exhausts the agent. Override to thin LTO, debug = 1 and no incremental via CARGO_PROFILE_* in the Windows branch of getEnvVars, so only Windows changes and the macOS and Linux release artifacts keep the original settings. Incremental does nothing under LTO anyway. lld-link: error: subsystem must be defined lld-link infers the subsystem from the entry point, and with everything merged into one LTO object it stops finding _DllMainCRTStartup when linking divvun-runtime-ffi's cdylib. The override dated from the repo's initial import with no stated rationale; rustc defaults to MSVC link.exe for msvc targets, which infers this correctly. crt-static is retained on both targets. Neither change is verified on Windows -- there is no msvc toolchain here.