[antono3]

Running v run setup.vsh requested Vulkan v3.2.0 and unpinned Memory even though the allocator's supported manifest specifies Vulkan v3.2.2 and Memory v1.5.0. Align the allocator setup script's explicit dependency requests with those existing pins.

Add scripts/test_setup.vsh, a V regression script that runs the real setup script with an isolated module root and a V command-recording executable. It checks dependency versions, read-only mode, invalid arguments, and paths containing spaces without installing packages or changing native prerequisites. Run it separately on Linux, Windows, and advisory current V; the allocator sanitizer suite continues to test allocator memory behavior. A unique probe output prevents replacement of an active Windows setup executable. Disable automatic external compiler reports throughout CI.

Validation: the V fixture reproduces the wrong requests on the original script and passes after the fix. All nine allocator V test files pass locally with TinyCC and with Clang AddressSanitizer/UndefinedBehaviorSanitizer. Fresh VPM installations, exact dependency tags, allocator buffer/image/stress workloads, OpenCL vector-add/image/SVM, the GPU zero-copy memory/semaphore handshake, and staged Vulkan rendering were verified locally. Applicable checks on the final PR commit must pass before merge. No dependency manifests or generated bindings change.