fix(WINDOWS): test_openai_api_server.exe crashes with STATUS_ACCESS_VIOLATION on Windows CI

Row: -

Owed

Spec: none yet — this is a pre-existing CI failure, not a row-scoped change.

Problem

The Windows CI job windows-msvc-cpu fails on every PR with test_openai_api_server.exe exiting with code -1073740791 (STATUS_ACCESS_VIOLATION / 0xC0000005). The crash occurs in multiple api_server test cases:

• Case 58: api_server: an explicit-cpu device-selected engine serves /v1/completions
• Case 59: api_server: embeddings dispatch — OpenAI shape over the engine path
• Case 61: api_server: embeddings socket smoke; generate routes 404 on the embedding server

Plus two rc=1 failures (cases 6 and 81).

Evidence

• PR #3096 (merged at 0b5783e2e) had the same Windows failure and was merged despite it
• PR #3133 has the same failure pattern
• The crash is not introduced by any specific PR — it is pre-existing on main

Impact

Every PR shows red on Windows CI. While the failure is pre-existing and does not block individual PR merges (it fails on main too), it masks real Windows regressions and makes CI unreadable.

Start with the windows-msvc-cpu job logs and the test_openai_api_server.exe failures in cases 58, 59, 61, 6, and 81. Compare the failures with PRs #3096 and #3133, then investigate the STATUS_ACCESS_VIOLATION on Windows. Done means the affected tests no longer crash or return unexpected failures and Windows CI becomes reliable enough to expose regressions.