Windows 3.14 native parity: test_vector.py process died silently once on main #295

The native parity job on Windows with Python 3.14 failed once on main: the pytest process for tests/test_vector.py died without a traceback, 17 of 46 tests into the file.

• Run: https://github.com/ArcadeData/arcadedb-python/actions/runs/42187538256 (the push of the Docs: Python functions and record events, with tests that pin each statement first (refs #267) #284 merge commit 361e36efa3), job Parity against the installed wheel (windows-x64, Python 3.14).
• The per-file log in the uploaded native-parity-windows-x64-py3.14 artifact shows collected 46 items and then 17 passing dots and nothing else: no failure, no Python traceback, no Windows fatal exception text. No XML was written, so the runner reported test_vector.py(CRASH) with 0 tests, while the other files of that job passed (2432 passed, 0 failed).
• Counting the tests in file order, the 18th is TestLSMVectorIndex::test_lsm_vector_search_approximate_returns_k (a count of def test_ in the file at that commit, not a confirmed trace).
• It does not reproduce: the PR run of the same code was green on Windows, and the next push to main (Return a Python str from Document.get_type_name() on arcadedb-jvm #287, f0d594a124) was green on every platform. Docs: Python functions and record events, with tests that pin each statement first (refs #267) #284 only added docs and tests.
• native/wheel/parity_wheel.py already carries a comment that whole-file runs of test_vector.py on Windows failed in the past, when the engine logged to the console under pytest's fd capture. This may be the same family, but nothing in this log shows it.

What is missing is the exit code of the dead process. An access violation, a kill by the runner and a pytest-internal abort all look the same in the current log. I am sending a one-line change so the next occurrence records it (CRASH(rc=...) in the status and the log). I will not retry crashed files automatically: one occurrence does not justify hiding a native crash.

If it happens again on Windows, this issue collects the occurrences.