# Windows cache hash and FFI output pointers

Qualification on 2026-10-10 from 9f4a074cdc753efee659212333fc664dac51a2c9.

The development-server cache hash receives the same mtime value directly. Win32 job configuration, console size and sudo registry calls use explicit raw mutable output pointers, preserving buffer types, lengths, handle ownership and call results. Rust formatting also normalizes the existing elevate module.

Locked strict bun_runtime Clippy passes on GNU x64 and ARM64 on the VPS. Both MSVC targets report zero errors in these four files and 24 unrelated runtime errors (exit 101), down from 28. Scoped Rust formatting and git diff checks pass.

The changed Windows debug engine, built with MSVC 14.44, four jobs/linker threads and full symbols, runs app-options, HMR socket protocol, parallel startup-failure and parallel suites: 46 pass, eight inherited platform skips, zero failures, two snapshots, 288 assertions, 31.05 seconds. The skipped process-tree cases are not established by this run. Console interactivity and UAC elevation are compile-qualified only; no interactive elevation is claimed.

Receipts remain in tmp/windows-ffi-output-* and the VPS owner-linux-qualification directory. Before linkage, 180 exact canonical Cargo cache artifacts were NTFS-compressed under the factory lock, with all SHA256 values unchanged; free space rose from 6575116288 to 9315995648 bytes. No artifact or symbol was removed.

Global strict qualification, tagged release/performance, PATH promotion, private video delivery and physical Linux GPU verification remain open.